public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Paul Paulson <paul.paulson@seagate.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] generic/017: skip tests with mkfs failures
Date: Tue, 7 Oct 2014 10:21:14 +1100	[thread overview]
Message-ID: <20141006232114.GK2301@dastard> (raw)
In-Reply-To: <1412619830-23088-1-git-send-email-paul.paulson@seagate.com>

On Mon, Oct 06, 2014 at 01:23:50PM -0500, Paul Paulson wrote:
> The mkfs command fails to create ext4 filesystems on partition sizes
> greater than 1998080 MiB when using 1024 byte blocks and the default
> calculation for the number of inodes reserved for the filesystem.

This is what the MKFS_OPTIONS field is for. We don't usually try to
work around specific perculiarities of specific filesystem configs
in individual tests.

> The following error message is produced when the maximum number of
> inodes is exceeded:
> 
>     "Cannot create filesystem with requested number of inodes while
>      setting up superblock"
> 
> The generic/017 test was modified to skip the 1K block size test
> for partitions with an inode count that exceeds the maximum.

Oh, I thought we got rid of the multiple block size loop in that
test.

Hmm - maybe I missed picking up that patch from Lucas after we
discussed it. I'll go back and pick it up, and then you won't have
this problem when testing default filesystem configs.

> diff --git a/tests/generic/017 b/tests/generic/017
> index 13b7254..eb38d4d 100755
> --- a/tests/generic/017
> +++ b/tests/generic/017
> @@ -49,8 +49,16 @@ _do_die_on_error=y
>  testfile=$SCRATCH_MNT/$seq.$$
>  BLOCKS=10240
>  
> -for (( BSIZE = 1024; BSIZE <= 4096; BSIZE *= 2 )); do
> +MAX_INODE_COUNT_1K=127877120
> +inode_count=`$TUNE2FS_PROG -l $SCRATCH_DEV | awk '/Inode count:/ { print $3 }'`
> +initial_bsize=$(($inode_count <= $MAX_INODE_COUNT_1K ? 1024 : 2048))

FWIW, that'll break every filesystem type other than ext4.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2014-10-06 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 18:23 [PATCH] generic/017: skip tests with mkfs failures Paul Paulson
2014-10-06 23:21 ` Dave Chinner [this message]
2014-10-07 18:18   ` Paul Paulson
2014-10-07  0:53 ` Theodore Ts'o
2014-10-07 18:12   ` Paul Paulson
2014-10-08  2:11     ` Theodore Ts'o
2014-10-08 13:17       ` Paul Paulson

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=20141006232114.GK2301@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=paul.paulson@seagate.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