This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
Replaces old_device with new_device. This is equivalent to attach-
ing new_device, waiting for it to resilver, and then detaching
old_device.
The size of new_device must be greater than or equal to the minimum
size of all the devices in a mirror or raidz configuration.
Partition the HDD and give only the partition to ZFS. [...] This strategy is only useful when setting up a new array. The idea is to use slightly less than your entire HDD. Thus, if a replacement HDD happens to be smaller, you're covered.
x64 9.1.0.1 (revision 636) embedded | Asus P5Q Pro + Q9550 | onboard Atheros AR8121 | 8 GB DDR2 | Dell PERC H200 with IT firmware | 3x 2TB WD Caviar Red with RaidZ1 | U204FB-A2 HD44780 LCD (updated 27/02/2013)
I do not recomend to partition disk before to adding it to a pool, but I recommend to label it ( using gpart like descrived on your link) to easy manage/administration of disk in the pool.
PD: adax may / can change if you add new disk, labels do not change.
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)
yes, but the problem is not ZFS is that you identify your device in case you need to replace / delete / etc... or if you use UFS or Raid sollutions.
12.1.0.4 - Ingva (revision 7743) on SUPERMICRO X8SIL-F 8GB of ECC RAM, 11x3TB disk in 1 vdev = Vpool = 32TB Raw size , so 29TB usable size (I Have other NAS as Backup)