kretos

For me, this was the reason to exclude most of smaller files (pictures). Parallel scanning and the ability to include/exclude directories on-the-fly when scanning (not after), that would be great

Thanks once more. I'm aware of the parity demands. I always leave free space on hdd to allow proper defrag, also I will put only big files so it shouldn't be a problem. I've tried to hash ma image files but i've got almost 2 million files - content file was over 1.2 GB big and crawling throught directories took almost 20 minutes. So i've decided to just make simple copy on external hdd. I can afford for 3TB for images but not 15TB for all my files:)

Thank you very much for your explanation! About 2&3 - great design! I thought that snapraid uses physical structure of hdd and it will require bigger parity that data disc even if inclusion and exclusion is used and only part of data should be protected. Good to know that it uses its own logical connection. About 5 - more suggestion or wish than question. Is there any thread were some improvements can be written? About 6 - I thought of maximum size - so no smaller gap would be present - sth like...

Hi everyone. I'll be a new user of snapraid but I have few doubts that were not cleared after reading manual and faq and searching through forum (honestly - maybe it was answered before but there are 60 pages to look through...). So here are my questions: 1. How exactly files from different data drives are matched to compute parity? Since snapraid support splited parity drives is it not based on cluster (sector) number? Or maybe it's based but snapraid adds offset on splited parity (place on second...

Hi everyone. I'll be a new user of snapraid but I have few doubts that were not cleared after reading manual and faq and searching through forum (honestly - maybe it was answered before but there are 60 pages to look through...). So here are my questions: 1. How exactly files from different data drives are matched to compute parity? Since snapraid support splited parity drives is it not based on cluster (sector) number? Or maybe it's based but snapraid adds offset on splited parity (place on second...

Hi everyone. I'll be a new user of snapraid but I have few doubts that were not cleared after reading manual and faq and searching through forum (honestly - maybe it was answered before but there are 60 pages to look through...). So here are my questions: 1. How exactly files from different data drives are matched to compute parity? Since snapraid support splited parity drives is it not based on cluster (sector) number? Or maybe it's based but snapraid adds offset on splited parity (place on second...

Hi everyone. I'll be a new user of snapraid but I have few doubts that were not cleared after reading manual and faq and searching through forum (honestly - maybe it was answered before but there are 60 pages to look through...). So here are my questions: 1. How exactly files from different data drives are matched to compute parity? Since snapraid support splited parity drives is it not based on cluster (sector) number? Or maybe it's based but snapraid adds offset on splited parity (place on second...

Hi everyone. I'll be a new user of snapraid but I have few doubts that were not cleared after reading manual and faq and searching through forum (honestly - maybe it was answered before but there are 60 pages to look through...). So here are my questions: 1. How exactly files from different data drives are matched to compute parity? Since snapraid support splited parity drives is it not based on cluster (sector) number? Or maybe it's based but snapraid adds offset on splited parity (place on second...