https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #4 from vice...@gmail.com ---
Hi! Yes, it is reproducible.
Each time TRIM is enabled via the UDEV rule and the FS mounted with
the discard option, the issue is triggered at the very first write attempt.
Before mounting fsck.f2fs was
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #5 from vice...@gmail.com ---
Created attachment 278227
--> https://bugzilla.kernel.org/attachment.cgi?id=278227=edit
fsck.f2fs
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #6 from vice...@gmail.com ---
Hi, just found that the issue is also reproducible when mounted
with the "nodiscard" option, enabling TRIM via UDEV is enouth.
--
You are receiving this mail because:
You are watching the assignee of
Hi,
On Fri, Aug 24, 2018 at 9:16 PM, Eric Biggers wrote:
> Hi Gao,
>
> On Sat, Aug 25, 2018 at 10:29:26AM +0800, Gao Xiang wrote:
>> Hi,
>>
>> At last, I hope filesystems could select the on-disk position of hash tree
>> and 'struct fsverity_descriptor'
>> rather than fixed in the end of verity
