public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Theodore Tso <tytso@mit.edu>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH 0/12] e2fsprogs: add 64-bit support
Date: Tue, 12 Jun 2007 13:25:37 +0200	[thread overview]
Message-ID: <466E82B1.5000709@bull.net> (raw)
In-Reply-To: <20070611231248.GE5181@schatzie.adilger.int>

Andreas Dilger wrote:
> On Jun 11, 2007  18:41 +0200, Valerie Clement wrote:
>> This patchset is also not complete:
>> TODO:
>>   - update code under ext2ed/,
> 
> This code should just be removed entirely.  It is dangerous to use, and
> by including it in e2fsprogs it lends a false sense of credibility to
> the code.  Hopefully most of the functionality here has been incorporated
> into debugfs?
> 
OK.

>> Code compiled, booted and briefly tested on a 20TB device (mkfs, 
>> debugfs, e2fsck, dumpe2fs, filefrag tested)
>> Some non-regression tests also done on ext3 filesystems when compiling 
>> code without _EXT4FS_ option.
> 
> Did you run the "make check" tests?  We've found these invaluable for
> catching regressions.  Ideally there would also be some test cases
> for this support using "lazy_bg", a script to generate the filesystem,
> and conditional upon being able to create sparse files that big.
> 
I missed to mention that some changes have to be done under tests/ too.
Without changes, "make check" fails.

     Valérie

      reply	other threads:[~2007-06-12 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:41 [RFC][PATCH 0/12] e2fsprogs: add 64-bit support Valerie Clement
2007-06-11 23:12 ` Andreas Dilger
2007-06-12 11:25   ` Valerie Clement [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=466E82B1.5000709@bull.net \
    --to=valerie.clement@bull.net \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox