Okay, the spuds and the drives work like a charm:
[root@ultralord ~]> format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t1d0 <DEFAULT cyl 30391 alt 2 hd 255 sec 63>
/pci@0,0/pci108e,5351@1f,2/disk@1,0
1. c0t3d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 126>
/pci@0,0/pci108e,5351@1f,2/disk@3,0
2. c0t4d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 126>
/pci@0,0/pci108e,5351@1f,2/disk@4,0
Specify disk (enter its number): ^D
I want to create a pool for building kernels:
[root@ultralord ~]> zpool create builds c0t3d0 c0t4d0 [root@ultralord ~]> df -h /builds Filesystem size used avail capacity Mounted on builds 1.1T 19K 1.1T 1% /builds
Hmm, while I like the space, these are 640G HDs. Wait, I didn't use raidz:
[root@ultralord ~]> zpool destroy builds [root@ultralord ~]> zpool create builds raidz c0t3d0 c0t4d0 [root@ultralord ~]> df -h /builds Filesystem size used avail capacity Mounted on builds 587G 19K 587G 1% /builds
Much better - now I need to get some source and let it rip!
With two disks, a mirror would probably perform better.
Posted by Mark J Musante on April 19, 2009 at 11:14 PM CDT #
2-disk raidz? for builds? just use a mirror and save the cpu for your compiler.
Posted by Dan on April 21, 2009 at 04:10 AM CDT #
Okay, let me play more dumb here:
1) Why mirror over having more space?
I.e., when is redundancy more important than space?
2) How many disks does it take to get to the center of raidz?
Ignore whether these are for builds or not.
3) Does the answer change for the casual home user with a limited number of drive bays versus someone able to add a drive pack?
Posted by Tom Haynes on April 21, 2009 at 11:06 AM CDT #