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 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
