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
