3 ms·
I’m not going to corroborate the entire article, but my experience from an outage 2 days ago on our new ZFS on Linux file server has left a bad taste despite ye
by reacharavindh 3y ago
I’m not going to corroborate the entire article, but my experience from an outage 2 days ago on our new ZFS on Linux file server has left a bad taste despite years of great use with ZFS in the FreeBSD world.
Ok. So, We hit the deadlock that was fixed
here:-> https://github.com/rohan-puri/zfs/commit/8e4d086c13c16bc461bad9f56b3d91c44c2c149e https://github.com/rohan-puri/zfs/commit/8e4d086c13c16bc461b...
but it never got merged to the master or release as far as I see it
Current Master: https://github.com/openzfs/zfs/blob/acb33ee1c169bf1c1f687db18fa1815ffa68f246/module/os/linux/zfs/zfs_ctldir.c#L365 https://github.com/openzfs/zfs/blob/acb33ee1c169bf1c1f687db1...
When I look up the problem, I could only see the issue being discussed, and probably leading to that commit, and then it was not in my current release (2.1) despite several years later. I’m wondering if ZFS still holds that high standard for reliability.
- donmcronald 3y agoIsn't it there? https://github.com/openzfs/zfs/commit/fd7265c646f40e364396af5014bbb83e809e124a https://github.com/openzfs/zfs/commit/fd7265c646f40e364396af... git branch --contains fd7265c * master Since 0.8. git branch -r --contains fd7265c | head origin/HEAD -> origin/master origin/compat-5.15-META origin/issue-14573-backport origin/master origin/revert-14721-remove-quota-zap origin/zfs-0.8-release origin/zfs-0.8.7-staging origin/zfs-2.0-release origin/zfs-2.0.3-staging origin/zfs-2.0.4-staging