public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tapani Tarvainen <tapani.j.tarvainen@jyu.fi>
To: xfs@oss.sgi.com
Subject: "This is a bug."
Date: Thu, 10 Sep 2015 12:18:34 +0300	[thread overview]
Message-ID: <20150910091834.GC24937@tehanu.it.jyu.fi> (raw)

Hi,

After a rather spectacular crash we've got an xfs filesystem
in unrepairable state: mount fails with "Structure needs cleaning",
xfs_repair without options refuses to work (asks to mount first),
and xfs_repair -L stopped with

corrupt dinode 2151195170, extent total = 1, nblocks = 0.  This is a bug.
Please capture the filesystem metadata with xfs_metadump and
report it to xfs@oss.sgi.com.

I tried to dump the metadata and it failed, too:

# xfs_metadump /dev/sdata1/data1 /data2/tmp/data1_metadump
xfs_metadump: cannot init perag data (117)
*** glibc detected *** xfs_db: double free or corruption (!prev): 0x0000000003361000 ***
======= Backtrace: ========= 
[...]
Aborted


At this point I'm going to give up trying to recover the data
(recreate filesystem and restore from backup), but if you want to
analyze it to find the bug, I have enough spare disk space to keep a
copy for a while (took lvm snapshot of it before recovery attempt,
could dd it to another location).

The machine is running Debian Wheezy (7.8),
kernel 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u1 x86_64 GNU/Linux,
xfsprogs version 3.1.7+b1.
And the filesystem is 6TB in size.

If you want to take a look, please let me know what I can do to help.

Thank you,

-- 
Tapani Tarvainen

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2015-09-10  9:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  9:18 Tapani Tarvainen [this message]
2015-09-10 10:31 ` "This is a bug." Tapani Tarvainen
2015-09-10 11:53   ` Emmanuel Florac
2015-09-10 12:05     ` Tapani Tarvainen
2015-09-10 11:48 ` Emmanuel Florac
2015-09-10 11:55   ` Tapani Tarvainen
2015-09-10 12:30     ` Tapani Tarvainen
2015-09-10 12:36       ` Brian Foster
2015-09-10 12:54         ` Tapani Tarvainen
2015-09-10 13:01           ` Brian Foster
2015-09-10 13:05             ` Tapani Tarvainen
2015-09-10 14:51               ` Brian Foster
2015-09-10 15:05                 ` Brian Foster
2015-09-10 17:52                   ` Tapani Tarvainen
2015-09-10 18:01                     ` Tapani Tarvainen
2015-09-10 17:31                 ` Tapani Tarvainen
2015-09-10 17:55                   ` Brian Foster
2015-09-10 18:03                     ` Tapani Tarvainen
2015-09-10 18:33                       ` Brian Foster
2015-09-11  6:19                         ` Tapani Tarvainen
2015-09-11  0:12                       ` Eric Sandeen

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=20150910091834.GC24937@tehanu.it.jyu.fi \
    --to=tapani.j.tarvainen@jyu.fi \
    --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