From: tytso@mit.edu
To: Eric Sandeen <sandeen@redhat.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: dump/restore not supported for ext4
Date: Thu, 4 Mar 2010 23:38:22 -0500 [thread overview]
Message-ID: <20100305043822.GA5747@thunk.org> (raw)
In-Reply-To: <4B90419E.20309@redhat.com>
On Thu, Mar 04, 2010 at 05:26:22PM -0600, Eric Sandeen wrote:
> Justin Piszcz wrote:
> > Hi,
> >
> > I should have researched it more:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511651
> > https://lists.ubuntu.com/archives/universe-bugs/2009-June/098729.html
> >
> > Looks like it's broken, I agree with the reporters, dump should abort if
> > it is dealing with an ext4 filesystem, since you cannot restore data
> > from an ext4 dump.
>
> does dump still read the mounted block device directly? I'm not familiar
> with the internals (need to look, I guess) but if so, I wonder how that
> + delalloc get along...
It does read the mounted block device directly, and so it's certainly
not a _recommended_ way to back up your ext4 filesystem. It should
work, though, since it just uses the high-level libext2fs functions
--- and a while back, I think I did a quick test and found that it
really did work. So I'm not sure what broke, but it might not be that
hard to fix. That being said, it may not be worth it to fix it, since
with delayed allocation, backups using dump will be even more
unreliable than they were before.
- Ted
next prev parent reply other threads:[~2010-03-05 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 22:05 dump/restore not supported for ext4 Justin Piszcz
2010-03-04 23:26 ` Eric Sandeen
2010-03-05 4:38 ` tytso [this message]
2010-03-05 6:23 ` Gertjan van Wingerde
2010-03-05 14:27 ` Justin Piszcz
2010-03-05 16:21 ` Bdale Garbee
2010-03-08 11:03 ` Stelian Pop
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=20100305043822.GA5747@thunk.org \
--to=tytso@mit.edu \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).