From: Daniel Browning <db@kavod.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump segfault
Date: Sat, 16 Feb 2013 16:06:02 -0800 [thread overview]
Message-ID: <201302161606.02693.db@kavod.com> (raw)
In-Reply-To: <20130216065111.GV26694@dastard>
Thanks for the quick response, Dave.
On Friday 15 February 2013 10:51:11 pm Dave Chinner wrote:
> 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.
Ah, yes, that's right.
> Can you run xfsdump to dump to
> a file, then xfsrestore to restore from the file, rather than piping
> one into the other?
Done. It took a little while since it's a 2.4TiB filesystem. Here is
the last line of the "-v debug" restore (path names scrubbed for
anonymity):
xfsrestore: restoring UNIX domain socket ino 128004852 backup/secondary/backups/firefly/root/backups/[...]/etc/socket
Segmentation fault (core dumped)
[root@betelgeuse ~]# dmesg | tail -n 1
xfsrestore[18838]: segfault at 10 ip 00000033fd8478de sp 00007fcad10a0e00 error 4 in libc-2.12.so[33fd800000+189000]
So it appears that a socket is causing the problem. What should I
try next?
--
DB
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-17 0:06 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
2013-02-17 0:06 ` Daniel Browning [this message]
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=201302161606.02693.db@kavod.com \
--to=db@kavod.com \
--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.