[865] in SIPB_Linux_Development
Re: ext2 files getting unlinked under 1.1.7[23] and other things
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Tue Dec 20 17:32:44 1994
Date: Tue, 20 Dec 1994 17:32:24 +0500
From: "Theodore Ts'o" <tytso@MIT.EDU>
To: Erik Nygren <nygren@MIT.EDU>
Cc: linux-kernel@vger.rutgers.edu, linux-afs-bugs@MIT.EDU, warlord@MIT.EDU,
yonah@MIT.EDU, jered@MIT.EDU, linux-dev@MIT.EDU
In-Reply-To: Erik Nygren's message of Tue, 20 Dec 1994 16:51:30 -0500,
<199412202151.QAA00735@foundation.mit.edu>
I use Linux AFS, and I haven't seen any of these problems --- on the
other hand, I have 20 megs of memory in my laptop.
It would be useful to try to see if this problem is related to
low-memory availability situations. If the problem is that ext2fs
doesn't deal with certain low memory situations well, then once we know
that, we can try to duplicate the problem without using Linux AFS, and
then report it to the ext2 developers.
>I don't think .bash_history will work all that well as
>a setuid character device.... :-/ Anyways,
>this stayed like this for a short while and then
>suddenly returned to normal! I have no idea what caused
>this sudden change of heart as I didn't reboot or fsck or
>anything. The inode numbers of these are in the 6432[0-9] range
Sounds like a disk buffer containing part of the inode table got
corrupted somehow. Since you didn't modify it, it eventually got
flushed out, and "returned to normal". If you had tried to modify an
inode in that range, it would have gotten written out to disk, and
therefore those inodes would have disappeared.
Now, if someone could make this consistently happen, either with or
without Linux AFS, that would be great....
- Ted
