[867] 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 20:44:15 1994
Date: Tue, 20 Dec 1994 20:43:55 +0500
From: "Theodore Ts'o" <tytso@MIT.EDU>
To: jered@tertius.mit.edu
Cc: nygren@MIT.EDU, jered@MIT.EDU, linux-afs-bugs@MIT.EDU, linux-dev@MIT.EDU,
linux-kernel@vger.rutgers.edu, warlord@MIT.EDU, yonah@MIT.EDU
In-Reply-To: Jered Floyd's message of Tue, 20 Dec 1994 20:24:10 -0500,
<9412210124.AA23211@tertius.mit.edu>
Date: Tue, 20 Dec 1994 20:24:10 -0500
From: jered@tertius.mit.edu (Jered Floyd)
Perhaps this is somehow linked to the fact that on some systems, afsd
will not shutdown?
I don't think so.... Perhaps this is linked to the fact that you're not
supposed to even try to shut afsd down? This is listed as a KNOWN BUG
in the Linux AFS readme file....
* afsd -shutdown doesn't work -- in fact, it will probably crash
your machine.
Vorlon, one of the systems the error was reported on, has 32 MB of
RAM, so I doubt the cause is low memory conditions. I have not seen
any problems with kernel release 1.1.73, but others have reported it.
Low memory conditions may aggrivate the problem, at least data
suggests that.
Well, let's try to correlate other patterns. One of the things which I
do is that I've got my cache set up as its own separate 30 meg
partition. Does anyone else do this? Also, so far it seems to be Linux
AFS specific. If this is the case, perhaps we should take it off the
linux-kernel@vger.rutgers.edu list.....
- Ted
