Zoroeyes

That looks excellent steini84, exactly what i was looking for (hopefully others too). thanks for taking the time to put it together.

That sounds great steini84, appreciate it and will look forward to it.

Ok, so I’ve been reading like crazy about zfs and I’ve been creating, destroying and recreating zpools to try to understand how it all works. However, like many, I’m not quite piecing it all together. I’ve can create a zpool (say zfspool), I can see what drives it uses and that it’s status is all good. I can set the mountpoint to say /mnt/zfs (which I’m afraid is confusing me a little) but then I run out of steam. Basically all I want to use it for it to group 4 devices into effectively a raid-set and use it for a VM (if I learn more about zfs then I might be brave enough to use it for more things like dockers etc., but a single VM would be a start). I wonder if someone with zfs knowledge would mind doing a generic, idiots guide to the most common setups so people like me could make use of this awesome plugin/technology. These might include: configuring a zpool for a vm, on unRaid, start to finish. Configuring a zpool for a general samba share, on unRaid, start to finish. If all we’ve got to do is swap out our device names and pool names, then I think this would really help guys like me understand how the more general use-cases work in the unRaid environment. I know basic guides do exist (like level1techs), but they all seem to stop at the point where the pool is created, so I can’t progress past that point, I’d like to see someone take that pool, give it a real mount-point and create a VM (on unRaid) using that same pool. Please understand I have tried to read as much as possible about the subject, but not being a Linux guy, even the main concepts are quite alien to me (and I’m sure others). Any help would be much appreciated Thanks in advance

Brilliant, I certainly will, look forward to giving this a try, and seeing what kind of performance I can get out of those NVMEs!

Excellent, thanks steini84, I didn’t realise that had been implemented yet. I had read about it being available in some implementations, but didn’t for a second think it’d be the one I actually wanted to use! So with auto trim, is it ‘set and forget’? No periodic commands etc?

Apologies if this is covered elsewhere, but if I wanted to use this to create a 4x NVME vdev with 1 disk parity (like a raid 5), how would I deal with TRIM and would this become an issue?