" Ted Ts'o, instead, explained why the affected pages are marked clean after an I/O error occurs; in short, the most common cause of I/O errors, by far, is a user pulling out a USB drive at the wrong time. If some process was copying a lot of data to that drive, the result will be an accumulation of dirty pages in memory, perhaps to the point that the system as a whole runs out of memory for anything else."
IOW Linux developers compromised kernel behavior for a DESKTOP use case.
Seriously, who the fuck cares if someone's computer crashes if they're dumb enough to pull out a USB drive while data is being written to it? You're seriously causing people's databases to lose data for that?
Fuck you, Linux.
(Including myself, but maybe it's time for that to change.)
Linux throws away your data Show more
I currently run FreeBSD on one system: my file/media server, via FreeNAS. Prior to FreeNAS, that machine ran straight up FreeBSD, which I'd forgotten until just now. I knew I'd migrated it at some point but had it in my head that I'd been running Linux on it previously. But I've always used ZFS for it and ZFS was even crappier on Linux when I built the thing than it is now.