On Tue, Nov 23, 2010 at 9:59 AM, taemun <tae...@gmail.com> wrote: > I'm currently populating a pool with a 9-wide raidz vdev of Samsung HD204UI > 2TB (5400rpm, 4KB sector) and a 9-wide raidz vdev of Seagate LP ST32000542AS > 2TB (5900 rpm, 4KB sector) which was created with that binary, and haven't > seen any of the performance issues I've had in the past with WD EARS drives. > It would be lovely if Oracle could see fit to implementing correct detection > of these drives! Or, at the very least, an -o ashift=12 parameter in the > zpool create function.
What is the "upgrade path" like from this? For example, currently I have b134 OpenSolaris with 8x1.5TB drives in a -Z2 storage pool. I would like to go to OpenIndiana and move that data to a new pool built of 3 6-drive -Z2s (utilizing 2TB drives). I am going to stagger my drive purchases to give my wallet a breather, so I would likely start with 2 6-drive -Z2s at the beginning. If I was to use that binary/"hack" to force the ashift for 4k drives, I should be able to "reconcile" and upgrade to a zpool version down the road that is happy and aware of 4k drives? I know the safest route would be to just go with 512-byte sector 7K2000s, but their prices do not drop nearly as often as the LPs or F4s do. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
