From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] ext4: check mount's handling for very large s_first_meta_bg
Date: Mon, 24 Apr 2017 17:46:16 +0800 [thread overview]
Message-ID: <58FDC968.7050506@cn.fujitsu.com> (raw)
In-Reply-To: <20170424084339.GL26397@eguan.usersys.redhat.com>
On 2017/04/24 16:43, Eryu Guan wrote:
> On Mon, Apr 24, 2017 at 01:52:26PM +0800, Xiao Yang wrote:
>
>>>> +_require_command "$DEBUGFS_PROG" debugfs
>>>> +_require_ext4_mkfs_feature "bigalloc,meta_bg,^resize_inode"
>>>> +
>>>> +echo "Create ext4 fs and modify first_meta_bg's value"
>>>> +$MKFS_EXT4_PROG -F -b 4096 -O bigalloc,meta_bg,^resize_inode $SCRATCH_DEV 16m>> $seqres.full 2>&1 \
>>>> + || _notrun "Could not create ext4 filesystem"
>>> _scratch_mkfs "-O bigalloc,meta_bg,^resize_inode">> $seqres.full 2>&1
>>>
>>> should be fine, if there're conflicts between MKFS_OPTIONS and these
>>> extra mkfs options _scratch_mkfs will mkfs again only with test-provided
>>> mkfs options.
>>>
>> I will use _scratch_mkfs as you said. However, i still specify 4096 as
>> block size, because debugfs can't set first_meta_bg
>> to 842150400 on RHEL7 when default block size is 1024. Please see the
>> following e2fsprogs bug:
>>
>> commit d36b957b345ee6e4b529be99b8fdc8d3e70ccdc1
>> Author: Darrick J. Wong<darrick.wong@oracle.com>
>> Date: Sat Jan 11 13:58:15 2014 -0500
>>
>> libext2fs: don't always read backup group descriptors on a 1k-block
>> meta_bg fs
> I noticed this too, debugfs failed to open ext4 fs when block size is 1k
> when testing on my rhel7 host. But I think what should be done is fixing
> e2fsprogs on RHEL7 not workarounding the bug in the test code. The test
> is doing nothing wrong, and it 'finds' a bug (test not run).
>
> This leads me to wonder if we should skip this test if debugfs hanppened
> to fail to set first_meta_bg? So that test would fail explicitly (mount
> succeeds unexpectedly) instead of _notrun and being ignored.
>
Hi Eryu
Agreed, we should indicate various bugs instead of ignoring them, so i
will send v3 patch.
Thanks for your comment. :-)
Thanks,
Xiao Yang
> Thanks,
> Eryu
>
>
>
next prev parent reply other threads:[~2017-04-24 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:10 [PATCH 1/2] ext4: check mount's handling for very large s_first_meta_bg Xiao Yang
2017-04-21 10:10 ` [PATCH 2/2] btrfs: use $FILEFRAG_PROG instead of filefrag Xiao Yang
2017-04-24 4:47 ` [PATCH 1/2] ext4: check mount's handling for very large s_first_meta_bg Eryu Guan
2017-04-24 5:52 ` Xiao Yang
2017-04-24 8:43 ` Eryu Guan
2017-04-24 9:46 ` Xiao Yang [this message]
2017-04-24 9:57 ` [PATCH v3] " Xiao Yang
2017-04-24 16:40 ` [PATCH 1/2] " Darrick J. Wong
2017-04-25 1:22 ` Xiao Yang
2017-04-24 6:34 ` [PATCH v2] " Xiao Yang
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=58FDC968.7050506@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/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.