From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: Do we need dump for ext4?
Date: Fri, 29 Aug 2008 13:14:30 -0500 [thread overview]
Message-ID: <48B83C86.2010507@redhat.com> (raw)
In-Reply-To: <20080829141703.GC30887@mit.edu>
Theodore Tso wrote:
> Just for completeness's sake, can you apply the following patch to
> dump, and then try doing a benchmark run using dump on ext4?
>
> I'm curious how it would compare.
>
> - Ted
>
> Index: dump-0.4b41/dump/traverse.c
> ===================================================================
> --- dump-0.4b41.orig/dump/traverse.c
> +++ dump-0.4b41/dump/traverse.c
> @@ -157,14 +157,6 @@ int dump_fs_open(const char *disk, ext2_
> retval = EXT2_ET_UNSUPP_FEATURE;
> ext2fs_close(*fs);
> }
> - else if ((retval = es->s_feature_incompat &
> - ~(EXT2_LIB_FEATURE_INCOMPAT_SUPP |
> - EXT3_FEATURE_INCOMPAT_RECOVER))) {
> - msg("Unsupported feature(s) 0x%x in filesystem\n",
> - retval);
> - retval = EXT2_ET_UNSUPP_FEATURE;
> - ext2fs_close(*fs);
> - }
> else {
> if (es->s_feature_compat &
> EXT3_FEATURE_COMPAT_HAS_JOURNAL &&
Yep, will do. Should have included it in the run (in last, in case
anything exploded...) :)
I'm traveling but will give it a shot soon.
-Eric
next prev parent reply other threads:[~2008-08-29 18:16 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 [this message]
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=48B83C86.2010507@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=tytso@mit.edu \
/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.