From: Dave Chinner <david@fromorbit.com>
To: alexander.tsvetkov@oracle.com
Cc: xfs@oss.sgi.com
Subject: Re: scratch filesystem corruptions
Date: Fri, 7 Nov 2014 08:49:34 +1100 [thread overview]
Message-ID: <20141106214934.GF23575@dastard> (raw)
In-Reply-To: <545B541A.60800@oracle.com>
On Thu, Nov 06, 2014 at 01:57:30PM +0300, alexander.tsvetkov@oracle.com wrote:
> Hello,
>
> I've noted that the enabling of scratch device post checks after
> xfstests commit
> "common: Check the file system consistency on SCRATCH_DEV" has
> started to show
> the scratch filesystem corruptions for the following tests runs:
> xfs/050,134,187,244,287.
> I have these corruptions reproduced with upstream linux kernel of
> version 3.15 and
> the latest xfsprogs/xfstests. Are these known issues?
# ./check xfs/050 xfs/134 xfs/187 xfs/244 xfs/287
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 test2 3.18.0-rc2-dgc+
MKFS_OPTIONS -- -f -bsize=4096 /dev/vdb
MOUNT_OPTIONS -- /dev/vdb /mnt/scratch
xfs/050 3s ... 4s
xfs/134 0s ... 0s
xfs/187 1s ... 1s
_check_xfs_filesystem: filesystem on /dev/vdb is inconsistent (c) (see /home/dave/src/xfstests-dev/results//xfs/187.full)
_check_xfs_filesystem: filesystem on /dev/vdb is inconsistent (r) (see /home/dave/src/xfstests-dev/results//xfs/187.full)
xfs/244 0s ... 1s
xfs/287 1s ... 0s
Ran: xfs/050 xfs/134 xfs/187 xfs/244 xfs/287
Passed all 5 tests
# cat ~/results/xfs/187.full
....
_check_xfs_filesystem: filesystem on /dev/vdb is inconsistent
*** xfs_check output ***
sb_features2 (0x2) not same as sb_bad_features2 (0xa)
*** end xfs_check output
.....
The xfs/187 failure needs investigation - that's a bad_features2
mismatch, but it's been way down my list of priorities...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-11-06 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 10:57 scratch filesystem corruptions alexander.tsvetkov
2014-11-06 21:49 ` Dave Chinner [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=20141106214934.GF23575@dastard \
--to=david@fromorbit.com \
--cc=alexander.tsvetkov@oracle.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.