| 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> |
Dave, 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). Kamal -- View this message in context: http://old.nabble.com/xfs-filesystem-corruption-with-kernel-2.6.37-tp34601185p34633803.html Sent from the Xfs - General mailing list archive at Nabble.com. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/2 V2] xfs_logprint: Handle multiply-logged inode fields, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH] xfsdump:fill in bs_forkoff, Ben Myers |
| Previous by Thread: | Re: xfs filesystem corruption with kernel 2.6.37, Dave Chinner |
| Next by Thread: | Re: xfs filesystem corruption with kernel 2.6.37, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |