This is a bug. #emerge rsync #emerge -UDp world
Upgrade to baselayout 1.8.6.10-r1 and the next time your root file system is checked/modified, gentoo will just reboot instead of giving this confusing error message. Some other very nice fixes in baselayout too! On Sun, 2003-09-14 at 12:03, Dmitry Suzdalev wrote: > Hello! > > Today my ext3 filesystem had gone 30 days w/o checking and check was forced > :). When the checking process ended, it said something usual about > fragmentation and number of blocks, and then: > > * Filesystem couldn't be fixed [!!] > > And this is the only error message I can see. > What does this mean and where can I look for error that occured? Any kind of > log? Syslog starts later so I can't rely on /var/log/*. > > Upon the next reboot, all goes okay, e2fsck says that FS is clean. Same result > if I issue "e2fsck /dev/hda4" command manually. > How can I catch this nasty error now? > > No strange noises from HDD, no read/write problems, but this is second time I > get this error. > > Anyone had something like this? > > TIA, > Dmitry. -- Karl Huysmans <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
