From: Cedric - Equinoxe Media <cedric@e-m.fr>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs crash
Date: Tue, 6 Nov 2007 10:21:57 +0100 [thread overview]
Message-ID: <20071106092157.GB16694@e-m.fr> (raw)
In-Reply-To: <20071106082632.GU995458@sgi.com>
On 06/11/2007 19:26, David Chinner wrote:
> On Mon, Nov 05, 2007 at 10:51:35PM +0100, Cedric - Equinoxe Media wrote:
> > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file
> > fs/xfs/xfs_alloc.c. Caller 0xffffffff88113b35
> >
> > Call Trace:
> > [<ffffffff88111fcb>] :xfs:xfs_free_ag_extent+0x1a6/0x6b5
> > [<ffffffff88113b35>] :xfs:xfs_free_extent+0xa9/0xc9
> > [<ffffffff8811cf77>] :xfs:xfs_bmap_finish+0xee/0x167
> > [<ffffffff8813c843>] :xfs:xfs_itruncate_finish+0x19b/0x2e0
> > [<ffffffff881543c1>] :xfs:xfs_setattr+0x841/0xe57
>
> Corrupted free space btree, by the look of it. Can you run
> xfs_check on the filesystem and report the output. You can recover
> from this by running xfs_repair.
xfs_check /dev/sda4 :
bad format 2 for inode 2961770479 type 0
bad format 2 for inode 3229517262 type 0
block 20/621714 type unknown not expected
link count mismatch for inode 2961770479 (name ?), nlink 0, counted 1
link count mismatch for inode 3229517262 (name ?), nlink 0, counted 1
the xfs_repair worked perfectly.
Do you have an idea why this corruption happened ?
Thanks.
Cédric
next prev parent reply other threads:[~2007-11-06 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:51 xfs crash Cedric - Equinoxe Media
[not found] ` <20071106082632.GU995458@sgi.com>
2007-11-06 9:21 ` Cedric - Equinoxe Media [this message]
2007-11-06 16:07 ` Cedric - Equinoxe Media
2007-11-06 16:44 ` Justin Piszcz
2007-11-06 17:08 ` Cedric - Equinoxe Media
2007-11-06 20:55 ` David Chinner
2007-11-07 10:58 ` Cedric - Equinoxe Media
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 4:45 Jabir M
2010-05-18 6:02 ` Dave Chinner
2010-05-19 11:26 ` Jabir M
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=20071106092157.GB16694@e-m.fr \
--to=cedric@e-m.fr \
--cc=dgc@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox