From: Vivek Goyal <vgoyal@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: fstests <fstests@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Eryu Guan <guaneryu@gmail.com>
Subject: Re: [PATCH V3] xfstest: overlay: Add tests for overlay metadata only copy up feature
Date: Fri, 1 Jun 2018 08:38:04 -0400 [thread overview]
Message-ID: <20180601123804.GA3259@redhat.com> (raw)
In-Reply-To: <CAOQ4uxgjbK=XHy0E0n94KoLhkxEbNU-YFz05mHYaiQTuXPmiRQ@mail.gmail.com>
On Fri, Jun 01, 2018 at 11:34:38AM +0300, Amir Goldstein wrote:
[..]
> > +# File size on lower
> > +lowername="lowerfile"
> > +lowerlink="lowerfile-link"
> > +lowerdata="lower"
> > +lowerblocks="32"
> > +lowersize=$(( $lowerblocks * 512 ))
> > +
>
> Although the test passes now on ext4/xfs, my comment remains -
> it makes no sense for this test to calculate expected nr of blocks
> instead of using actual lower file blocks.
>
> While fallocate $size guaranties that resulting file size is $size
> you cannot say the same about $blocks. There is no guarantie
> that file systems will use $size / 512 blocks to store size$.
> file systems can and do allocate more blocks for e.g. xattr and
> other file metadata. There is really no reason for this test to
> make the assumption about $blocks however probable it may be.
Ok. So instead of making assumptions about number of blocks, instead,
create a file of pre-determined size, and then query the number of
blocks from lower and use that as expected blocks from overlay mount?
Will make that change. Thanks.
Vivek
prev parent reply other threads:[~2018-06-01 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 19:41 [PATCH V3] xfstest: overlay: Add tests for overlay metadata only copy up feature Vivek Goyal
2018-06-01 8:34 ` Amir Goldstein
2018-06-01 12:38 ` Vivek Goyal [this message]
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=20180601123804.GA3259@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--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 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.