From: Dave Chinner <david@fromorbit.com>
To: Hans Kraus <hans.w.kraus@gmx.at>
Cc: xfs@oss.sgi.com
Subject: Re: Error (failing assert) in xfs_repair
Date: Wed, 9 Jul 2014 07:03:52 +1000 [thread overview]
Message-ID: <20140708210352.GA22339@dastard> (raw)
In-Reply-To: <trinity-abe1fdb7-c48f-4186-bc36-343c584e19d8-1404830904979@3capp-gmx-bs08>
On Tue, Jul 08, 2014 at 04:48:25PM +0200, Hans Kraus wrote:
> <html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
> <div>Hi,</div>
Hi, can you please use text-only email, not html email?
> <div>I installed xfstools from the git repository on my debian 7 amd64<br/>
> backup server. I got the following assertion error:<br/>
> -------------------------------------------------------------------<br/>
> root@elefant:/home/kraush# xfs_repair -L /dev/vg_stor1/lv_stor1<br/>
What commit did you pull from? Also, a bit more information about
your filesystem and storage will help us:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> Phase 1 - find and verify superblock...<br/>
> - reporting progress in intervals of 15 minutes<br/>
> Phase 2 - using internal log<br/>
> - zero log...<br/>
> - scan filesystem freespace and inode maps...<br/>
> zeroing unused portion of secondary superblock (AG #20)<br/>
> Metadata corruption detected at block 0x2b9e8a001/0x200<br/>
> zeroing unused portion of secondary superblock (AG #16)<br/>
> bad agbno 4274958142 in agfl, agno 16<br/>
> freeblk count 1 != flcount 1806214135 in ag 16<br/>
> bad agbno 131784061 for btbno root, agno 16<br/>
> bad agbno 1628187110 for btbcnt root, agno 16<br/>
> agf_freeblks 2414458438, counted 0 in ag 16<br/>
> agf_longest 1482451932, counted 0 in ag 16<br/>
> agf_btreeblks 4031360978, counted 0 in ag 16<br/>
> bad agbno 1207336865 for inobt root, agno 16<br/>
> agi_count 1835626108, counted 0 in ag 16<br/>
> agi_freecount 952362526, counted 0 in ag 16<br/>
> xfs_repair: scan.c:1579: scan_ag: Assertion `agf_dirty ||<br/>
> agfbuf->b_error != 117' failed.<br/>
So AG 16 has garbage in superblock, the AGF and the AGI. How did
that happen? What went wrong with the storage that lead you to run
xfs_repair?
I think I see the problem, but I first need to confirm what assert
is firing by matching commits.
> root@elefant:/home/kraush#<br/>
> -------------------------------------------------------------------<br/>
> What shall I do to repair the file system (about 16 TB, 88% full,<br/>
> backuppc storage medium).</div>
You'll probably have to wait for a patch to fix the problem. The
sooner I can confirm the assert you hit, the sooner I'll be able to
get you that patch.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-07-08 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 14:48 Error (failing assert) in xfs_repair Hans Kraus
2014-07-08 21:03 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-08 21:50 Hans Kraus
2014-07-08 22:39 ` Dave Chinner
2014-07-13 14:54 Hans Kraus
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=20140708210352.GA22339@dastard \
--to=david@fromorbit.com \
--cc=hans.w.kraus@gmx.at \
--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