Are there any volunteers willing to do testing of ZFS on RedSleeve? This will involve both zfs-fuse and in-kernel ZFS.
zfs-fuse: I have been using zfs-fuse for years on ARM without any issues, so the testing of this will primarily be for use as rootfs (I am working on porting zfs-dracut from ZoL to zfs-fuse). ZoL (in-kernel): This is far, far more experimental. I recently lost a 4x4TB RAIDZ2 pool on ARM to ZoL within minutes of trying to use ZoL. In fairness, I saw this coming, and my backups are pretty good, but it was still inconvenient. I tried to reproduce it on my Chromebook (EL7 rather than EL6, different kernel), and I tripped a different, far less serious bug, but cannot reproduce the pool trashing bug (could be that it only affects RAIDZ2 pools, or it's even more obscure). Either way, if you volunteer for this one, only use this on a machine you re-image regularly anyway, and don't put any data of any value on it. It goes without saying that you will need the kernel-devel-$(uname -r) package (or at least configured kernel sources in /usr/src/kernels/$(uname -r)/ ) to even build spl-dkms and zfs-dkms modules. I'll be moving one of my ARM laptops to ZoL rootfs (must be brave ;) soon, to facilitate more testing, but I re-image this a few times per month, so if/when it blows up it is neither unexpected nor a big deal. But without testing and hunting down bugs, things will never get better. So to recap: zfs-fuse: stable, in my experience suitable for production use. ZoL: definitely not problem free, much testing and bug reporting required. Gordan _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
