All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	Ric Wheeler <rwheeler@redhat.com>
Subject: Re: Do we need dump for ext4?
Date: Tue, 02 Sep 2008 10:52:03 -0500	[thread overview]
Message-ID: <48BD6123.9090406@redhat.com> (raw)
In-Reply-To: <20080831024300.GB3392@webber.adilger.int>

Andreas Dilger wrote:
> On Aug 29, 2008  07:36 -0500, Eric Sandeen wrote:
>> at Ric & hch's  request here is tar on the other fs's as well, re-sorted
>>  by level 0 dump time.  I put acp into the mix as well.
>>
>> Oh, and this time I remembered to set the elevator to something sane
>> (noop) for this storage, oops (was cfq last time)
>>
>> Also, this time the dup/tar/acp was written to /dev/null rather than
>> another filesystem.  Interesting how routing to /dev/null alone changed
>> the ranking quite a bit.
> 
> Note that tar has a (questionable) optimization when writing to /dev/null.
> It will NOT open the file or read the data, and just do the filename
> traversal to generate the file list and total file size.  It does this by
> comparing the output file to "/dev/null":

Ah, crud.

-Eric

      reply	other threads:[~2008-09-02 15:53 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
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 [this message]

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=48BD6123.9090406@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@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.