From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 204049] [xfstests generic/388]: XFS: Assertion failed: ip->i_d.di_format != XFS_DINODE_FMT_BTREE || ip->i_d.di_nextents > XFS_IFORK_MAXEXT(ip, XFS_DATA_FORK), file: fs/xfs/xfs_inode.c, line: 3646
Date: Thu, 18 Jul 2019 20:29:18 +0000 [thread overview]
Message-ID: <bug-204049-201763-sqxMi1T70G@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204049-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204049
--- Comment #3 from Luis Chamberlain (mcgrof@kernel.org) ---
And, do you not get a crash with the "xfs_nocrc" or "xfs_reflink"
configurations? What if you run the test in a loop. To test in a loop I use
oscheck's naggy-check.sh [0]. Provided you have configured your sections named
in the fstests configuration as I have on oscheck [1], you should be able to
use it as follows until a failure is found:
./naggy-check.sh -s xfs_reflink_normapbt -f generic/388
I just added xfs_reflink_normapbt to the upstream oscheck demo config.
[0] https://gitlab.com/mcgrof/oscheck/blob/master/naggy-check.sh
[1] https://gitlab.com/mcgrof/oscheck/blob/master/fstests-configs/xfs.config
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-07-18 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 8:04 [Bug 204049] New: [xfstests generic/388]: XFS: Assertion failed: ip->i_d.di_format != XFS_DINODE_FMT_BTREE || ip->i_d.di_nextents > XFS_IFORK_MAXEXT(ip, XFS_DATA_FORK), file: fs/xfs/xfs_inode.c, line: 3646 bugzilla-daemon
2019-07-18 20:00 ` [Bug 204049] " bugzilla-daemon
2019-07-18 20:19 ` bugzilla-daemon
2019-07-18 20:29 ` bugzilla-daemon [this message]
2019-07-19 19:37 ` bugzilla-daemon
2019-07-19 21:29 ` bugzilla-daemon
2019-07-19 21:37 ` Bill O'Donnell
2019-07-19 21:45 ` 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-204049-201763-sqxMi1T70G@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.