All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	Ric Wheeler <rwheeler@redhat.com>
Subject: Re: Do we need dump for ext4?
Date: Thu, 28 Aug 2008 14:48:04 -0400	[thread overview]
Message-ID: <20080828184804.GN26987@mit.edu> (raw)
In-Reply-To: <48B6BD02.3080307@redhat.com>

On Thu, Aug 28, 2008 at 09:58:10AM -0500, Eric Sandeen wrote:
> I was talking to Ric about dump benchmarks, and he was of the impression
> that dump may not be used that often anymore, at least in the
> enterprise.

Many people don't use the dump/restore any more program any more,
that's definitely true.  Whether people use backups (as opposed to
large amounts of RAID) in the enterprise is a different question.  I'm
not so sure about the second question.

So a couple of comments.  First, it's probably not fair to use
different backup programs for the different filesystems.  We probably
want to do one set of comparisons where we use tar for all three.
(Note: not all backup/dump programs are doing the right things with
xattr's, so we're not necessarily comparing programs with completely
identical functionality.)

Secondly, it really wouldn't be hard to update dump/restore for ext4.
It uses libext2fs, so the real problem is that it is explicitly
checking the feature flags.  Removing those checks may be all that is
necessary, given that ext2_block_iterate() still works for
extent-based files.  I just noted BTW that the dump/restore doesn't
seem to be TOTALLY abandoned.  It was last updated in 2006, true, but
there is support for backing up and restoring extended attributes and
ACL's.  I wonder if they broke format compatibility with BSD 4.4
format dump/restore backups when they did it --- and if anyone would
still cares.  :-)

Finally, I suspect most of the problem with using tar is the HTREE
dirent sorting problem.  If we modify tar to sort the directory
entries before emitting the files, and then use that tar across all
the filesystems, I suspect the results would be much more better for
ext3 and ext4.

						- Ted

  reply	other threads:[~2008-08-28 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 14:58 Do we need dump for ext4? Eric Sandeen
2008-08-28 18:48 ` Theodore Tso [this message]
2008-08-28 19:03   ` Ric Wheeler
2008-08-28 20:04     ` Andreas Dilger
2008-08-28 20:35       ` Theodore Tso
2008-08-28 22:23         ` Andreas Dilger
2008-08-28 22:34           ` Theodore Tso
2008-08-28 23:14             ` Andreas Dilger
2008-08-28 19:13   ` Eric Sandeen
2008-08-29 12:36 ` Eric Sandeen
2008-08-29 14:17   ` Theodore Tso
2008-08-29 18:14     ` Eric Sandeen
2008-08-31  2:43   ` Andreas Dilger
2008-09-02 15:52     ` Eric Sandeen

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=20080828184804.GN26987@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.