xfs
[Top] [All Lists]

Re: still xfs/nfs oopses with 2.6.7-bk17

To: linux-xfs@xxxxxxxxxxx
Subject: Re: still xfs/nfs oopses with 2.6.7-bk17
From: evilninja <evilninja@xxxxxxx>
Date: Wed, 07 Jul 2004 14:18:49 +0200
In-reply-to: <20040707110800.GA15891@infradead.org>
References: <40EBD210.1080307@gmx.net> <20040707110800.GA15891@infradead.org>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 0.6 (X11/20040605)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christoph Hellwig schrieb:
> Does the box actually hang?  The message below just means a memory
> allocation failed.

no, it does not hang. but last time i just wanted to unexport/unmount my
nfs shares, and then the box hung.

<me trying to trigger this one now....>

nope, it does not. i've unmount the nfs shares from the client,
unexported on the server, unmounted on the server, then again
mount/exported/mounted again with no hungs (i do make a difference here
to a lockup: the box always seem to respond to SYSRQ, although the last
time it could not write to disk any more).

now i don't have to reboot :-)
when you say "memory allocation", is this releted to the in-kernel bugs
Chris told me about or do you suspect any hardware memory corruption?
because i don't, the machine was always quite stable...

thanks,
Christian.
- --
BOFH excuse #418:

Sysadmins busy fighting SPAM.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA6+opC/PVm5+NVoYRAl12AJ4hTxdImUFdxSpndUsqW7Nrp0UR4QCg8RUI
jSxvJNx85I+Sf0ZCwjkD33Y=
=2abc
-----END PGP SIGNATURE-----


<Prev in Thread] Current Thread [Next in Thread>