-
Help: Process to migrate to a zfs Pool
Thanks for confirming
-
Help: Process to migrate to a zfs Pool
ok. You consider the described process to be ok?
-
Help: Process to migrate to a zfs Pool
But it can be one of the old 4 TB drives, doesn't need to be like 16TB?
-
Help: Process to migrate to a zfs Pool
I'm planning to get my server to zfs. Current setup Array: 2 x 16TB HDD, 3 x 4TB HDD Cache: 1 SSD I would like to install another 16 TB HDD in order to form a zfs pool. The 4TB drives will then get obsolete. What is the best way of doing this without loosing data and keeping my existing shares/docker/setup/ in place? I'm thinking of the following process, and I'm not sure it works this way 1. Move everything away from the 16 TB Data disk 2. Change the config: 2.1 Remove the parity drive from the array. 2.2 Exchange one of the (empty) 4 TB drives with the new 16 TB drive 2.3 Build a zfs pool with the 3 x 16 TB drives (raidz) 2.4 Add zfs pool to array 3. Move everything from the 4TB disks (and from other sources) back to the new array 4. Remove the 4 TB drives from the array Two questions: Will the process work this way? If I understand it correctly there is no "Unraid" Parity drive anymore but zfs will take care of the parity among the 3 drives. Thanks in advance
-
-
[6.12.2] zfs write speed very slow (e.g. ~ 30MB/S)
I'm trying to convert my btrfs drives to zfs by * moving everything away from the btrfs drive * reformat to zfs * and then move back to the newly formatted zfs However, zfs is extremely slow. Write speed around 30MB/s, sometimes even lower. Tried the unbalance plugin but also used rsync, also tried it with different values for --bwlimit, as found in in the forum for Prereleases. Not much change, see the attached plugin screenshot where the target disk4 is formatted with zfs. Not sure if I'm doing something wrong but with this speed, zfs is close to be unusable. tower-diagnostics-20230711-1630.zip
hulk66
Members
-
Joined
-
Last visited