This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1686687
Title:
fstrim destroying XFS on SAN
Status in linux package in Ubuntu:
Confirmed
Bug
We did get around to do more testing and follow suggestions. The
filesystem corruption could be reproduced. The run was done bypassing
multipathing and using a single path directly.
OUTPUT reproduce.sh (tail):
+ fstrim -v /mnt/san
/mnt/san: 120 TiB (131939249291264 bytes) trimmed
+ umount -vvv /m
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 kernel[
Come to think of it, since you say it only seems to happen on a
multipath SAN and not on a normal disk, it may be related to the order
of requests being sent to the disk and XFS's use of io barriers to make
sure that the unmap request for the old data does not hit the disk after
the new filesystem
Marked as Confirmed in accordance with comment #3. Further detail might
be provided on request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
For us, fstrim was the frontend to the bug and running it consistently
damaged our filesystems. That is why util-linux was chosen as the
affected package. Also removing the cron file will not be sufficient as
any update to the package (using cron-apt) might re-install it. Maybe a
conflicting change
Just reomve /etc/cron.weekly/fstrim as a workaround. The underlying bug
is not in fstrim, but in the kernel somewhere; probably the XFS
filesystem driver and its interaction between preallocation and the
FIBMAP ioctl.
** Package changed: util-linux (Ubuntu) => linux (Ubuntu)
** Tags added: bot-
8 matches
Mail list logo
