From: Dave Chinner <david@fromorbit.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] generic/067: add a testcase to check some inline truncation behaviors
Date: Wed, 18 Mar 2015 14:46:53 +1100 [thread overview]
Message-ID: <20150318034653.GE10105@dastard> (raw)
In-Reply-To: <1426613572-2405-1-git-send-email-jaegeuk@kernel.org>
On Tue, Mar 17, 2015 at 10:32:51AM -0700, Jaegeuk Kim wrote:
> This patch introduces a new testcase, generic/067, to test several truncation
> cases under the inline feature supported by filesystems.
"inline feature" means what, exactly?
>
> +_supported_os Linux
> +_require_scratch
> +
> +testfile=$SCRATCH_MNT/testfile
> +
> +_scratch_mkfs > /dev/null 2>&1
> +_scratch_mount
> +
> +# aligned inline truncation
Aligned to what, exactly?
> +$XFS_IO_PROG -t -f \
> +-c "pwrite -S 0x58 0 120" `# write |XXXXXXXXXXXXXXXXXXXXXXXX|` \
> +-c "fsync" \
> +-c "truncate 0" `# truncate | |` \
> +-c "truncate 160" `# truncate | |` \
> +-c "close" \
> +$testfile | _filter_xfs_io
Please indent multiple line xfs_io command a little more clearly,
and align the "\" so it's clear it's amultiple line command
$XFS_IO_PROG -t -f \
-c "pwrite -S 0x58 0 120" `# write |XXXXXXXXXXXXXXXXXXXXXXXX|` \
-c "fsync" \
-c "truncate 0" `# truncate | |` \
-c "truncate 160" `# truncate | |` \
-c "close" \
$testfile | _filter_xfs_io
(not sure the comment on the second truncate is correct, either)
Also, why do you need the "close" command?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-03-18 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 17:32 [PATCH 1/2] generic/067: add a testcase to check some inline truncation behaviors Jaegeuk Kim
2015-03-17 17:32 ` [PATCH 2/2] f2fs/001: introduce a testcaes for -ENOSPC with inline operation Jaegeuk Kim
2015-03-18 3:46 ` Dave Chinner [this message]
2015-03-18 18:01 ` [PATCH 1/2] generic/067: add a testcase to check some inline truncation behaviors Jaegeuk Kim
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=20150318034653.GE10105@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).