Timeline for New disk array on linux
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2 at 7:29 | comment | added | cas | Finally, to improve performance: make sure that the system has enough RAM for normal usage PLUS another 16 or 32 GB or more for ARC caching. And optionally add an SSD (or use a partition on an existing SSD) for L2ARC caching (so that frequently read data comes from the SSD rather than direct from the HDDs). | |
| Jul 2 at 7:21 | comment | added | cas | The reason I say "get another drive if you can" is because this can't be done safely with only two empty drives, but can be done with some risk by starting with a two-drive DEGRADED RAIDZ-1 pool, copy the data from one original drive then add that to the zpool (so it's no longer degraded). Then copy the data from the second original drive and then add that to the zpool. End result, a 4-drive RAIDZ-1 array, with total capacity of 30TB, not including zstd compression (which won't be significant if the files are mostly already-compressed videos, music, photos, etc) | |
| Jul 2 at 7:18 | comment | added | cas | or, if the OP can afford one more 10TB drive (and it can physically fit into the machine), start with a 3-drive RAIDZ-1, copy the data from the original two drives to it, and then use ZFS' relatively recent (2022-ish) RAIDZ expansion feature to expand it to a 5-drive RAIDZ-1. And then use zfs snapshot, zfs send, and zfs receive to force a rewrite of all data to take full advantage of the new layout). | |
| Jul 1 at 13:14 | history | edited | hardillb | CC BY-SA 4.0 |
added 255 characters in body
|
| Jul 1 at 9:44 | history | answered | hardillb | CC BY-SA 4.0 |