3 ms·

Do you have any specific reasons not to trust ZoL? ZFS-on-Linux devs say it's ready for production[1]. Lawrence Livermore laboratory stores petabytes of data

by dmm 10y ago

Do you have any specific reasons not to trust ZoL? ZFS-on-Linux devs say it's ready for production[1]. Lawrence Livermore laboratory stores petabytes of data using ZoL[2]. If we're sharing anecdotes, ZoL has served me fantastically for several years. [1] https://clusterhq.com/2014/09/11/state-zfs-on-linux/ https://clusterhq.com/2014/09/11/state-zfs-on-linux/ [2] http://computation.llnl.gov/newsroom/livermores-zfs-linux-port-hit-it-industry http://computation.llnl.gov/newsroom/livermores-zfs-linux-po...

user5994461 10y ago
I thought "ZoL" was a pun with ZFS and LOL to tell how not ready it is for production ^^
- ryao 10y ago
  ZoL is an acronym for ZFSonLinux.
devoply 10y ago
My reasons are as follows: 1) Seen users complaining about data loss on issues on github. 2) Had the init script fail on upgrade and had to fix it by hand when upgrading Ubuntu. Probably a one time issue. Need a bit more reliability from a file system.
otterley 10y ago
We have encountered a reproducible panic and deadlocks when a containerized process gets terminated by the kernel for exceeding its memory limit: https://github.com/zfsonlinux/zfs/issues/5535 https://github.com/zfsonlinux/zfs/issues/5535 We're strongly considering using something else until this gets addressed. The problem is, we don't know what, because every other CoW implementation also has issues. * dm-thinp: Slow, wastes disk space * OverlayFS: No SELinux support * aufs: Not in mainline or CentOS kernel; rename(2) not implemented correctly; slow writes
- brendangregg 10y ago
  The issue you link to was opened a day ago. If that were me, I'd see how quickly it was fixed before strongly considering something else.
  - otterley 10y ago
    Have you had any issues to report? If so, how quickly were they fixed? Knowing what the typical time is to address these issues would help us make a more educated decision.
    - lscotte 10y ago
      Yes, we've run into 2 or 3 ZFS bugs that I can think of that were resolved in a timely fashion (released within a few weeks if I recall) by Canonical working with Debian and zfsonlinux maintainers (and subsequently fixed in both Ubuntu and Debian - and upstream zfsonlinux for ones that were not debian-packaging related). Of course your mileage may vary, and it depends on the severity of the issue. Being prepared to provide detailed reproduction and debug information, and testing proposed fixes, will greatly help - but that can be a serious time commitment on your side (for us, it's worth it). Hope that helps!
- justincormack 10y ago
  zfs is not in mainline or centos kernel, so you are presumably willing to try stuff. I believe all the overlay/selinux work is now upstream, it is supposed to ship in the next RHEL release.
  - otterley 10y ago
    I look forward to that.

by dmm 10y ago

user5994461 10y ago

I thought "ZoL" was a pun with ZFS and LOL to tell how not ready it is for production ^^

ryao 10y ago
ZoL is an acronym for ZFSonLinux.

devoply 10y ago

My reasons are as follows: 1) Seen users complaining about data loss on issues on github. 2) Had the init script fail on upgrade and had to fix it by hand when upgrading Ubuntu. Probably a one time issue. Need a bit more reliability from a file system.

otterley 10y ago

We have encountered a reproducible panic and deadlocks when a containerized process gets terminated by the kernel for exceeding its memory limit: https://github.com/zfsonlinux/zfs/issues/5535 https://github.com/zfsonlinux/zfs/issues/5535 We're strongly considering using something else until this gets addressed. The problem is, we don't know what, because every other CoW implementation also has issues. * dm-thinp: Slow, wastes disk space * OverlayFS: No SELinux support * aufs: Not in mainline or CentOS kernel; rename(2) not implemented correctly; slow writes

brendangregg 10y ago
The issue you link to was opened a day ago. If that were me, I'd see how quickly it was fixed before strongly considering something else.
- otterley 10y ago
  Have you had any issues to report? If so, how quickly were they fixed? Knowing what the typical time is to address these issues would help us make a more educated decision.
  - lscotte 10y ago
    Yes, we've run into 2 or 3 ZFS bugs that I can think of that were resolved in a timely fashion (released within a few weeks if I recall) by Canonical working with Debian and zfsonlinux maintainers (and subsequently fixed in both Ubuntu and Debian - and upstream zfsonlinux for ones that were not debian-packaging related). Of course your mileage may vary, and it depends on the severity of the issue. Being prepared to provide detailed reproduction and debug information, and testing proposed fixes, will greatly help - but that can be a serious time commitment on your side (for us, it's worth it). Hope that helps!
justincormack 10y ago
zfs is not in mainline or centos kernel, so you are presumably willing to try stuff. I believe all the overlay/selinux work is now upstream, it is supposed to ship in the next RHEL release.
- otterley 10y ago
  I look forward to that.