Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ===================================================================checking root filesystem /:contain a file system with errors. check forced ... /:Duplicate blocks found... invoking duplicate block passes Pass 1B: Rescan for duplicate/bad blocks /:Duplicate/bad block(s) in inode 52:/: 1661/: /:Duplicate/bad block(s) in inode 53:/: 1662/: /:Duplicate/bad block(s) in inode 71:/: 1662/: /:Duplicate/bad block(s) in inode 74:/: 1661/: /Pass 1C: Scan directories for inodes with dup blocks /:Pass 1D: Reconciling duplicate blocks /:(There are 4 inodes containing duplicate/bad blocks) /:File /root/.gnome/session/ (inode #74, mod time Sun Apr 21 12:48:48 2002) has 1 duplicate blocks), shared with 1 file(s): /: /root/.gnome/panel.d/default/Applet_4.desktop (inode #52, mod time Sun Apr 21 10:02:00 2002) /: /:UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY ================================================= Below are what I tried with 'fsck' (Repair Filesystem)1# fsck Parallelizing fsck version 1.19 (13-Jul-2000) (Repair Filesystem)2# fsck /root Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Is a directory while trying to open /root (Repair Filesystem)3# fsck /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Read-only file system while trying to open /root/.gnome/session Disk write-protected, use -n option to do read-only (Repair Filesystem)4# fsck -n /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Attemp to read block from filesystem resulted in short read while trying to open /root/.gnome/session Could this be a zero-length partition? ======================================================== _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com
Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ===================================================================checking root filesystem /:contain a file system with errors. check forced ... /:Duplicate blocks found... invoking duplicate block passes Pass 1B: Rescan for duplicate/bad blocks /:Duplicate/bad block(s) in inode 52:/: 1661/: /:Duplicate/bad block(s) in inode 53:/: 1662/: /:Duplicate/bad block(s) in inode 71:/: 1662/: /:Duplicate/bad block(s) in inode 74:/: 1661/: /Pass 1C: Scan directories for inodes with dup blocks /:Pass 1D: Reconciling duplicate blocks /:(There are 4 inodes containing duplicate/bad blocks) /:File /root/.gnome/session/ (inode #74, mod time Sun Apr 21 12:48:48 2002) has 1 duplicate blocks), shared with 1 file(s): /: /root/.gnome/panel.d/default/Applet_4.desktop (inode #52, mod time Sun Apr 21 10:02:00 2002) /: /:UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY ================================================= Below are what I tried with 'fsck' (Repair Filesystem)1# fsck Parallelizing fsck version 1.19 (13-Jul-2000) (Repair Filesystem)2# fsck /root Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Is a directory while trying to open /root (Repair Filesystem)3# fsck /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Read-only file system while trying to open /root/.gnome/session Disk write-protected, use -n option to do read-only (Repair Filesystem)4# fsck -n /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Attemp to read block from filesystem resulted in short read while trying to open /root/.gnome/session Could this be a zero-length partition? ======================================================== _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com
Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ===================================================================checking root filesystem /:contain a file system with errors. check forced ... /:Duplicate blocks found... invoking duplicate block passes Pass 1B: Rescan for duplicate/bad blocks /:Duplicate/bad block(s) in inode 52:/: 1661/: /:Duplicate/bad block(s) in inode 53:/: 1662/: /:Duplicate/bad block(s) in inode 71:/: 1662/: /:Duplicate/bad block(s) in inode 74:/: 1661/: /Pass 1C: Scan directories for inodes with dup blocks /:Pass 1D: Reconciling duplicate blocks /:(There are 4 inodes containing duplicate/bad blocks) /:File /root/.gnome/session/ (inode #74, mod time Sun Apr 21 12:48:48 2002) has 1 duplicate blocks), shared with 1 file(s): /: /root/.gnome/panel.d/default/Applet_4.desktop (inode #52, mod time Sun Apr 21 10:02:00 2002) /: /:UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY ================================================= Below are what I tried with 'fsck' (Repair Filesystem)1# fsck Parallelizing fsck version 1.19 (13-Jul-2000) (Repair Filesystem)2# fsck /root Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Is a directory while trying to open /root (Repair Filesystem)3# fsck /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Read-only file system while trying to open /root/.gnome/session Disk write-protected, use -n option to do read-only (Repair Filesystem)4# fsck -n /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Attemp to read block from filesystem resulted in short read while trying to open /root/.gnome/session Could this be a zero-length partition? ======================================================== _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ===================================================================checking root filesystem /:contain a file system with errors. check forced ... /:Duplicate blocks found... invoking duplicate block passes Pass 1B: Rescan for duplicate/bad blocks /:Duplicate/bad block(s) in inode 52:/: 1661/: /:Duplicate/bad block(s) in inode 53:/: 1662/: /:Duplicate/bad block(s) in inode 71:/: 1662/: /:Duplicate/bad block(s) in inode 74:/: 1661/: /Pass 1C: Scan directories for inodes with dup blocks /:Pass 1D: Reconciling duplicate blocks /:(There are 4 inodes containing duplicate/bad blocks) /:File /root/.gnome/session/ (inode #74, mod time Sun Apr 21 12:48:48 2002) has 1 duplicate blocks), shared with 1 file(s): /: /root/.gnome/panel.d/default/Applet_4.desktop (inode #52, mod time Sun Apr 21 10:02:00 2002) /: /:UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY ================================================= Below are what I tried with 'fsck' (Repair Filesystem)1# fsck Parallelizing fsck version 1.19 (13-Jul-2000) (Repair Filesystem)2# fsck /root Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Is a directory while trying to open /root (Repair Filesystem)3# fsck /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Read-only file system while trying to open /root/.gnome/session Disk write-protected, use -n option to do read-only (Repair Filesystem)4# fsck -n /root/.gnome/session Parallelizing fsck version 1.19 (13-Jul-2000) e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 fsck.ext2: Attemp to read block from filesystem resulted in short read while trying to open /root/.gnome/session Could this be a zero-length partition? ======================================================== _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
commence yan bai quotation:> Below are what I tried with 'fsck' > > (Repair Filesystem)1# fsck > [...] > (Repair Filesystem)2# fsck /root > [...] > (Repair Filesystem)3# fsck /root/.gnome/session > [...] > (Repair Filesystem)4# fsck -n /root/.gnome/sessionYou need to run fsck on the device node for your root file system, "/", not on an actual directory or file in the filesystem itself. Check /etc/fstab on your machine to find out what this node is by looking at the second field to find "/": the device node is listed in the first field. For example, here is the relevant line from *my* /etc/fstab: /dev/hda2 / ext3 defaults,errors=remount-ro 0 1 Here you can see that on my machine the device node for "/" is /dev/hda2. Therefore I would run fsck /dev/hda2. Check your /etc/fstab and run fsck in a similar fashion. -- ///////////////// | | The spark of a pin <sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise.
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, I guess it is because fsck didn't work on the system filesystems after they're mounted to /mnt, so i tried 'fsck /mnt' and 'fsck /mnt/sysimage/dev/sda1', but still failed. I was lost and totally confused. I want to get some helps from man files of fsck and e2fsck, but these files cannot do much helps. For a novel, Linux is quite difficult to follow with... 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. Thanks a lot......> >You usually run fsck on partitions - not on directory paths. If your root >partition is on /dev/hda1 - use the rescue mode on your Linux distribution >and do > >'fsck /dev/hda1' once you have booted into single user mode. The other >method is to plug in your corrupted hdd into a new machine - and ran fsck >on that machine itself; leaving the cd rescue mode + single user mode >things aside. > >HTH. > > > Hi there, > > > > I am very new in linux and met the filesystem problem as described in >the > > following, I tried to use 'fsck' and tried to find some support >documents > > but failed. Your hints and helps are very appreciated. > > > > Millions of thanks, > > > > Annie > > > > The error message is (sorry for it's length, I just want to make it >clear) > > ===================================================================> > checking root filesystem > > /:contain a file system with errors. check forced > > ... > > /:Duplicate blocks found... invoking duplicate block passes >_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
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 mailing list >Ext3-users@redhat.com >https://listman.redhat.com/mailman/listinfo/ext3-users_________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Hi, On Wed, May 15, 2002 at 06:11:43PM +0000, yan bai wrote:> Thank you so much for your helps. > > My problem is when the system is booted, there are some duplicate block > error.Every time?> 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 MESSAGEIs this the full fsck log? Is it the same each time?> So, I tried to use rescue mode and fsck to fix it, but failed.What did you try, and how did it fail? --Stephen
Hi,> > My problem is when the system is booted, there are some duplicate block > > error. > >Every time? >Yes, every time. the error message is the same.> > 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 > >Is this the full fsck log?Several lines followed are 'USE fsck MANUALLY' and then ask me to input the root password.>Is it the same each time?YES.> > So, I tried to use rescue mode and fsck to fix it, but failed. > >What did you try, and how did it fail?I tried to use fsck under the root, but I was told I should use boot instead of directories. so I used the disk to boot into rescue mode, which gave a shell prompt as sh-2.04, the following is what I tried and the message I got. sh-2.04# fsck /dev/sda1 <ENTER> 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/56190 blocks _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
> > 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 > >What version of e2fsck/e2fsprogs are you using, and what distribution >are you using? >I really don't know how to check the version, what is distribution? this is my first time tried to install it.>If this is happening during the boot sequence, most distributions call >use the -p option (preen) to fsck/e2fsck. But in preen mode, the >duplicate blocks scanning doesn't happen; instead fsck, will stop the >boot process and request manual fsck processing. Both Red Hat and >Debian do this. >I am using Red Hat 7.1. Until now, I only heard about rescue/single user mode, what a preen mode use for? Sorry... I was totally lost with my first swim in Linux.>And do you know what options is it is passing to fsck?I didn't use any options. just 'fsck /dev/sda1' _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
I used 'fsck /' and the errors are fixed. Millions of thanks to all of you :)>From: Theodore Ts'o <tytso@mit.edu> >To: yan bai <annie_bai@hotmail.com> >CC: sct@redhat.com, ext3-users@redhat.com >Subject: Re: How To Fix Duplication Block Error? >Date: Thu, 16 May 2002 00:32:58 -0400 > >On Thu, May 16, 2002 at 02:43:17AM +0000, yan bai wrote: > > >> 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 > > > > I tried to use fsck under the root, but I was told I should use boot > > instead of directories. so I used the disk to boot into rescue mode, >which > > gave a shell prompt as sh-2.04, the following is what I tried and the > > message I got. > > > > sh-2.04# fsck /dev/sda1 <ENTER> > > 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/56190 blocks > ^^^^^ > >You aren't checking the right partition. /dev/sda1 is the /boot >partition. You need to check the '/', or root partition. I don't >know what your partition layout is, /dev/sda1 clearly isn't right. >Maybe /dev/sda2? > >You were told to use devices, not directory names, by the way. > >You may want to pick up an intro Linux system administration book. >"Linux for Dummies" isn't a bad intro-level text, although there are >many good books out there who can help up newcomers get up to speed to >Linux. > > - Ted_________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com