And you would run into divide by zero in a tiny array with less than 100 blocks, so let's put that idea permanently in the trashcan :)
And you would run into divide by zero in a tiny array with less than 100 blocks, so let's put that idea in the trash can :)
I guess this would also work, by simply avoiding the large number, in case there would be possible issues using uint64_t? out_perc = countpos / (countmax / 100);
There is no need to rebuild parity when adding an additional part to existing parity. But, once the parity has been split you can't undo the split... Instead you can later put both parts on the same device like below example from my current array: parity C:\Mnt\Duo1\p1a.par,C:\Mnt\Duo1\p1b.par,C:\Mnt\Duo2\p1c.par To expand a bit further on above example: p1a.par and p1b.par was originally stored 4 TB disks, protecting 8 TB data disks. When the disk containing p1a.par got full, the parity continued...
I believe it is this old bug: https://sourceforge.net/p/snapraid/discussion/1677233/thread/bab5f97c/#7465 TLDR: Percentage completed resets to 0% when reaching block ~42 million (~11.2 TB data on invidivudal disk with block size 256 kiB). As far as I know, it has no practical effect on anything.
Assuming that you are not getting any error messages while running fix, then I would suspect that the files were bad even before the data loss. To confirm, you could run snapraid list and compare the size listed with the size of one of the small recovered files. Unfortunately it means that you won't be able to repair any of the bad files.
Are you offended ? Are you deliberately not understanding the problem ? Yes, I'm very sensitive, thanks for noticing. But, I perfectly understand the issue. No. My test confirmed that "snapraid fix" recreates a folder with the old name (including files), but keeps the folder with the new name (including files). I repeat what I have already said. This means that we now have two folders with the same files ! Is it difficult to understand ? This was never unclear. No. This is not normal. All backup...
Are you offended ? Are you deliberately not understanding the problem ? Yes, I'm very sensitive, thanks for noticing. But, I perfectly understand the issue. No. My test confirmed that "snapraid fix" recreates a folder with the old name (including files), but keeps the folder with the new name (including files). I repeat what I have already said. This means that we now have two folders with the same files ! Is it difficult to understand ? This was never unclear. No. This is not normal. All backup...