From: Marc Lehmann <schmorp@schmorp.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair 3.1.4/3.1.5: fatal error -- couldn't malloc dir2 buffer data
Date: Sat, 6 Aug 2011 19:54:28 +0200 [thread overview]
Message-ID: <20110806175428.GA1900@schmorp.de> (raw)
In-Reply-To: <20110806141241.GF3162@dastard>
On Sun, Aug 07, 2011 at 12:12:41AM +1000, Dave Chinner <david@fromorbit.com> wrote:
> > this is 3.1.5 - 3.1.4 simply segfaults. using ltrace shows this as
> > last call to malloc:
> >
> > malloc(18446744073708732928) = NULL
> >
> > I think thats a bit unreasonable of xfs_repair :)
>
> Can you share a metadump of the image in question?
I can, but unfortunately, it's fixed itself in the meantime:
I wanted to make a copy of the image, and mounted it read-write. I stat'ed
all files inside (which worked) and then rsynced all files out.
Then I unmounmted it and re-ran xfs_repair
(http://ue.tst.eu/3cbc07150eb6b69c63361937c6c3044f.txt) which got much
farther, but failed with the same error.
Then I re-ran xfs_repair one last time, which ran through without any "error"
messages.
An xfs_metadata -o is here (gzipped):
http://data.plan9.de/smoker-chroot.bin.gz
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-06 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 12:17 xfs_repair 3.1.4/3.1.5: fatal error -- couldn't malloc dir2 buffer data Marc Lehmann
2011-08-06 14:12 ` Dave Chinner
2011-08-06 17:54 ` Marc Lehmann [this message]
2011-08-06 23:39 ` Dave Chinner
2011-08-08 0:29 ` Dave Chinner
2011-08-08 17:49 ` Marc Lehmann
2011-08-08 23:45 ` Dave Chinner
2011-08-06 17:27 ` Roger Willcocks
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=20110806175428.GA1900@schmorp.de \
--to=schmorp@schmorp.de \
--cc=david@fromorbit.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.