FS/XFS testing framework
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: fstests@vger.kernel.org
Subject: generic/256 test failure?
Date: Wed, 10 Dec 2014 19:50:30 -0500	[thread overview]
Message-ID: <20141211005030.GA30240@thunk.org> (raw)

I've been trying to debug generic/256 failing under ext4, and I
realized that it's actually failing with xfs as well:

BEGIN TEST: XFS Wed Dec 10 19:36:38 EST 2014
Device: /dev/vdd
mk2fs options:
mount options:
FSTYP         -- xfs (non-debug)
PLATFORM      -- Linux/i686 kvm-xfstests 3.18.0-rc3-00029-g754c126
MKFS_OPTIONS  -- -f -bsize=4096 /dev/vdc
MOUNT_OPTIONS -- /dev/vdc /vdc

generic/256		[19:36:40] [19:37:31] - output mismatch (see /results/results-xfs/generic/256.out.bad)
    --- tests/generic/256.out	2014-12-10 18:15:22.000000000 -0500
    +++ /results/results-xfs/generic/256.out.bad	2014-12-10 19:37:32.002538550 -0500
    @@ -1 +1,2229 @@
     QA output created by 256
    +wrote 1073741824/1073741824 bytes at offset 0
    +1 GiB, 262144 ops; 0:00:11.00 (92.306 MiB/sec and 23630.3397 ops/sec)
    +pwrite64: No space left on device
    +pwrite64: No space left on device
    +pwrite64: No space left on device
    +pwrite64: No space left on device
    ...
    (Run 'diff -u tests/generic/256.out /results/results-xfs/generic/256.out.bad'  to see the entire diff)
Ran: generic/256
Failures: generic/256
Failed 1 of 1 tests

root@kvm-xfstests:~# blkid /dev/vdc
/dev/vdc: UUID="6a820f3b-109f-465e-941e-6bc2bfae6e42" TYPE="xfs"

This is failing with xfstests commit 6676905, and xfsprogs v3.2.2.

Is anyone else seeing this failure?

						- Ted

             reply	other threads:[~2014-12-11  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  0:50 Theodore Ts'o [this message]
2014-12-11  2:15 ` generic/256 test failure? Theodore Ts'o
2014-12-11  4:06   ` Dave Chinner

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=20141211005030.GA30240@thunk.org \
    --to=tytso@mit.edu \
    --cc=fstests@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