From: Eric Sandeen <sandeen@sandeen.net>
To: Thomas Gutzler <thomas.gutzler@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Corruption of in-memory data detected
Date: Wed, 11 Mar 2009 21:23:10 -0500 [thread overview]
Message-ID: <49B8720E.3070400@sandeen.net> (raw)
In-Reply-To: <49B79586.5060801@gmail.com>
Thomas Gutzler wrote:
> Eric Sandeen wrote:
>> Thomas Gutzler wrote:
...
>>> What can I do to help getting this fixed?
>>>
>> can you make an xfs_metadump of the filesystem in question, and then try
>> an xfs_repair? Capture/save the repair output. If repair finds errors,
>> then perhaps the bug is triggered by bad error checking on a corrupted
>> image, and we might reproduce it w/ the metadump image.
>
> I tried...
>
> root@io:~# xfs_metadump /dev/sda xfs_metadump_sda
> *** glibc detected *** xfs_db: double free or corruption (out):
> 0x00000000017b8000 ***
...
> Aborted
:( what version of xfsprogs?
> 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.
> xfs_repair fixed "bad names" of 4 inodes (see attached log file)
>
> another xfs_metadump /dev/sda xfs_metadump_sda_2 (without -w):
> -rw-r--r-- 1 root root 588261888 2009-03-11 19:23 xfs_metadump_sda_2
>
>> It'd be nice if ubuntu had debug kernel variants (Fedora does this, I
>> dunno about ubuntu) - if you are hitting any kind of memory corruption
>> then a kernel with debug checks enabled might catch it sooner.
>
> I haven't seen any - probably have to build my own debug kernel. Oh joy.
>
> Is the metadump of any use?
it might be, let's see how well it shrinks.
-Eric
> Tom
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-12 2:24 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 [this message]
2009-03-12 5:06 ` Thomas Gutzler
-- 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=49B8720E.3070400@sandeen.net \
--to=sandeen@sandeen.net \
--cc=thomas.gutzler@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.