From: Eric Sandeen <sandeen@sandeen.net>
To: Johannes Weydt <Johannes.Weydt@EMEA.NEC.COM>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Cc: "'dwdos@hpce.nec.com'" <dwdos@hpce.nec.com>,
"Reiter Manuel" <manuel.reiter@dwd.de>,
"Frühauf Andreas" <Andreas.Fruehauf@dwd.de>
Subject: Re: xfs_metadump
Date: Fri, 12 Jun 2015 08:26:23 -0500 [thread overview]
Message-ID: <557ADDFF.8080809@sandeen.net> (raw)
In-Reply-To: <51AEB2C95D121A4D983B13981120AC65853860@EX10MBX01.EU.NEC.COM>
On 6/12/15 7:49 AM, Johannes Weydt wrote:
> Hello SGI,
>
>
>
> We experienced a I/O error on one of our XFS filesystems, xfs_repair –n advised to
>
> “Please capture the filesystem metadata with xfs_metadump and
>
> report it to xfs@oss.sgi.com <mailto:xfs@oss.sgi.com>.”
> before it ended with a Segmentation fault.
>
> The metadata is almost 3GB big, how do you recommend to transfer the file?
did you try to compress it?
> Do you have an open FTP for us?
> Also attached are some console outputs of first investigation attempts.
>
> Log of xfs_repair –n (1^st run)
What version? Have you tried the latest version?
oh:
> xfsprogs is installed in version:
>
> root@daw1:/localtmp # rpm -qa |grep xfsprogs
>
> xfsprogs-3.1.1-10.el6.x86_64
>
> Can you advise something?
If this is a RHEL6 box, have you contacted Red Hat support?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-12 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 12:49 xfs_metadump Johannes Weydt
2015-06-12 13:26 ` Eric Sandeen [this message]
2015-06-12 13:58 ` xfs_metadump Johannes Weydt
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=557ADDFF.8080809@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Andreas.Fruehauf@dwd.de \
--cc=Johannes.Weydt@EMEA.NEC.COM \
--cc=dwdos@hpce.nec.com \
--cc=manuel.reiter@dwd.de \
--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.