Solaris – ZFS – How to use ZIL or L2ARC partition SSD?

I am using a Sun x4540 device with two pools and newly installed ZIL (OCZ Vertex 2 Pro) and L2ARC (Intel X25-M) devices. Because I need to Keeping these two pools, I want to know how to partition these devices to provide two data pools. I have tried format, parted and fdisk, and can’t seem to get the right combination to generate recognizable partitions for zpool add. In this case, the operating system is NexentaStor, but I also need this for general OpenSolaris solutions.
out For data integrity and performance reasons, sharing SSDs between pools is not a good idea.

First of all, ZFS needs to be able to trigger the device’s onboard cache to perform when synchronous writes are requested. Refresh to ensure that the write is indeed on stable storage before returning to the application. It can only do this when controlling the entire device. If you use slicing, ZFS cannot issue a cache refresh, and you may lose data during an unexpected shutdown. /p>

Secondly, although SSD is fast, it is still a limited resource. Sharing this resource between pools means that if the drive is busy providing IOPS from another pool, it will be viewed from the perspective of either pool. The expected performance of the device may be very different. The end result is that if you don’t use SSD at all, the performance will be worse.

ZIL and L2ARC devices dedicated to each pool are feasible methods.

p>

I am using a Sun x4540 device with two pools and newly installed ZIL (OCZ Vertex 2 Pro) and L2ARC (Intel X25-M) devices. Since I need to To keep these two pools in the short term, I want to know how to partition these devices to provide two data pools. I have tried format, parted and fdisk, and can’t seem to get the right combination to generate recognizable partitions for zpool add In this case, the operating system is NexentaStor, but I also need this for general OpenSolaris solutions.

For data integrity and performance reasons, in Sharing SSDs between pools is not a good idea.

First of all, ZFS needs to be able to trigger the device’s onboard cache to refresh when a synchronous write is requested, to ensure that the write is written before returning to the application The input is indeed on stable storage. It can only perform this operation when controlling the entire device. If you use slices, ZFS cannot Issue a cache refresh, and you may lose data during an unexpected shutdown.

Secondly, although SSD is fast, it is still a limited resource. Sharing this resource between pools means that if the drive is busy from If you provide IOPS in another pool, the expected performance of the device from the perspective of either pool may be very different. The end result is that if you don’t use SSD at all, the performance will be worse.

A pool dedicated ZIL and L2ARC equipment are feasible methods.

Leave a Comment

Your email address will not be published.