From: Dave Chinner <david@fromorbit.com>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: XFS: attempt to access beyond end of device
Date: Wed, 21 Dec 2011 09:04:33 +1100 [thread overview]
Message-ID: <20111220220433.GZ23662@dastard> (raw)
In-Reply-To: <CADDb1s1cSM0vS3gnO369hwHwe5dJ0Afaf_6wNVDf0eT-jTvKCg@mail.gmail.com>
On Tue, Dec 20, 2011 at 07:18:15PM +0530, Amit Sahrawat wrote:
> Hi,
>
> While trying to open a file with a large number of extents in append
> mode – it resulted in the below error logs continually.
> I was trying to open the file in append mode, but it showed error, so
> I checked for the extents – it has around 2238 extents. Although, it
The first question you have to get to the bottom of is if there are
only 2238 extents in the file, why is the xfs_bmap output showing
more than that?
> is not repetitive, when I try on next mount and write – it is working
> fine at times.
> Also, the system does not seem to be corrupted. Since, running
> xfs_repair after umount does not show any errors.
Which implies memory corruption. Have you turned on memory poisoning
and the memory leak detection to see if it detects any problems?
What about running with CONFIG_XFS_DEBUG=y? Does that trip any
problems sooner than the corruption is detected?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-12-20 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 13:48 XFS: attempt to access beyond end of device Amit Sahrawat
2011-12-20 22:04 ` Dave Chinner [this message]
2011-12-21 3:40 ` Amit Sahrawat
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=20111220220433.GZ23662@dastard \
--to=david@fromorbit.com \
--cc=amit.sahrawat83@gmail.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox