From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: linux-ext4@vger.kernel.org
Subject: Dump/restore not functional on ext4
Date: Sun, 15 Feb 2009 13:04:48 +0100 [thread overview]
Message-ID: <87d4djucrj.fsf@atlas.lan> (raw)
Hello list!
Cca 2 months ago I switched to ext4 on all of my machines/partitions and
has been a very happy customer ever since. Except one little thing...
Dump/restore is not working on ext4 filesystem. Actually... it's even
worse, it appears that it's working, but if you try to restore files,
only garbage gets restored. Obviously wrong fs blocks are dumped (or
restored) rendering backup completely useless.
As this could be bug in e2fslibs, I'm reporting all versions relevant:
Distribution: Debian sid
Kernel: 2.6.28 Linus virgin (FS made with 2.6.28-rc9)
File system: ext4 (w/ extents, w/o xattr)
e2fsprogs: 1.41.3-1
dump: 0.4b41-6
And I'm slightly dissapointed that there's so little users of dump, it
has a feature set that I can't replace with any other backup system (I
tried). Or is it maybe that ext4 is slow to adapt?
This was also reported as Debian bug #511651 a month ago, but without
any progress so far, so I decided to report it to this list, too (I'm
not subscribed).
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511651
Thanks for any help you can provide!
--
Zlatko
reply other threads:[~2009-02-15 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87d4djucrj.fsf@atlas.lan \
--to=zlatko.calusic@iskon.hr \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).