Jessie Taylor

To be clear, the problems that Walter refers to are mainly related to the size of data on data drives versus available parity space. With compression, deduplication, and more efficient storage of small files on a data drive, you are more likely to run into a problem with the effective data size of a data drive being too large for parity drives. If your parity drive is significantly larger than your largest btrfs data drive, or if none of your btrfs data drives are close to full, then you are much...

I suspect the OP meant that the UUID of the OS drive changed when the new OS was installed. There is nothing SnapRAID can do about that. The OP will have to fix it manually. The partition UUIDs can be edited manually and the /etc/fstab updated accordingly. Although I tend to avoid UUIDs and instead label the partitions so that this sort of problem is easier to deal with.

I suspect the OP meant that the UUID of the OS drive changed when the new OS was installed. There is nothing SnapRAID can do about that. The OP will have to fix it manually. The partition UUIDs can be edited manually and the /etc/fstab updated accordingly.

I suspect the OP meant that the UUID of the OS drive changed when the new OS was installed. There is nothing SnapRAID can do about that. The OP will have to fix it manually.

I suspect the OP meant There is nothing SnapRAID can do about that. The OP will have to fix it manually.

I suspect the OP meant that the UIDs and GIDs no longer correspond with the usernames and group names in /etc/passwd and /etc/group There is nothing SnapRAID can do about that. The OP will have to fix it manually.

The parity file in SnapRAID is almost like its own filesystem, and as such, it can become fragmented if you add and delete files from your data drives. Now Andrea can correct me if I am wrong here, but I think SnapRAID is still able to utilize all the space in the parity file, even if it becomes fragmented. But SnapRAID is not able to shrink the parity file if it is fragmented. So after a while, if you had one or more data drives full and then deleted files, your parity file may be larger than it...

You should definitely exclude frequently changing files that are not important to backup. When you run a sync, SnapRaid should behave as if you deleted those files and it should recompute parity without those files. It will not be a complete rebuild. It will probably add some fragmentation to the parity file(s).