At 01/11/2017 10:40 AM, Eric Sandeen wrote:
On 1/10/17 8:08 PM, Qu Wenruo wrote:
Hi, Andreas and Eryu,
I found test case generic/389 fails on btrfs and ext4, and it fails with xfs_io
segfault.
Details, please?
Works ok here:
# ./check generic/389
FSTYP -- ext4
PLATFORM -- Linux/x86_64 bp-05 4.9.0-rc1+
MKFS_OPTIONS -- /dev/sdb2
MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0
/dev/sdb2 /mnt/scratch
generic/389 1s ... 1s
Ran: generic/389
Passed all 1 tests
# rpm -q xfsprogs
xfsprogs-4.9.0-1.el6.x86_64
OK, that's the problem.
My repo only provides old xfsprogs, which xfsprogs-4.5.0-2.fc25.x86_64.
What version of kernel and xfsprogs were you testing, and what was the segfault?
Kernel is mainline v4.10-rc1.
No debuginfo installed, so no backtrace, but since there is so many
So the problem is the old xfsprogs, I'll update or compile xfsprogs.
Thanks for your kind info.
Thanks,
Qu
Thanks,
-Eric
So it seems to be a bug in xfsprogs, but I'm already using the latest release
from Fedora.
Is this a known bug?
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
