From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair v3.1.6 - Segmentation fault AND XFS internal error xfs_btree_check_sblock
Date: Mon, 17 Oct 2011 17:08:00 +0200 [thread overview]
Message-ID: <4E9C44D0.7040904@cape-horn-eng.com> (raw)
In-Reply-To: <20111017150236.GA7056@infradead.org>
On 10/17/2011 05:02 PM, Christoph Hellwig wrote:
> Can you send me a metadump of the filesystem? It is generated using the
> xfs_metadump tool from xfsprogs, and obsfucates the file names used.
> Feel free to upload it to a private place and send the link and/or
> directly send it to me if you don't want to see it on the list.
>
Hi, thanks for responding!
xfs_metadump also throws a Segmentation fault, both v3.1.6 and v3.1.4 :
# /opt/xfsprogs-3.1.6/sbin/xfs_metadump /dev/sdb1 xfs_metadump_dev-sdb1.log
*** stack smashing detected ***: xfs_db terminated
/opt/xfsprogs-3.1.6/sbin/xfs_metadump: line 31: 22049 Segmentation fault xfs_db$DBOPTS -F -i -p xfs_metadump -c "metadump$OPTS $2" $1
I will send the gzipped metadump file to you directly.
Many thanks,
Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-17 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 14:42 xfs_repair v3.1.6 - Segmentation fault AND XFS internal error xfs_btree_check_sblock Richard Ems
2011-10-17 15:02 ` Christoph Hellwig
2011-10-17 15:08 ` Richard Ems [this message]
2011-10-17 22:52 ` Dave Chinner
2011-10-18 9:58 ` Richard Ems
2011-10-24 16:55 ` Michael Monnerie
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=4E9C44D0.7040904@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--cc=hch@infradead.org \
--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