F. Wessels wrote:
Hi,
as Richard Elling wrote earlier:
"For more background, low-cost SSDs intended for the boot market are
perfect candidates. Take a X-25V @ 40GB and use 15-20 GB for root
and the rest for an L2ARC. For small form factor machines or machines
with max capacity of 8GB of RAM (a typical home system) this can make a
pleasant improvement over a HDD-only implementation."
For the upcoming 2010.03 release and now testing with a b134.
What is the most appropiate way to accomplish this?
The caiman installer allows you to control the size of the partition on the boot disk but it doesn't allow you (at least I couldn't figure out how) to control the size of the slices. So you end with slice0 filling the entire partition.
Now this leaves you with two options, create a second partition or start a complex process of backing up the root pool, reslicing the first partition, restore the root pool and pray that the system will boot again.
I tried the first, knowing that multiple partitions isn't recommended. I
couldn't get zfs to add the second partition as L2ARC. It simply said that it
wasn't supported.
Before I try the second option perhaps somebody can give some directions howto
accomplish a shared rpool and l2arc on a (ss)disk.
Regards,
Frederik
As I think was possibly mentioned before on this thread, what you
probably want to do is either:
(a) create a zvol inside the existing rpool, then add the zvol as an L2ARC
or
(b) create a file in one of the rpool filesystems, and add that as the L2ARC
Likely, (a) is the better option.
So, go ahead and give the entire boot SSD to the installer to create a
rpool of the entire disk, then zvol off a section to be used as the L2ARC.
--
Erik Trimble
Java System Support
Mailstop: usca22-123
Phone: x17195
Santa Clara, CA
Timezone: US/Pacific (GMT-0800)
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
