From: David Chinner <dgc@sgi.com>
To: Jay Sullivan <jpspgd@rit.edu>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
Date: Fri, 2 Nov 2007 16:18:34 +1100 [thread overview]
Message-ID: <20071102051834.GM995458@sgi.com> (raw)
In-Reply-To: <3A2120EF-3EB0-4CF1-8C4E-920B9688D51F@rit.edu>
On Thu, Nov 01, 2007 at 10:08:09PM -0400, Jay Sullivan wrote:
> (Sorry if this is a dupe to the list; it has been a long day.)
>
> I have an XFS filesystem that has had the following happen twice in 3
> months, both times an impossibly large block number was requested.
....
Sure sign of a corrupted btree.
> I ran xfs_repair –L on the FS and it could be mounted again, but how
> long until it happens a third time?
<shrug>
What was the problem that xfs_repair fixed?
BTW, why did you run xfs_repair -L?
Also, when it happens next, what does xfs_check tell you is broken?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-11-02 5:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 2:08 xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c Jay Sullivan
2007-11-02 5:18 ` David Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
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
[not found] <B3EDBE0F860AF74BAA82EF17A7CDEDC660BE05A3@svits26.main.ad.rit.edu>
2007-12-21 2:01 ` Jay Sullivan
2008-01-03 15:55 ` Jay Sullivan
2008-08-04 16:55 ` Richard Freeman
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=20071102051834.GM995458@sgi.com \
--to=dgc@sgi.com \
--cc=jpspgd@rit.edu \
--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.