On Tue, 2019-02-19 at 10:07 -0500, Jeff Mahoney wrote: > That's more or less how the problem presents itself, but it's not that > we issue an fstrim on a block and it gets zeroed. That would be fine > from the file system perspective. It's that the fstrim is issued and > unrelated blocks are zeroed. Once I saw the storage layer was > responsible, I stopped digging and passed it to Hannes.
How can issuing an fstrim cause unrelated blocks to be zeroed? I think the root cause needs to be identified before we continue with this patch. Thanks, Bart.
