From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: xfs@oss.sgi.com
Subject: xfs_repair stuck?
Date: Sun, 10 Jul 2011 17:54:37 +0200 [thread overview]
Message-ID: <20110710155437.GA19200@apartia.fr> (raw)
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.
Any idea?
Thanks,
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-07-10 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 15:54 Louis-David Mitterrand [this message]
2011-07-11 0:20 ` xfs_repair stuck? Dave Chinner
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=20110710155437.GA19200@apartia.fr \
--to=vindex+lists-xfs@apartia.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