public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gutzler <thomas.gutzler@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Corruption of in-memory data detected
Date: Thu, 12 Mar 2009 14:06:55 +0900	[thread overview]
Message-ID: <49B8986F.60009@gmail.com> (raw)
In-Reply-To: <49B8720E.3070400@sandeen.net>

Eric Sandeen wrote:
> Thomas Gutzler wrote:
>>
>> root@io:~# xfs_metadump /dev/sda xfs_metadump_sda
>> *** glibc detected *** xfs_db: double free or corruption (out):
>> 0x00000000017b8000 ***
> 
> ...
> 
>> Aborted
> 
> :(  what version of xfsprogs?

xfsprogs 2.9.8-1
most recent version that comes with ubuntu intrepid.

>> and tried again:
>> root@io:~# xfs_metadump -w /dev/sda xfs_metadump_sda
>> root@io:~# ll xfs_metadump_sda
>> -rw-r--r-- 1 root root 588407296 2009-03-11 19:09 xfs_metadump_sda
>> (where do I upload this to?)
> 
> You can bzip2 it and probably shrink it pretty well (it's sparse).  See
> how big that is, and we can find a place for it.

87M     xfs_metadump_sda_2.bz2
109M    xfs_metadump_sda.bz2

The filesystem has 3.1TB of data on it.
I can put that on our webserver for download or put it somewhere - let
me know what's best.

Tom

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

  reply	other threads:[~2009-03-12  5:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  2:46 Corruption of in-memory data detected Thomas Gutzler
2009-01-02  3:24 ` Eric Sandeen
2009-03-11  2:44   ` Thomas Gutzler
2009-03-11  4:30     ` Eric Sandeen
2009-03-11 10:42       ` Thomas Gutzler
2009-03-12  2:23         ` Eric Sandeen
2009-03-12  5:06           ` Thomas Gutzler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-01  6:44 corruption " Alexandru Cardaniuc
2014-07-01  7:02 ` Dave Chinner
2014-07-01  8:29   ` Alexandru Cardaniuc
2014-07-01  9:38     ` Dave Chinner
2014-07-01 20:13       ` Alexandru Cardaniuc
2014-07-01 21:43         ` 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=49B8986F.60009@gmail.com \
    --to=thomas.gutzler@gmail.com \
    --cc=sandeen@sandeen.net \
    --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