public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: dumpe2fs/dump/restore not working correctly for ext4?
Date: Thu, 4 Mar 2010 16:22:38 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1003041621550.17723@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1003041000140.18322@p34.internal.lan>



On Thu, 4 Mar 2010, Justin Piszcz wrote:

> 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)

And from another day:

p34:/x2/bup/p34/2010-03-01/d# restore -f ../p34-root-2010-03-01.ext4dump 
-r .
Segmentation fault (core dumped)
p34:/x2/bup/p34/2010-03-01/d# ls
a/      core.restore.18181  l2/          nfs/             sbin/     var/
app@    dev/                lib/         opt/             selinux/  x@
appc@   etc/                lib64@       proc/            sys/      x2@
bin/    home/               lost+found/  r1/              tmp/      x3@
boot/   initrd/             media/       restoresymtable  usr/      x4@
cdrom@  l1/                 mnt/         root/            vapp@     x5@
p34:/x2/bup/p34/2010-03-01/d#

Does anyone use dump/restore with ext4?

Justin.


  reply	other threads:[~2010-03-04 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 15:19 dumpe2fs/dump/restore not working correctly for ext4? Justin Piszcz
2010-03-04 21:22 ` Justin Piszcz [this message]
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.1003041621550.17723@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