xfs
[Top] [All Lists]

Re: XFS internel errors (oops?)

Subject: Re: XFS internel errors (oops?)
From: Michael Loftis <mloftis@xxxxxxxxx>
Date: Wed, 01 Oct 2003 15:36:22 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1065043818.26615.376.camel@xxxxxxxxxxxxxxxxxxxx>
References: <126430627.1065020909@[10.1.2.77]> <1065043818.26615.376.camel@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Thanks, I appreciate the response...I have had this trace (or similar ones) happen before, but they seemed to have stopped after we xfs_repair-ed during one long planned downtime (actually went longer, lots of smallish files, webserver store)...

I'm due for another round of kernel upgrades in a couple months for that box and other sensitive ones, I'll be sure and catch the latest XFS patches again when I do.

--On Wednesday, October 01, 2003 4:30 PM -0500 Steve Lord <lord@xxxxxxx> wrote:

On Wed, 2003-10-01 at 16:08, Michael Loftis wrote:
OK at about 3AM this morning under heavy-ish load one of the remaining
NFS  fileservers with XFS quipped the below...

It's still..running....I don't know if that's a good thing or not.
We're looking at about 160GB of storage, and this sysem is extremely
downtime sensitive, I can't just take the thing offline...


This is a stale/bad nfs file handle, some debugging info added to
xfs was a but gratuitous in this case and has been turned off
unless you crack up some debug options. Should not have caused
any harm.

Steve


--
Undocumented Features quote of the moment...
"It's not the one bullet with your name on it that you
have to worry about; it's the twenty thousand-odd rounds
labeled `occupant.'"
  --Murphy's Laws of Combat


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