lkml.org 
[lkml]   [1997]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Serious ext2fs problem

I've a different problem with the ext2fs. Here is what I did.

My linux source is messed up during patching (dying scsi disk,
return scsi error _while_ patching and patch just die in the middle
of it). The story just begins here.

So I download the newest linux-2.1.20 (I'm running 2.1.17) and
I did a 'rm -rf *' under /usr/src/linux.

Trouble is it rm was killed by memory exhausted error (I've 20M
plus 50M swap) with some "pmd" error. Sorry that I did write that
down.

Then my system locked. Push the red button and e2fsck keeps finding
a lot of duplicate/bad inode. I've to run more than a 3 time e2fsck
to fix those.

And finally, all those "lost" files and directories appears in
/usr/lost+found.

Trying to remove the files without problem. But while removing those
"#61485" type directories caused this message

EXT2-fs warning (device 08:09): empty_dir: bad directory (dir #61485) -
no `.' or `..'

The rm process is stuck again. And /usr has basically turn into read-only
filesystem.

I'm using libc 5.4.17, e2fsck 1.06, rm and rmdir is fileutil-3.12. I
should have used fileutil-3.14 but it's in different bin directory...
Any idea?

Thanks.

Chris





\
 
 \ /
  Last update: 2005-03-22 13:38    [W:0.133 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site