Messages in this thread | | | Date | Fri, 7 Nov 1997 11:24:42 -0500 (EST) | From | linux kernel account <> | Subject | Re: ext2 errors with 2.0.31 *Me TOO* |
| |
Not to start a scare or anything..
I just found my root paratition on my main webserver majorly foobed EXACTLY the way you are describing.. Badblocks says the hdd is good..
I mean EXACTLY! I was trying to rm -R a bogus .terminfo directory.. And poof! major corruption.. I'm recompiling most of my netutils (which got whiped) as we speak..
Someone far more exped in these sort of kernel problems needs to take a look REAL fast now..
On 6 Nov 1997 toreo-mlist@tihlde.hist.no wrote:
> I'm getting errors with directories that turn into files all of a > sudden. It happened with my /usr/X11R6/lib/X11/fonts/misc so I > couldn't start X this morning, and today I compiled and installed > XEmacs, which make .../etc/toolbar/ into a file consisting of SGML. > > I tried rm -rf /usr/local/lib/xemacs-20.3/ which had the offending > toolbar "file", and now the process eats all of my CPU, refusing to > die. > > Running dmesg tells me: > EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508248 > EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508260 > EXT2-fs warning (device 03:04): empty_dir: bad directory (dir #42990) - no `.' or `..' > > I never had problems with 2.0.31 (or any other kernel) until > recently[1]. What could this be? Hardware failure? > > -Toreo > > [1] At least not that I have noticed. > -- > Surprise, fear, and a ruthless dedication to the Gnu! >
| |