Linux NFS development
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Steve French <smfrench@gmail.com>
Cc: fstests@vger.kernel.org,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: xfstest generic/299
Date: Fri, 23 Jan 2015 14:25:18 -0600	[thread overview]
Message-ID: <54C2AE2E.2040906@sandeen.net> (raw)
In-Reply-To: <CAH2r5mtL52=MYu225w5G-D8X9kAb1w0Zi-GhvOfyBzm-WVT0pQ@mail.gmail.com>

On 1/23/15 2:09 PM, Steve French wrote:
> On Thu, Jan 22, 2015 at 11:35 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> On 1/22/15 11:23 PM, Steve French wrote:
>>> Noticed test generic/299 failing over NFS (v4.1 dialect) with the error
>>>
>>> "[not run] /usr/bin/fio too old"
>>>
>>> fio-2.1.11 version (which is what is installed on current Ubuntu) is
>>> presumably not too old
>>
>> Well, 2.1.11 was released 16-Jul-2014
>>
>> fio is up to 2.2.5 now, so it sure could be.
> 
> I updated to 2.2.5-3 (cloning and building from the repository on
> git.kernel.org) which did not seem to change the results.
> 
>> The test sets up a config file, and tries to run fio against it;
>> if it fails, it's deemed "too old"
>>
>> And _require_fio dumps to $seqres.full,
>>
>>         $FIO_PROG --warnings-fatal --showcmd $job >> $seqres.full 2>&1
>>         [ $? -eq 0 ] || _notrun "$FIO_PROG too old, see $seqres.full"
>>
>> so what does 299.full look like?

so it's telling you:

> min value out of range: 0 (1 min)
> fio: failed parsing filesize=0
                      ^^^^^^^^^^

and if we read the test:

BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV`
FILE_SIZE=$((BLK_DEV_SIZE * 512))

cat >$fio_config <<EOF
###########
# $seq test fio activity
# Filenames derived from jobsname and jobid like follows:
# ${JOB_NAME}.${JOB_ID}.${ITERATION_ID}
[global]
ioengine=libaio
bs=128k
directory=${SCRATCH_MNT}
filesize=${FILE_SIZE}
^^^^^^^^^^^^^^^^^^^^^
...

since you have no block device for NFS, blockdev will fail,
and you won't get a block dev size, so you won't get a file size,
and the fio test won't work.

The script not catching this looks like a bug.

fio saying "too old" looks inaccurate.

You could fix it to DTRT on NFS somehow, or catch the fact that
the blockdev command fails (probably because $SCRATCH_DEV isn't
set?) and _notrun the test.

I imagine it could be fixed, though; df total space available on
$SCRATCH_MNT might do as well as blockdev --getsz, though I'm not
100% sure.

-Eric

      parent reply	other threads:[~2015-01-23 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  5:23 xfstest generic/299 Steve French
2015-01-23  5:35 ` Eric Sandeen
2015-01-23 20:09   ` Steve French
2015-01-23 20:17     ` Steve French
2015-01-23 20:28       ` Eric Sandeen
2015-01-23 20:25     ` Eric Sandeen [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=54C2AE2E.2040906@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=smfrench@gmail.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