All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamal Dasu <kdasu.kdev@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: xfs filesystem corruption with kernel 2.6.37
Date: Fri, 2 Nov 2012 09:34:32 -0700 (PDT)	[thread overview]
Message-ID: <34633803.post@talk.nabble.com> (raw)
In-Reply-To: <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.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-11-02 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 13:45 xfs filesystem corruption with kernel 2.6.37 Kamal Dasu
2012-10-25 22:47 ` Dave Chinner
2012-11-01 19:30   ` Kamal Dasu
2012-11-02  1:27     ` Dave Chinner
2012-11-02 16:34       ` Kamal Dasu [this message]
2012-11-02 22:55         ` Dave Chinner
2012-11-03  1:57           ` Kamal Dasu
2012-11-03 22:25             ` Dave Chinner
2012-11-09 21:18               ` Kamal Dasu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=34633803.post@talk.nabble.com \
    --to=kdasu.kdev@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.