Interesting. Seems to be in our ports tree as well. Now I know what I'm doing this evening. :)
On Jul 20, 2016 9:29 AM, "Scott Bonds" <sc...@ggr.com> wrote: > Take a look at par2. https://en.wikipedia.org/wiki/Parchive > > On 07/20, Miles Keaton wrote: > >> Got a fileserver with a few terabytes of important personal media, like >> all >> old home movies, baby photos, etc. Files that I want my family to have >> access to when I die. >> >> Really it's more of a file archive. A backup. Just rsync + ssh. Serving >> it isn't the point. Just preserving it forever. >> >> (It's all unencrypted. It's not that kind of private. Private and >> offline >> from the outside world, but public within the family.) >> >> For years it's been on a Synology, Linux ext4 filesystem. Now I'm making >> a >> new clone of it (new PC) to be in a different location. >> >> I assumed I'd use FreeBSD + ZFS because of ZFS's checksum features. But >> really I love and prefer OpenBSD for everything else, and don't want any >> other ZFS features : just that checksum. >> >> So I figure if I use OpenBSD + softraid RAID 5 (across 4 disks) and then >> write my own little shell script to track the MD5 (find . -type f -exec >> md5 >> {} \;) whenever I make changes, that should be enough to see if a file has >> been changed due to disk corruption. >> >> (Which makes me realize I don't know a damn thing about disk corruption, >> only that it's happened a few times in the past. The occasional JPG or >> MP3 >> from the late 90s that used to work but now doesn't, and who-knows-why.) >> >> Before I embark on this direction for a fileserver, I thought I should >> check with the smart people here on misc: >> >> Any tips from anyone who's done something similar? >> >> Or would anyone advise me against OpenBSD or this MD5 log approach for a >> fileserver like this? >> >> Thank you.
