How do I do that with NVMe drives? Do I create a smaller namespace? Or create a partition on a large namespace?Yes you can do it that way. Did it myself exactly like you have described.
I'm using a 1TB PM953 which is rated for 1.3DWPD. It has PLP. I'm intending to overprovision, using only 50GB of the drive. So that should increase lifespan by around 20x?Are you certain your NVMe is designed to the heavy rewrites happening on the SLOG device?
If you are using consumer grade hardware the lifetime of your SSD will be around 1-4 weeks depending..
You would probably also want to mirror your SLOG device. It is no fun to loose the pool due to a single SSD failure. These cases have been seen. Fixed since pool version 19
Also is your SSD battery backed? You will need that in case of poweroutage.
NVMe drives have the main nvme0 drive which is sometimes divided into multiple namespaces like nvme0n1 nvme0n2 etc. Am I supposed to use gpart to create a small partition over a single nvme0n1 that fills the whole drive or am I supposed to create a small namespace nvme0n1 and leave the rest in nvme0n2?I dont get your question.
Nvme is not different to any other block device.
You have a physical device and either throw that completely into the pool or you partition it and assign the partition to the pool.
The term you are looking for is "short stroking". This means you are making the usable space much smaller as the whole disk. This can either done by partition or by drive configuration itself.. I'm intending to overprovision, using only 50GB of the drive.
I'm using a 1TB PM953 which is rated for 1.3DWPD. It has PLP. I'm intending to overprovision, using only 50GB of the drive. So that should increase lifespan by around 20x?
NVMe drives have the main nvme0 drive which is sometimes divided into multiple namespaces like nvme0n1 nvme0n2 etc. Am I supposed to use gpart to create a small partition over a single nvme0n1 that fills the whole drive or am I supposed to create a small namespace nvme0n1 and leave the rest in nvme0n2?
Appreciate the reply but that's actually not my question. My question was should the partition be a full partition of a separate namespace or a slice of the full namespace that covers the whole drive?A slog device usually does not need to be much bigger than 10-20GB as they only need to hold few seconds of data before they are written to the underlying storage devices disks or ssd.
The problem is that the ZIL afaik does not support TRIM
apt-get install nvme-cli
nvme<TAB>
You will find a nvme delete-ns command which you can use to delete the ns's you dont need.
As has already been stated, ZIL does not need much as it only holds a few seconds of writes. The rest of your question has been answered I believe, otherwise hit me up again, I just woke up and haven't had breakfast yet
Wow, nice!PS: One of the best solutions for ZIL is one of these, or two:
https://www.radianmemory.com/edge-card-rms-300/
No, but I'm also intrigued. Currently I use Optane for this.Would they work out of the box?
Anyone tried those in real live?