[Top] [All Lists]

Re: xfs filesystem corruption with kernel 2.6.37

To: xfs@xxxxxxxxxxx
Subject: Re: xfs filesystem corruption with kernel 2.6.37
From: Kamal Dasu <kdasu.kdev@xxxxxxxxx>
Date: Fri, 2 Nov 2012 09:34:32 -0700 (PDT)
In-reply-to: <20121102012728.GT29378@dastard>
References: <CAC=U0a2T_J9Y6WzvWyFfbBSDy__Pr7f4gfQBie2o0VhAm2jCaQ@xxxxxxxxxxxxxx> <20121025224713.GF29378@dastard> <34630253.post@xxxxxxxxxxxxxxx> <20121102012728.GT29378@dastard>

I see the following. On two different systems with the same want= value.
Does not seem like a random corruption.

>attempt to access beyond end of device
> sda2: rw=0, want=33792081130943048, limit=3147132

> > Track down where those stray upper bits in the block numbers are
> > coming from, and you'll have your answer. 

Where would be the best place to put this check. 

Also on a XFS DEBUG all the asserts seem to be in the unlink (delete path).


View this message in context: 
Sent from the Xfs - General mailing list archive at Nabble.com.

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