Mirror / Raid 1: ZFS+Parity or Zpool Raid1

[foo_fighter]

Let's say I only have 2 identical disks.

Both Unraid Parity with 1 ZFS Disk and A Zpool would be considered "Mirrors" with the same information identically stored on both drives.

But it seems like there are some subtle differences:

A Zpool would have bitrot protection(A Scrub would auto fix it) but Unraid parity would not(Need to restore from Backup if Integrity plugin indicates mismatches)?

Both can provide ZFS snapshots.

Unraid Parity: Reads only would only require 1 drive to spin up, Would a Zpool require both drives to spin up?

Expanding: Unraid Parity is easier to expand with extra drives without touching existing data. I'm not an expert but it seems like you cannot change a ZMirror to a RaidZ1(Parity) easily? You have to destroy/rebuild the pool? 

A build with Zpools only needs a dummy parity assigned(could be USB)?

Mover can move from Cache Pool to Array. Can it also now be configured to Move from 1 Pool to another Pool?

 

Any other pros/cons/differences between the 2?

Edited November 27, 2023 by foo_fighter
added mover question

[JorgeB]

6 hours ago, foo_fighter said:

Unraid Parity: Reads only would only require 1 drive to spin up, Would a Zpool require both drives to spin up?

Yes, but reads would be faster since it's stripes from both devices.

 

6 hours ago, foo_fighter said:

A build with Zpools only needs a dummy parity assigned(could be USB)?

Can be an old flash drive.

 

6 hours ago, foo_fighter said:

Any other pros/cons/differences between the 2?

Array won't support TRIM, if you use SSDs.