xfs
[Top] [All Lists]

Re: oops: XFS internal error xfs_itobp (Again) / nfsd: non-standard err

To: linux-xfs@xxxxxxxxxxx
Subject: Re: oops: XFS internal error xfs_itobp (Again) / nfsd: non-standard errno : -990
From: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: 05 Jul 2003 17:54:07 +0200
In-reply-to: <1057407266.436.4.camel@bonnie79>
References: <1057407266.436.4.camel@bonnie79>
Reply-to: christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Sat, 2003-07-05 at 14:14, Christian Guggenberger wrote:
> Hi Folks,
>                                                                               
>   
> after Tuesdays crash we had to restore one of the 2 xfs-filesystems from
> tape. (lvm58,0)
> Today afternoon the server went back in production, but ca. 20 min later
> we got oopsen (Kernel 2.4.20 CVS April 2003).
> These oopsen seem to have something to do with:
> nfsd: non-standard errno: -990
> The dmesg output and the oopsen decoded with ksymoops are available at:
> http://homepages.uni-r.de/~guc28561/oops
> http://homepages.uni-r.de/~guc28561/oops.decode

Steve,

I searched the archives and found a post by Nicolas K.
http://marc.theaimsgroup.com/?l=linux-xfs&m=105307906417456&w=2
which shows similar xfs error messages. In reply to that, you said these
messages are cosmetical. So I should not worry too much about them?

We're in a very similar situation as Nicolas was, because after
tuesday's crash many (about 100 or more clients) have nfs stale
filehandles. But it's difficult to reboot them all now, because some
important calculations are running on them...

thanks for (hopefully) some feedback.
Christian



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