Диск Zfs конфигурируется на FreeNas

Нет, нет никакого способа, которым можно добавить таблицы к репликации на лету.

Можно считать его в документах:

Другие, такой как - копируют -* опции, может быть установлен только, когда ведомый сервер запускается.

2
задан 17 October 2012 в 07:43
1 ответ
  1. If your raid-z VDEV has mixed spindle speeds speeds performance will be like the slowest disks (IO will arrive sooner from the 7200rpm disks, but will wait for data from the 5400rpm before the block is reconstructed.) Your greens are somewhere in the 5400-5900rpm range.

  2. (A) Data security: mirror wins. You'd survive a single disk failing and if you were lucky (33% chance) you could survive a second disk too. Rebuild times are faster with mirrors too. (B) Performance: mirror wins. Double the write performance, better read performance since simultaneous reads are serviced by both halves of the mirror. (C) Capacity (not asked): with mismatched disk sizes raid-z will be limited to the smallest disk (2x1TB + 2x3TB acts just like 4x1TB, so 3TB usable). With mirrors you get all that capacity (2x1TB + 2x3TB = 4TB usable).

  3. A random extra hard disk as L2ARC or ZIL likely won't yield measurable performance gains for most workloads. Maybe as ZIL if the disk was faster than pool media (10k vs 7200rpm). If used as L2Arc maybe a few extra pool IOPS could be eeked under load from any L2Arc cache hits, but I can't imagine it's worth it using an extra old hard drive.

Don't forget to use ashift=12 at pool creation time if your disks have 4K sectors (WD 1TB Green 'EARS' Drives do).

1
ответ дан 3 December 2019 в 13:04

Теги

Похожие вопросы