Re: Irritating ext2fs corruption

Brandon S. Allbery KF8NH (allbery@kf8nh.apk.net)
Mon, 03 Aug 1998 20:15:07 -0300

In message <199808032253.SAA26810@dcl.MIT.EDU>, "Theodore Y. Ts'o" writes:
+-----
| It could be something else, but the bug report wasn't terribly clear,
| and this was the best I could come up with. Given that no one else has
| reported anything else like this (and I would get inundated with
| complaints if this was happening in general), I'm for the moment
+--->8

I am getting a dirty root filesystem which contains exactly one deleted
inode with zero dtime on approximately one out of 5 reboots on the Linux
boxes I've been installing for ECE. These are Red Hat 5.0 running 2.0.33
kernel (and until I get a working AFS that's where they stay...) with 300MHz
PII uniprocessor, 128MB RAM (forced via LILO), 8GB HD (Maxtor, don't have
model number on tap but can look it up), other hardware specs available on
request.

So far it's only been an annoyance; no significant space appears to be tied
up via these inodes.

The machines don't use initrd, so I doubt that it's the loopback device as
suggested earlier.

-- 
brandon s. allbery	[os/2][linux][solaris][japh]	 allbery@kf8nh.apk.net
system administrator	     [WAY too many hats]	   allbery@ece.cmu.edu
electrical and computer engineering
carnegie mellon university			   (bsa@kf8nh is still valid.)






-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html