From: Vivek Goyal <vgoyal@redhat.com>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: linux-unionfs@vger.kernel.org, fstests@vger.kernel.org,
miklos@szeredi.hu, amir73il@gmail.com, eguan@redhat.com,
miaoxie@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH xfstest v2 2/4] overlay: add fsck.overlay whiteout test
Date: Wed, 3 Jan 2018 10:04:35 -0500 [thread overview]
Message-ID: <20180103150435.GA3595@redhat.com> (raw)
In-Reply-To: <20171228114933.47759-3-yi.zhang@huawei.com>
On Thu, Dec 28, 2017 at 07:49:31PM +0800, zhangyi (F) wrote:
[..]
> +# Test orphan whiteout in lower and upper layer, should remove
> +echo "+ Orphan whiteout"
> +make_whiteout $lowerdir/foo
> +make_whiteout $upperdir/foo
> +make_whiteout $upperdir/bar
> +
> +_overlay_fsck_dirs $lowerdir $upperdir $workdir -p >> $seqres.full 2>&1 || \
> + _fail "fsck should not fail"
I ran fsck.overlay manually (V3 patches) with one orphan whiteout in
upper. I get following output.
fsck.overlay -o lowerdir=lower,upperdir=upper,workdir=work
Orphan whiteout: /root/fsck-overlay-testing/upper/foo Remove ? [y]:
y
fsck.overlay:[Error]: Cannot getxattr /root/fsck-overlay-testing/upper/foo trusted.overlay.origin: No such file or directory
Filesystem clean
This message about "overlay.origin" not being there, should not be an
error. You have already figured out, its an orphan whiteout, and user
already asked you to remove it. So checking or origin after that can
calling it Error might not make much sense. Also on top, later I get
"Filesystem clean".
I think in this case, user should not see any message until and unless a
error actually has happened which prevents from cleaning orphan whiteout.
Vivek
next prev parent reply other threads:[~2018-01-03 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 11:49 [PATCH xfstest v2 0/4] overlay: add fsck.overlay basic tests zhangyi (F)
2017-12-28 11:49 ` [PATCH xfstest v2 1/4] overlay: add filesystem check helper zhangyi (F)
2017-12-28 12:12 ` Amir Goldstein
2017-12-28 11:49 ` [PATCH xfstest v2 2/4] overlay: add fsck.overlay whiteout test zhangyi (F)
2017-12-28 12:11 ` Amir Goldstein
2017-12-29 1:27 ` zhangyi (F)
2018-01-02 20:05 ` Vivek Goyal
2018-01-03 1:02 ` zhangyi (F)
2018-01-03 15:04 ` Vivek Goyal [this message]
2018-01-04 1:15 ` zhangyi (F)
2017-12-28 11:49 ` [PATCH xfstest v2 3/4] overlay: add fsck.overlay redirect directory test zhangyi (F)
2017-12-28 12:37 ` Amir Goldstein
2017-12-29 1:49 ` zhangyi (F)
2017-12-30 4:06 ` zhangyi (F)
2017-12-30 9:35 ` Amir Goldstein
2017-12-31 5:06 ` zhangyi
2017-12-28 11:49 ` [PATCH xfstest v2 4/4] overlay: add fsck.overlay impure xattr test zhangyi (F)
2017-12-28 12:43 ` Amir Goldstein
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=20180103150435.GA3595@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=miklos@szeredi.hu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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