public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: cgxu519 <cgxu519@gmx.com>
To: Amir Goldstein <amir73il@gmail.com>, Chengguang Xu <cgxu519@icloud.com>
Cc: Eryu Guan <eguan@redhat.com>, fstests <fstests@vger.kernel.org>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH v5 3/3] generic/471: add syncfs test
Date: Fri, 31 Aug 2018 22:19:16 +0800	[thread overview]
Message-ID: <6c2125c0-5a89-4a67-7a2c-2bebe8dd5b7e@gmx.com> (raw)
In-Reply-To: <63598ea1-8fd3-1003-a5b1-cb177a9380d8@gmx.com>


Hi Amir,

It seems godown will cause side effect on ext4/tune2fs, mount an ext4 
filesystem after running godown,
then tune2fs -l <dev> complains like below. so definitely it will not 
pass d_type check.


[root@x201 xfstests-dev]# tune2fs -l /dev/mapper/test-test1
tune2fs 1.44.2 (14-May-2018)
tune2fs: Superblock checksum does not match superblock while trying to 
open /dev/mapper/test-test1
Couldn't find valid filesystem superblock.


Thanks,
Chengguang


On 08/30/2018 11:12 AM, cgxu519 wrote:
> Hi Amir,
>
> I think I tested both xfs/ext4. Let me have a look at the code for 
> detail.
>
>
> Thanks,
>
> Chengguang
>
>
> On 08/26/2018 10:53 PM, Amir Goldstein wrote:
>> On Fri, Dec 15, 2017 at 9:48 AM Chengguang Xu <cgxu519@icloud.com> 
>> wrote:
>>> Inspired by syncfs bug of overlayfs which does not sync dirtyinodes in
>>> underlying filesystem.
>>> Run syncfs and shutdown filesystem(or underlying filesystem of 
>>> overlayfs)
>>> to check syncfs result.
>>>
>>> Signed-off-by: Chengguang Xu <cgxu519@icloud.com>
>>> ---
>> Hi Chengguang,
>>
>> I just noticed that this test (now generic/474) is skipped for 
>> overlay over ext4
>> for a strange looking reason - it seems that in the overlay_mount() 
>> call from
>> _scratch_cycle_mount() the function hits
>> _notrun "upper fs needs to support d_type".
>>
>> This doesn't happen on my test system with overlay over xfs.
>> Did you happen to test this with overlay over ext4 at the time?
>> Will you have time to look into this?
>>
>> Thanks,
>> Amir.
>

  reply	other threads:[~2018-08-31 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  7:47 [PATCH v5 1/3] common/rc: add scratch shutdown support for overlayfs Chengguang Xu
2017-12-15  7:47 ` [PATCH v5 2/3] common/rc: check syncfs support Chengguang Xu
2017-12-15  7:47 ` [PATCH v5 3/3] generic/471: add syncfs test Chengguang Xu
2018-08-26 14:53   ` Amir Goldstein
2018-08-30  3:12     ` cgxu519
2018-08-31 14:19       ` cgxu519 [this message]
2018-08-31 14:28         ` problem with tune2fs after ext4 godown Amir Goldstein
2018-08-31 14:53           ` cgxu519
2018-09-01 18:42             ` Theodore Y. Ts'o

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=6c2125c0-5a89-4a67-7a2c-2bebe8dd5b7e@gmx.com \
    --to=cgxu519@gmx.com \
    --cc=amir73il@gmail.com \
    --cc=cgxu519@icloud.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-unionfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox