On 2019-09-06 00:15:03, Ryan Beisner wrote:
> We’ve just dug into this aspect of both Disco and Eoan. Unfortunately,
> I don’t know if this ever succeeded on these two releases.
I don't know if you're easily able to test old kernel versions but it
could be helpful to test the kernel that Disco released with. That's
kernel version 5.0.0-13.14.
It doesn't look problematic to me but it is a commit shared between
current Disco and Eoan kernels and intersects with the direct I/O
operations that mkfs.xfs does on the block device.
It is a reach but just knowing whether or not the Disco release kernel
is affected would allow us to rule out (or not) any changes landed since
the release.
On 2019-09-06 00:15:03, Ryan Beisner wrote:
> We’ve just dug into this aspect of both Disco and Eoan. Unfortunately,
> I don’t know if this ever succeeded on these two releases.
I don't know if you're easily able to test old kernel versions but it
could be helpful to test the kernel that Disco released with. That's
kernel version 5.0.0-13.14.
That kernel would not have this commit:
https:/ /git.launchpad. net/~ubuntu- kernel/ ubuntu/ +source/ linux/+ git/disco/ commit/ ?id=13674c2ebe5 2da7c30cf27f980 0d0624c63deb03
It doesn't look problematic to me but it is a commit shared between
current Disco and Eoan kernels and intersects with the direct I/O
operations that mkfs.xfs does on the block device.
It is a reach but just knowing whether or not the Disco release kernel
is affected would allow us to rule out (or not) any changes landed since
the release.