4 ms·
Tomas Vondra goes over this in the talk. There's a rationale for that behavior: pulling out a USB stick out of the USB socket may have been what's triggered th
by adaszko 8y ago
Tomas Vondra goes over this in the talk. There's a rationale for that behavior: pulling out a USB stick out of the USB socket may have been what's triggered the fsync() failure. In that case, there's no way the kernel will be able to retry reliably.
- pas 8y agoSilent error ignoring is never a great API. Especially for a data integrity operation. fsync in case of the USB disappearing should simply return an error and drop the dirty pages.