Hi Stephen, Thank you so much for your helps. My problem is when the system is booted, there are some duplicate block error. some error messages are as the following: /////////BEGIN ERROR MESSAGE checking root filesystem /:Duplicate blocks found... invoking duplicate block passes Pass1B: Rescan for duplicate/bad blocks /:Duplicate/bad blocks in inode 52:/: 1661/: /:Duplicate/bad blocks in inode 53:/: 1662/: /:Duplicate/bad blocks in inode 71:/: 1662/: /:Duplicate/bad blocks in inode 74:/: 1661/: /:Pass1C: Scan directories for inodes with duplicate blocks /:Pass1D: Reconciling duplicate blocks /:(There are 4 inodes containing duplicate/bad blocks) /:File /root/.gnome/session(inode#74.) has 1 duplicate block(s), shared with 1 file(s) /: /root/panel.d/default/Applet_4.desktop (inode#52) ////////END OF ERROR MESSAGE So, I tried to use rescue mode and fsck to fix it, but failed. > >Hi, > >On Wed, May 15, 2002 at 07:24:34AM +0000, yan bai wrote: > > After booted to rescue mode (system files are mounted to mnt/sysimage/), >a > > 'shell' was created, then I used fsck /dev/sda1 and get message as the > > following: > > sh-2.04# fsck /dev/sda1 > > parallelizing fsck version 1.19(13-Jul-2000) > > e2fsck 1.19 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 > > /boot:clean, 27/14056 files, 5616/59196 blocks. > > > > It seems the problem still exist, > >What problem? There's no sign of a problem in the above --- fsck >found the fs clean and exited. That's not a problem. If you want to >force a full fsck regardless of whether the filesystem is clean or >not, you can always "fsck -f". > > > BTW, I hope I can get some hints on the usage and differences between >fsck > > and e2fsck, I cannot get a satisfied answer after googled a whole night. > >fsck is the generic program for checking any filesystem. e2fsck is >the specific version customised for ext2 and ext3. If you run fsck, >all it does it work out which type of filesystem is involved --- it >then calls the appropriate special-case program to check that >particular filesystem. > >So, for ext2 or ext3 filesystems, it doesn't much matter whether you >call fsck or e2fsck. If you call fsck, then fsck will invoke e2fsck >itself automatically. > >Cheers, > Stephen > > > >_______________________________________________ > >Ext3-users@redhat.com >https://listman.redhat.com/mailman/listinfo/ext3-users _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
