3 ms·
Their solution is zfs on the write master can't wait for the next blog post on how they found their data corrupted
by avereveard 3y ago
Their solution is zfs on the write master can't wait for the next blog post on how they found their data corrupted
- philkrylov 3y agoPostgreSQL does not use SEEK_DATA/SEEK_HOLE so they're ok
- bfung 3y agoOr how after they do a writer failover, they start seeing duplicate data.
- ikiris 3y agoOk, I'm out of the loop, whats the problem with zfs here?
- avereveard 3y agohttps://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=Zfs%20corruption&sort=byDate&type=story https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... the mean time between corruption article on zfs is two years
- philkrylov 3y agoLooking at your search results, there's just one recent ZFS corruption case with SEEK_DATA/SEEK_HOLE (in several HN reflections), a 2-year old Ubuntu-only buggy patch story, and some 2008 [Open]Solaris corruption.
- ikiris 3y agoMost of those links are about bad memory. If you blame bad memory for filesystem issues I don't really know what to tell you. Ignoring the poor state of the native encryption code, ZFS has had 1 corruption bug in like 10 years. Thats one of the best records for modern filesystems. I still wouldn't trust my data to btrfs by comparison.