RAID1 with 2 SSDs - on board RAID or ZFS?

[wywywywy]

Hi all,

I have a spare HP Microserver N54L that I want to put Proxmox on and have a go.

It will have two SSDs only in RAID 1. But should I use the built in RAID 1 of the storage controller, or do it through ZFS? Is there any practical difference? And how about TRIM support?

On a related note, is MLC vs 3D-TLC still a thing? Or does it not matter nowadays?

Thanks.

 

[Richard]

It will have two SSDs only in RAID 1. But should I use the built in RAID 1 of the storage controller, or do it through ZFS?

Deactivate HW RAID and use ZFS

Is there any practical difference?

ZFS has additional security features.

And how about TRIM support?

Supported.

 

[wywywywy]

Well that settles it then! Thank you.

 

[Rhinox]

And how about TRIM support?

Supported.

Not in case of ZFS on Linux

 

[wywywywy]

Actually I followed the link to the Github issue and the thread seems to suggest that the change has been merged?

 

[fabian]

nope, it has been closed in favor of a new PR: https://github.com/zfsonlinux/zfs/pull/5925 which has not been merged yet (and when it gets merged, in will be released with 0.8 or even 0.9, and not as part of a 0.7 bug fix update)

 

[wywywywy]

Thanks. I think I'll go for ZFS anyway. Hopefully the built-in garbage collector works ok.

I've got the 2 SSDs delivered today and I'm currently burning the ISO and printing the 2.5 to 3.5 adapters for use in the caddies.

 

[joshin]

Didn't realize the lack of TRIM on ZFSOnLinux. Ugh, no wonder my zvols are slowing down - even with decent drives (S3610's).

 

[Rhinox]

You can eliminate it (at least partially) by keeping enough free space for garbage collection. I have left ~20% unallocated, and i/o-speed seems to be not changing...

 

[joshin]

Yeah thanks, I had an oops that made a mess of things on that server. Didn't have autoexpand set when swapping out bigger drives, and the zpool filled b/c I moved more to it & missed that it hadn't expanded. I probably just need to nuke it and rebuild.

You can eliminate it (at least partially) by keeping enough free space for garbage collection. I have left ~20% unallocated, and i/o-speed seems to be not changing...