> CentOS 7 system running kernel 3.10
what the actual f*?
tag name v3.10 (bc1b510b8979ecc322f8d930dde56658967b7355)
tag date 2013-06-30 15:13:42 -0700
RHEL kernels are like that. They backport a ton of stuff and the major version number is of little relevance, but it doesn't change because they maintain a stable kABI.
By now the CentOS 7 kernel is probably closer to mainline 4.x and 5.x than the original 3.10
Wait until you find 2.6 (not many changes before 3.2 allegedly) and 2.4 kernels in embedded systems.
I'm well aware of 2.6 in embedded systems (and have to work with such systems T_T), I just didn't expect to see 3.10 in a system that also runs ZFS...
After 10+ years of using zfs, I just "might" know something... ;) While your 1 year old versions of ZoL just "might" not prove anything.
if you had actually been using it during the last 1.5/2 years you would know it work.
otherwise you're just talking about stuff (zfs on gnu/linux) you know little about.
if you use zfs on freebsd then good for you, but that doesn't mean you can spread disinformation about zfs-on-linux.
btw: freebsd dropped its own implementation of zfs and is rebasing onto zfs-on-linux (from 2018: https://lists.freebsd.org/pipermail/freebsd-fs/2018-December...). that's how good zfs-on-linux is.
Just update your outdated ZoL to latest version. Than we can talk. And you might just agree.
I run ZFS on both Linux and FreeBSD. On Linux I compile from the latest releases. I’ve honestly not noticed any issues either.
Are you absolutely sure this isn’t something you’ve misconfigured yourself?
For what it’s worth, I do prefer FreeBSD over Linux but not not for any reasons relating to ZFS.
This guy speaks without knowing.
I just tried going in my .zfs/snapshot on my CentOS 7 system running kernel 3.10 and ZoL 0.8.3 and it's working. I can list snapshots and cat file off a snapshot.