From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201897] [xfstests generic/482]: filesystem corruption after log replay
Date: Wed, 05 Dec 2018 10:02:43 +0000 [thread overview]
Message-ID: <bug-201897-201763-7IkRplFf0g@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201897-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201897
--- Comment #4 from Zorro Lang (zlang@redhat.com) ---
V5 XFS without reflink feature test pass:
# ./check generic/482
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 ibm-x3650m4-10 4.20.0-rc1
MKFS_OPTIONS -- -f -m reflink=0,rmapbt=0,finobt=0,crc=1 -i sparse=0
/dev/mapper/rhel_ibm--x3650m4--10-xfscratch
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0
/dev/mapper/rhel_ibm--x3650m4--10-xfscratch /mnt/scratch
generic/482 1567s ... 774s
Ran: generic/482
Passed all 1 tests
# ./check generic/482
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/x86_64 ibm-x3650m4-10 4.20.0-rc1
MKFS_OPTIONS -- -f -m reflink=0,rmapbt=0,finobt=1,crc=1 -i sparse=1
/dev/mapper/rhel_ibm--x3650m4--10-xfscratch
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0
/dev/mapper/rhel_ibm--x3650m4--10-xfscratch /mnt/scratch
generic/482 774s ... 841s
Ran: generic/482
Passed all 1 tests
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-05 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 8:40 [Bug 201897] New: [xfstests generic/482]: filesystem corruption after log replay bugzilla-daemon
2018-12-05 8:43 ` [Bug 201897] " bugzilla-daemon
2018-12-05 8:44 ` bugzilla-daemon
2018-12-05 9:07 ` bugzilla-daemon
2018-12-05 10:02 ` bugzilla-daemon [this message]
2018-12-05 10:10 ` 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-201897-201763-7IkRplFf0g@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.