From: "zhangyi (F)" <yi.zhang@huawei.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: fstests <fstests@vger.kernel.org>, Eryu Guan <guaneryu@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>, Miao Xie <miaoxie@huawei.com>
Subject: Re: [PATCH v2 3/4] overlay: add fsck.overlay stress test
Date: Thu, 18 Oct 2018 11:48:52 +0800 [thread overview]
Message-ID: <1d2c7919-64d6-5e2e-9908-5729d4e561df@huawei.com> (raw)
In-Reply-To: <CAOQ4uxj_6CA1thOwwXOCtgZ3+oBW9g_sH=RY-Np5CmJkdH_+vA@mail.gmail.com>
On 2018/10/16 18:07, Amir Goldstein Wrote:
> On Tue, Oct 16, 2018 at 10:32 AM zhangyi (F) <yi.zhang@huawei.com> wrote:
>>
>> Introduce a test case for fsck.overlay which runs on the underlying
>> directories created by fsstress (contain a lot of fs objects) to
>> find potential stability issue.
>>
>
> Looks good.
> Did it help you find any stability issues?
>
Not yet, it looks fine everytime I run this test, maybe could help to
find in the future. :)
Thanks,
Yi.
next prev parent reply other threads:[~2018-10-18 11:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 7:45 [PATCH v2 0/4] overlay: enhance fsck.overlay test cases zhangyi (F)
2018-10-16 7:45 ` [PATCH v2 1/4] overlay: correct fsck.overlay exit code zhangyi (F)
2018-10-16 9:45 ` Amir Goldstein
2018-10-18 2:37 ` zhangyi (F)
2018-10-18 4:37 ` Amir Goldstein
2018-10-18 16:22 ` zhangyi
2018-10-18 4:54 ` Amir Goldstein
2018-10-16 7:45 ` [PATCH v2 2/4] overlay: fix exit code for some fsck.overlay valid cases zhangyi (F)
2018-10-16 9:26 ` Amir Goldstein
2018-10-18 3:42 ` zhangyi (F)
2018-10-18 4:44 ` Amir Goldstein
2018-10-19 12:36 ` zhangyi (F)
2018-10-19 14:00 ` Amir Goldstein
2018-10-16 7:45 ` [PATCH v2 3/4] overlay: add fsck.overlay stress test zhangyi (F)
2018-10-16 10:07 ` Amir Goldstein
2018-10-18 3:48 ` zhangyi (F) [this message]
2018-10-16 7:45 ` [PATCH v2 4/4] overlay: add fsck.overlay exception tests zhangyi (F)
2018-10-16 13:29 ` Amir Goldstein
2018-10-16 9:27 ` [PATCH v2 0/4] overlay: enhance fsck.overlay test cases Amir Goldstein
2018-10-16 12:39 ` Amir Goldstein
2018-10-18 3:50 ` zhangyi (F)
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=1d2c7919-64d6-5e2e-9908-5729d4e561df@huawei.com \
--to=yi.zhang@huawei.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=miaoxie@huawei.com \
--cc=miklos@szeredi.hu \
/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