On Feb 21, 2005 17:23 +0000, Yaego Stephen wrote: > Helping a friend fix a computer that was having severe, weird troubles. > Reformatted (from XP) and installed Fedora. Install went ok, on first boot, > however, filesystem was READONLY for some reason. > > Knew hard drive was suspect, so I e2fsck'd it over and over all night long, fall > asleep next to the computer. This morning, Fedora boots fine, login not a > problem, so I shut down and fsck it again, for kicks. > > What happens: > > ---- > > e2fsck keeps complaining about too many illegal blocks in inode 7. > > Clear inode? Yeah > > Error reading block #### (Attempt...) while reading indirect blocks of inode > ##### ignore error? Yeah > > Force rewrite? Yeah > > Restarting e2fsck from the beginning.... > /dev/Volgroup00/LogVol00 contains a file system with errors, check forced. > > Inode 7 has illegal blocks. Clear? Yeah > > *GOTO top* This is a known bug, please update to e2fsprogs-1.36. Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
Attachment:
pgpQ8gEwtVdcm.pgp
Description: PGP signature
_______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
