From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair stuck?
Date: Mon, 11 Jul 2011 10:20:14 +1000 [thread overview]
Message-ID: <20110711002014.GB23038@dastard> (raw)
In-Reply-To: <20110710155437.GA19200@apartia.fr>
On Sun, Jul 10, 2011 at 05:54:37PM +0200, Louis-David Mitterrand wrote:
> Hi,
>
> I've lauched xfs_repair on pretty damaged 300G partition and it has been
> stuck for a couple hours at this stage:
>
> bad magic # 0xdbe565b2 in inobt block 19/6115
> expected level 1 got 34602 in inobt block 19/6115
> agi_count 24064, counted 0 in ag 19
> agi_freecount 1375, counted 0 in ag 19
> agi unlinked bucket 0 is 44810432 in ag 19 (inode=2594947264)
> agi unlinked bucket 11 is 44722251 in ag 19 (inode=2594859083)
> agi unlinked bucket 24 is 44811800 in ag 19 (inode=2594948632)
> agi unlinked bucket 32 is 44722400 in ag 19 (inode=2594859232)
> agi unlinked bucket 47 is 65583 in ag 19 (inode=2550202415)
> agi unlinked bucket 48 is 44811056 in ag 19 (inode=2594947888)
> agi unlinked bucket 57 is 45920825 in ag 19 (inode=2596057657)
>
> I tried interrupting and re-launching but it always stops here.
man xfs_repair:
-P Disable prefetching of inode and directory
blocks. Use this option if you find xfs_repair gets
stuck and stops proceeding. Interrupting a stuck
xfs_repair is safe.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-11 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 15:54 xfs_repair stuck? Louis-David Mitterrand
2011-07-11 0:20 ` Dave Chinner [this message]
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=20110711002014.GB23038@dastard \
--to=david@fromorbit.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