From: Richard Freeman <freemanrich@gmail.com>
To: linux-xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
Date: Mon, 4 Aug 2008 16:55:41 +0000 (UTC) [thread overview]
Message-ID: <loom.20080804T165100-165@post.gmane.org> (raw)
In-Reply-To: C8CBE79A-8D1D-4151-ADFD-2C9400FAF356@rit.edu
Jay Sullivan <jpspgd <at> rit.edu> writes:
>
> Today I upgraded to the latest stable kernel in Gentoo (2.6.23-r3) and
> I'm still on xfsprogs 2.9.4, also the latest stable release. A few
> hours after rebooting to load the new kernel, I saw the following in
> dmesg:
>
> ####################
> attempt to access beyond end of device
> dm-0: rw=0, want=68609558288793608, limit=8178892800
I just started getting these on an ext3 filesystem also on gentoo, with the
latest stable kernel. I suspect there is an lvm bug of some kind that is
responsible. I ran an e2fsck on the filesystem and managed to corrupt not
only that filesystem, but also several others on the same RAID. I'm probably
going to have to try to salvage what I can from the no-longer-booting system
and rebuild from scatch/backups.
Either lvm has some major bug, or somehow e2fsck is bypassing the lvm layer
and writing directly to the drives. It shouldn't be possible to write to one
logical volume and modify data stored in a different logical volume on the
same md raid-5 device. A check of the underlying RAID turns up no issues - I
suspect the problem is in the lvm layer.
Googling around for "access beyond end of device" turns up other reports of
similar issues. Obviously the problem is rare.
next prev parent reply other threads:[~2008-08-07 21:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B3EDBE0F860AF74BAA82EF17A7CDEDC660BE05A3@svits26.main.ad.rit.edu>
2007-12-21 2:01 ` xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c Jay Sullivan
2008-01-03 15:55 ` Jay Sullivan
2008-08-04 16:55 ` Richard Freeman [this message]
2009-02-24 13:04 Federico Sevilla III
2009-02-24 22:46 ` Dave Chinner
2009-02-25 10:00 ` Federico Sevilla III
2009-02-25 11:51 ` Michael Monnerie
2009-02-25 18:47 ` Federico Sevilla III
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 2:08 Jay Sullivan
2007-11-02 5:18 ` David Chinner
2007-11-01 20:06 Jay Sullivan
2007-11-02 2:14 ` Eric Sandeen
2007-11-02 2:22 ` Jay Sullivan
2007-11-02 2:30 ` Eric Sandeen
2007-11-02 9:07 ` Ralf Gross
2007-11-02 16:10 ` Eric Sandeen
2007-11-02 14:00 ` Jay Sullivan
2007-11-02 14:49 ` Jay Sullivan
2007-11-14 15:05 ` Jay Sullivan
2007-11-15 3:26 ` Eric Sandeen
2007-11-02 4:37 ` Timothy Shimmin
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=loom.20080804T165100-165@post.gmane.org \
--to=freemanrich@gmail.com \
--cc=linux-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