RHEL5.8 if the ext3 file system is damaged, only the file system is not repaired (fsck,

RHEL5.8 if the ext3 file system is damaged, only the file system is not repaired (fsck,

RHEL5.8 if the ext3 file system is corrupted, it will only detect and not repair (fsck-n)

[root@lei1 ~]# df -ThFilesystem    Type    Size  Used Avail Use% Mounted on/dev/mapper/VolGroup00-LogVol00              ext3    872G  345G  482G  42% //dev/sda1     ext3    190M   13M  168M   7% /boottmpfs        tmpfs    2.0G     0  2.0G   0% /dev/shm[root@lei1 ~]# uname -r2.6.18-308.el5[root@lei1 ~]# uname -aLinux lei1 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux[root@lei1 ~]# [root@lei1 ~]# [root@lei1 ~]# fsck -n /dev/mapper/VolGroup00-LogVol00fsck 1.39 (29-May-2006)e2fsck 1.39 (29-May-2006)Warning!  /dev/mapper/VolGroup00-LogVol00 is mounted.Warning: skipping journal recovery because doing a read-only filesystem check./dev/mapper/VolGroup00-LogVol00 contains a file system with errors, check forced.Pass 1: Checking inodes, blocks, and sizesDeleted inode 67141633 has zero dtime.  Fix? noPass 2: Checking directory structurePass 3: Checking directory connectivityPass 4: Checking reference countsPass 5: Checking group summary informationBlock bitmap differences:  -76226569Fix? noFree blocks count wrong for group #643 (1459, counted=1458).Fix? noFree blocks count wrong for group #2326 (31294, counted=31293).Fix? noFree blocks count wrong (127388309, counted=137957667).Fix? noInode bitmap differences:  -67141633Fix? noFree inodes count wrong (235607546, counted=235607894).Fix? no/dev/mapper/VolGroup00-LogVol00: ********** WARNING: Filesystem still has errors **********/dev/mapper/VolGroup00-LogVol00: 158214/235765760 files (1.1% non-contiguous), 108361067/235749376 blocks[root@lei1 ~]# 

I once again stressed that fsck-y is a very dangerous thing to repair the file system. After I met fsck-y, fsck deleted the file directly...