1,034
edits
Equipment/Lattner: Difference between revisions
From London Hackspace Wiki
m
→Disk Configuration
m (Formatting issues and links.) |
|||
| Line 37: | Line 37: | ||
* 4 1TB drives connected directly to the motherboard SATA ports. | * 4 1TB drives connected directly to the motherboard SATA ports. | ||
* System is using ZFS in a RAIDZ2 (Double-Parity) RAID providing 1800GiB of usable storage | * System is using ZFS in a RAIDZ2 (Double-Parity) RAID providing 1800GiB of usable storage: | ||
* zpool was created using device-aware /dev/disk/by-id rather than generic /dev/sda,sdb,sdc,sdd enumeration to help facilitate disk replacements when a drive goes down | pool: chris | ||
state: ONLINE | |||
scan: none requested | |||
config: | |||
NAME STATE READ WRITE CKSUM | |||
chris ONLINE 0 0 0 | |||
raidz2-0 ONLINE 0 0 0 | |||
ata-Hitachi_HUA721010KLA330_GTA060PBK2ZY1F ONLINE 0 0 0 | |||
ata-Hitachi_HUA721010KLA330_GTA060PBKEVKZF ONLINE 0 0 0 | |||
ata-Hitachi_HUA721010KLA330_GTA060PBKEWNTF ONLINE 0 0 0 | |||
ata-Hitachi_HUA721010KLA330_GTA060PBKEWX4F ONLINE 0 0 0 | |||
** zpool was created using device-aware /dev/disk/by-id rather than generic /dev/sda,sdb,sdc,sdd enumeration to help facilitate disk replacements when a drive goes down. And by labeling the outside of the drive-tray with the disk serial number, we can easily reconcile the serial number of a failed/failing drive with one that is in the array. | |||
* Boot drive is simply a single SSD - it shouldn't hold anything precious nor be used as a caching device as there is sufficient system memory and ZFS can likely manage caching automatically. | * Boot drive is simply a single SSD - it shouldn't hold anything precious nor be used as a caching device as there is sufficient system memory and ZFS can likely manage caching automatically. | ||
