From: Dave Chinner <david@fromorbit.com>
To: Daniel Browning <db@kavod.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump segfault
Date: Sat, 16 Feb 2013 17:51:11 +1100 [thread overview]
Message-ID: <20130216065111.GV26694@dastard> (raw)
In-Reply-To: <201302152220.46756.db@kavod.com>
On Fri, Feb 15, 2013 at 10:20:46PM -0800, Daniel Browning wrote:
> Hello folks,
>
> I ran into a segfault while running xfsdump, what should I do
> to find the cause?
xfsrestore segfaulted, not xfsdump. Can you run xfsdump to dump to
a file, then xfsrestore to restore from the file, rather than piping
one into the other? That way we can determine what went wrong first.
i.e dump failing and restore segfaulting when the pipe was broken,
or restore segfaulting and dump stopping because the pipe was
broken....
Once you've worked out which failed, adding "-v verbose" or "-v
debug" flags to the the command line might give us more indication
of what went wrong.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-16 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 6:20 xfsdump segfault Daniel Browning
2013-02-16 6:51 ` Dave Chinner [this message]
2013-02-17 0:06 ` Daniel Browning
2013-02-17 3:47 ` [solved] xfsrestore segfault (was: Re: xfsdump segfault) Daniel Browning
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=20130216065111.GV26694@dastard \
--to=david@fromorbit.com \
--cc=db@kavod.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox