Thread (272 messages) 272 messages, 1 author, 2018-12-05

[Bug 201685] ext4 file system corruption

From: <hidden>
Date: 2018-11-23 02:09:48

https://bugzilla.kernel.org/show_bug.cgi?id=201685
--- Comment #32 from Azat Khuzhin (a3at.mail@gmail.com) ---
(In reply to Jens Axboe from comment #28)
If it's not this, another hint might be a discard change. Is everyone
affected using discard?
And what a coincidence, before upgrading to 4.20-rc2 I enabled discard:

# findmnt /
TARGET SOURCE                FSTYPE OPTIONS
/      /dev/mapper/cryptroot ext4   rw,relatime,discard

# cat /proc/cmdline
cryptdevice=...:cryptroot:allow-discards

# cryptsetup status cryptroot
/dev/mapper/cryptroot is active and is in use.
  ...
  flags:   discards

Plus I triggered fstrim manually at start:

# systemctl status fstrim
Nov 19 00:16:14 azat fstrim[23944]: /boot: 122.8 MiB (128716800 bytes) trimmed
on /dev/nvme0n1p1
Nov 19 00:16:14 azat fstrim[23944]: /: 0 B (0 bytes) trimmed on
/dev/mapper/cryptroot

But what is interesting here is that it did not do any discard for the "/", hm
(does ext4 did it for me at start?)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help