From: "Amir G." <amir73il@users.sourceforge.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, sandeen@redhat.com, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, sergey57@gmail.com,
Amir Goldstein <amir73il@users.sf.net>
Subject: Re: [PATCH v2] xfstests: add support for ext4dev FSTYP
Date: Thu, 2 Jun 2011 05:33:34 +0300 [thread overview]
Message-ID: <BANLkTimbPWfOJKq6er4mnSYNPcx6VHLcrw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=sV5=PyZvNSd=DGNW-V84=27d7Yw@mail.gmail.com>
On Thu, Jun 2, 2011 at 5:16 AM, Amir G. <amir73il@users.sourceforge.net> wrote:
> On Thu, Jun 2, 2011 at 2:28 AM, Dave Chinner <david@fromorbit.com> wrote:
>> On Wed, Jun 01, 2011 at 03:56:52PM +0300, amir73il@users.sourceforge.net wrote:
>>> From: Amir Goldstein <amir73il@users.sf.net>
>>>
>>> From: Amir Goldstein <amir73il@users.sf.net>
>>>
>>> blkid knows to identify the ext4dev FSTYP of a partition that was
>>> formatted with mkfs.ext4dev.
>>> quota tools and various util-linux utils are also aware of ext4dev,
>>> so ext4dev shares the same capabilities as ext4.
>>>
>>> Signed-off-by: Amir Goldstein <amir73il@users.sf.net>
>>> Tested-by: Sergey Ivanov <sergey57@gmail.com>
>>> ---
>>> ext4dev is used to test experimental ext4 code in mutual existance
>>> with production ext4 code on the same system.
>>>
>>> Specifically, ext4 snapshots code is available for testing as a
>>> stand-alone ext4dev module for Fedora 15 and Ubuntu 11.4
>>> (see http://next3.sf.net).
>>>
>>> v1 -> v2:
>>> - undo change of fsck -t $FSTYP to fsck.$FSTYP
>>>
>>> common.defrag | 2 +-
>>> common.quota | 4 ++--
>>> common.rc | 10 +++++-----
>>> 3 files changed, 8 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/common.defrag b/common.defrag
>>> index 1bcf01d..4850803 100644
>>> --- a/common.defrag
>>> +++ b/common.defrag
>>> @@ -26,7 +26,7 @@ _require_defrag()
>>> xfs)
>>> DEFRAG_PROG=/usr/sbin/xfs_fsr
>>> ;;
>>> - ext4)
>>> + ext4|ext4dev)
>>> DEFRAG_PROG=/usr/bin/e4defrag
>>> ;;
>>> *)
>>> diff --git a/common.quota b/common.quota
>>> index 3c87ce1..b6d5f16 100644
>>> --- a/common.quota
>>> +++ b/common.quota
>>> @@ -29,7 +29,7 @@ _require_quota()
>>> [ -n $QUOTA_PROG ] || _notrun "Quota user tools not installed"
>>>
>>> case $FSTYP in
>>> - ext2|ext3|ext4|reiserfs)
>>> + ext2|ext3|ext4|ext4dev|reiserfs)
>>> if [ ! -d /proc/sys/fs/quota ]; then
>>> _notrun "Installed kernel does not support quotas"
>>> fi
>>> @@ -237,7 +237,7 @@ _check_quota_usage()
>>> # Sync to get delalloc to disk
>>> sync
>>> VFS_QUOTA=0
>>> - if [ $FSTYP = "ext2" -o $FSTYP = "ext3" -o $FSTYP = "ext4" -o $FSTYP = "reiserfs" ]; then
>>> + if [ $FSTYP = "ext2" -o $FSTYP = "ext3" -o $FSTYP = "ext4" -o $FSTYP = "ext4dev" -o $FSTYP = "reiserfs" ]; then
>>> VFS_QUOTA=1
>>> quotaon -f -u -g $SCRATCH_MNT 2>/dev/null
>>> fi
>>
>> Perhaps this should be changes to a case statement?
>>
>
> you're making me go to v3 in such a trivial patch, but ok, I'll do it ;-)
>
I rechecked the fsck -t ext4dev vs. fsck.ext4dev.
fsck -t ext4dev doesn't work for me :-(
Sergey has a newer version of util-linux-ng
see:
amir@qalab:~/xfstests$ sudo fsck -t ext4dev -nf /dev/sda5
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda5 has unsupported feature(s): FEATURE_C7 FEATURE_C8 FEATURE_R7
e2fsck: Get a newer version of e2fsck!
amir@qalab:~/xfstests$ sudo fsck.ext4dev -nf /dev/sda5
e2fsck 1.41.14-next3-1.0.13-7 (24-May-2011)
Checking snapshots: 1,done
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 6596/6561792 files (3.6% non-contiguous), 1242522/26216064 blocks
amir@qalab:~/xfstests$
What do you thing, Dave?
Should xfstests rely on a non-buggy generic fsck util, or just
implement it's own
non-buggy generic fsck (invoke fsck.$FSTYP directly)
I am running a recent system (Ubuntu 11.4) and I don't thing that upgrading
util-linux should be a requirement for xfstests to work.
>> Cheers,
>>
>> Dave.
>>
>> --
>> Dave Chinner
>> david@fromorbit.com
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-02 2:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 12:56 [PATCH v2] xfstests: add support for ext4dev FSTYP amir73il
2011-06-01 23:28 ` Dave Chinner
2011-06-02 2:16 ` Amir G.
2011-06-02 2:33 ` Amir G. [this message]
2011-06-02 3:08 ` Dave Chinner
2011-06-02 3:49 ` Amir G.
2011-06-02 6:40 ` Dave Chinner
2011-06-02 7:11 ` Amir G.
2011-06-02 12:10 ` Lukas Czerner
2011-06-02 13:17 ` Amir G.
2011-06-02 14:44 ` Lukas Czerner
2011-06-02 7:16 ` Amir G.
2011-06-02 14:59 ` Eric Sandeen
2011-06-02 17:22 ` Andreas Dilger
2011-06-03 0:36 ` Ted Ts'o
2011-06-03 3:26 ` Eric Sandeen
2011-06-03 4:59 ` Amir G.
2011-06-03 5:06 ` Eric Sandeen
2011-06-03 17:21 ` Amir G.
2011-06-03 2:01 ` Dave Chinner
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=BANLkTimbPWfOJKq6er4mnSYNPcx6VHLcrw@mail.gmail.com \
--to=amir73il@users.sourceforge.net \
--cc=amir73il@users.sf.net \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sergey57@gmail.com \
--cc=xfs@oss.sgi.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 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).