Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] generic/017: skip invalid block sizes for btrfs
Date: Mon, 23 Jun 2014 14:35:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1406231413400.2169@localhost.localdomain> (raw)
In-Reply-To: <1403519280-24216-1-git-send-email-fdmanana@gmail.com>

On Mon, 23 Jun 2014, Filipe David Borba Manana wrote:

> Date: Mon, 23 Jun 2014 11:28:00 +0100
> From: Filipe David Borba Manana <fdmanana@gmail.com>
> To: fstests@vger.kernel.org
> Cc: linux-btrfs@vger.kernel.org,
>     Filipe David Borba Manana <fdmanana@gmail.com>
> Subject: [PATCH] generic/017: skip invalid block sizes for btrfs
> 
> In btrfs the block size (called sector size in btrfs) can not be
> smaller then the page size. Therefore skip block sizes smaller
> then page size if the fs is btrfs, so that the test can succeed
> on btrfs (testing only with block sizes of 4kb on systems with a
> page size of 4Kb).

The test itself is wrong, it's trying to do _scratch_mkfs with
different block size, but the block size might already be specified
by the user (in fact it should be user responsibility to test
different block sizes). In the case that mkfs can not handle
multiple of the same option like mkfs.xfs for example it will fail,
but the test will go on with the original file system.

The test needs to be fixed to just test the file system with options
specified by the user. Also we should change _scratch_mkfs() to fail
the test if the mkfs failed (no one is actually testing mkfs_status
variable anyway.

Once we do that this patch will no longer be needed.

Thanks!
-Lukas

> 
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
> ---
>  tests/generic/017 | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/tests/generic/017 b/tests/generic/017
> index 13b7254..6495be5 100755
> --- a/tests/generic/017
> +++ b/tests/generic/017
> @@ -51,6 +51,14 @@ BLOCKS=10240
>  
>  for (( BSIZE = 1024; BSIZE <= 4096; BSIZE *= 2 )); do
>  
> +	# btrfs doesn't support block size smaller then page size
> +	if [ "$FSTYP" == "btrfs" ]; then
> +		if (( $BSIZE < `getconf PAGE_SIZE` )); then
> +			echo "80"
> +			continue
> +		fi
> +	fi
> +
>  	length=$(($BLOCKS * $BSIZE))
>  	case $FSTYP in
>  	xfs)
> 

  parent reply	other threads:[~2014-06-23 12:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 10:28 [PATCH] generic/017: skip invalid block sizes for btrfs Filipe David Borba Manana
2014-06-23 10:48 ` Satoru Takeuchi
2014-06-23 10:55   ` Filipe David Manana
2014-06-23 11:04     ` Satoru Takeuchi
2014-06-23 11:46   ` Brendan Hide
2014-06-23 12:35 ` Lukáš Czerner [this message]
2014-06-23 14:09   ` Lukáš Czerner
2014-06-23 17:39     ` Filipe David Manana
2014-06-24  4:26     ` Dave Chinner
2014-06-24  5:28       ` Lukáš Czerner
2014-06-23 22:23 ` Zach Brown
2014-06-24  4:58 ` Roman Mamedov

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=alpine.LFD.2.00.1406231413400.2169@localhost.localdomain \
    --to=lczerner@redhat.com \
    --cc=fdmanana@gmail.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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