3 ms·
No need to pretend, because it never happened: > Initially, the problem was thought to be in the ext4 filesystem, since that is what the affected users were us
by kasabali 6y ago
No need to pretend, because it never happened:
> Initially, the problem was thought to be in the ext4 filesystem, since that is what the affected users were using...It took until December 4 for Lukáš Krejčí to correctly bisect the problem down to a block-layer change.
https://lwn.net/Articles/774440/ https://lwn.net/Articles/774440/
- efdee 6y agoI never said the problem was in the EXT4 filesystem. The problem resulted in EXT4 corruption. Quite sure the Git corruption issue WSL2 has isn't in Git either.
- barrkel 6y agoOK, the 4.19 filesystem corruption issue. The fact that it was in the block layer doesn't exactly mean it didn't materialize as a FS corruption issue.