Copying the file data over https://unix.stackexchange.com/q/30970/50703 # via rsync, file by file progress

flipou83 · 24dI have a M1 but all my storage is on a TrueNAS and Unraid server. Doesn't trust external drive storage for the problems you listed on your post. I have a share for it's TimeMachine backups and big Photos library and iMovie Library which don't even fit on the internal SSD of the Mac mini.I would put the SSD you bought into an independent computer that acts as a NAS on your network. What about this solution?

1. Back up data to an external drive, and sign out Apple ID if needed.2. Enable root user. Install OpenZFS.3. Delete user accounts including the home directories. Do not delete the Data APFS volume. 4. Partition disk. Choose a format other than ZFS dataset.5. Disable System Integrity Protection to allow mounting on /Users.6. Log in to root user.7. Create zpool on the new partition. I set the compression property to on.8. Create ZFS file system for /Users with mountpoint property set to /Users. You may create descendent file systems for each users.9. Verify the file systems are mounted after boot with root user.10. Add user accounts.11. Log in to user accounts and check if the home directory is a ZFS file system.12. Restore backed up data.

RAID is complicated, and getting it right is difficult. You don’t want to wait until your drives are failing to learn about a gap in your understanding of RAID. For this reason, I recommend ZFS to most. It automatically makes good decisions for you with respect to mirroring and parity, and gracefully handles rebuilds, sudden power loss, and other failures. It also has features which are helpful for other failure modes, like snapshots. Set up Zed to email you reports from ZFS. Zed has a debug mode, which will send you emails even for working disks — I recommend leaving this on, so that their conspicuous absence might alert you to a problem with the monitoring mechanism. Set up a cronjob to do monthly scrubs and review the Zed reports when they arrive. ZFS snapshots are cheap - set up a cronjob to take one every 5 minutes, perhaps with zfs-auto-snapshot.

Databases If databases data is stored on a ZFS filesystem, it’s better to create a separate dataset with several tweaks: zfs create -o recordsize=8K -o primarycache=metadata -o logbias=throughput -o mountpoint=/path/to/db_data rpool/db_data recordsize: match the typical RDBMSs page size (8 KiB) primarycache: disable ZFS data caching, as RDBMSs have their own logbias: essentially, disabled log-based writes, relying on the RDBMSs’ integrity measures (see detailed Oracle post)

ZFS native encryption: zpool create -o ashift=12 \ -O acltype=posixacl -O canmount=off -O compression=lz4 \ -O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa \ -O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase \ -O mountpoint=/ -R /mnt rpool ${DISK}-part4

Then create a file with the key (ex 31 x 1) echo 1111111111111111111111111111111 > /key.txt Then create an encrypted filesystem ex enc on your "pool" based on that key zfs create -o encryption=0n keyformat=raw -o keylocation=file:///key.txt pool/enc

zfsembedsdatadirectlyinalogentry.Forlargeval-ues,itwritesdatatodiskredirect-on-write,andstoresapointerinthelog[21].Thisgiveszfsfastdurabilityforsmallwritesbyflushingthelog,avoidstheoverheadofwritinglargevaluestwice,andretainstherecoveryse-manticsofdatajournaling.Ontheotherhand,btrfs[26]usesindirectionforallwrites,regardlessofsize.Itwritesdatatonewly-allocatedblocks,andrecordsthosewriteswithpointersinitsjournal