Updated Kernel Issues & Bugs (markdown)

trapexit 2024-02-28 12:55:54 -06:00
parent 44bcaafd20
commit 49225c5bdd

@ -2,6 +2,8 @@ There have been a number of kernel issues / bugs over the years which mergerfs h
## NFS and EIO errors
https://lore.kernel.org/linux-fsdevel/20240228160213.1988854-1-mszeredi@redhat.com/T/
Over the years some users have reported that while exporting mergerfs via NFS, after significant filesystem activity, not only will the NFS client start returning ESTALE and EIO errors but mergerfs itself would start returning EIO errors. The problem was that no one could reliability reproduce the issue. After a string of reports in late 2023 and early 2024 more investigation was done.
In Linux 5.14 new validation was put into FUSE which caught a few invalid situations and would tag a FUSE node as invalid if a check failed. Such checks include invalid file type, changing of type from one request to another, a size greater than 63bit, and the generation of a inode changing while in use.
@ -12,7 +14,8 @@ This wasn't a bug in FUSE but mergerfs. However, the incorrect behavior of merge
So the kernel was doing two invalid things. Requesting the parent of the root and then when that failed issuing a forget for the root. These led to chasing after the wrong possible causes.
How best to handle these edge cases are still being discussed as of 2024-02-25 but mergerfs has been fixed to ensure generation=0 when root lookups are requested. Nodes generally shouldn't be marked as bad so it might be good to have the kernel log when it happens for better debugging.
The proposed change is for FUSE to revert the marking of root node bad if the generation is non-zero and warn about it. It will mark the node bad but not unhash/forget/remove it.
## Truncated files