From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: dumpe2fs/dump/restore not working correctly for ext4?
Date: Thu, 4 Mar 2010 10:19:57 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1003041000140.18322@p34.internal.lan> (raw)
Hi,
I need to look into this more obviously and try other dumps etc, but I
even tried extracting a single (smaller) directory and it also segfaulted,
has dump been tested properly with ext4?
# restore -f ../p34-root-2010-03-02.ext4dump -r .
Segmentation fault (core dumped)
(gdb) bt full
#0 0x000000000040d03d in ?? ()
No symbol table info available.
#1 0x000000000040d336 in ?? ()
No symbol table info available.
#2 0x000000000040e1a4 in ?? ()
No symbol table info available.
#3 0x0000000000408d5b in ?? ()
No symbol table info available.
#4 0x0000000000407d92 in ?? ()
No symbol table info available.
#5 0x00007f8df3361abd in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#6 0x0000000000403019 in ?? ()
No symbol table info available.
#7 0x00007fffa98b8bb8 in ?? ()
No symbol table info available.
#8 0x000000000000001c in ?? ()
No symbol table info available.
#9 0x0000000000000005 in ?? ()
No symbol table info available.
#10 0x00007fffa98b8e18 in ?? ()
No symbol table info available.
#11 0x00007fffa98b8e20 in ?? ()
No symbol table info available.
#12 0x00007fffa98b8e23 in ?? ()
No symbol table info available.
#13 0x00007fffa98b8e43 in ?? ()
No symbol table info available.
#14 0x00007fffa98b8e46 in ?? ()
No symbol table info available.
#15 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)
Justin.
next reply other threads:[~2010-03-04 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 15:19 Justin Piszcz [this message]
2010-03-04 21:22 ` dumpe2fs/dump/restore not working correctly for ext4? Justin Piszcz
2010-03-04 22:17 ` tytso
2010-03-04 22:21 ` Justin Piszcz
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=alpine.DEB.2.00.1003041000140.18322@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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