All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201793] New: [xfstests generic/299] XFS corruption found: sb_fdblocks 7302443, counted 7302451
Date: Tue, 27 Nov 2018 03:30:09 +0000	[thread overview]
Message-ID: <bug-201793-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=201793

            Bug ID: 201793
           Summary: [xfstests generic/299] XFS corruption found:
                    sb_fdblocks 7302443, counted 7302451
           Product: File System
           Version: 2.5
    Kernel Version: xfs-4.20-fixes-2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: zlang@redhat.com
        Regression: No

Description of problem:
I hit a XFS corruption several times on ppc64le, by running generic/299 on 2k
blocksize XFS (reflink=1,rmapbt=1):
#
# FSQA Test No. 299
#
# AIO/DIO stress test
# Run random AIO/DIO activity and fallocate/truncate simultaneously
# Test will operate on huge sparsed files so ENOSPC is expected.
#
FSTYP         -- xfs (non-debug)
PLATFORM      -- Linux/ppc64le xxxxxxx 4.20.0-rc1.kasan
MKFS_OPTIONS  -- -f -b size=2048 -m crc=1,finobt=1,reflink=1,rmapbt=1 -i
sparse=1 /dev/vda5
MOUNT_OPTIONS -- -o context=system_u:object_r:nfs_t:s0 /dev/vda5
/mnt/xfstests/mnt2

generic/299 176s ... _check_xfs_filesystem: filesystem on /dev/vda5 is
inconsistent (r)
(see /var/lib/xfstests/results//generic/299.full for details)

Ran: generic/299
Failures: generic/299
Failed 1 of 1 tests

Version-Release number of selected component (if applicable):
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
xfs-4.20-fixes-2

How reproducible:
1~2% on my ppc64le kvm machine. But it's hard to reproduce on my x86_64 real
machine.

Steps to Reproduce:
Loop running generic/299, but maybe not easy to hit it

Actual results:
XFS corruption

Expected results:
test always pass

Additional info:
Please check the full output and xfs metadump from attachments.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2018-11-27 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  3:30 bugzilla-daemon [this message]
2018-11-27  3:31 ` [Bug 201793] [xfstests generic/299] XFS corruption found: sb_fdblocks 7302443, counted 7302451 bugzilla-daemon
2018-11-27  3:31 ` bugzilla-daemon
2018-11-27  3:33 ` bugzilla-daemon

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=bug-201793-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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 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.