On Tue, Mar 7, 2017 at 11:55 AM, Solène Rapenne <sol...@perso.pw> wrote:
> Le 2017-03-07 17:29, Roderick a écrit : > >> Before I make a decision, I want to ask you for suggestions. >> >> I want to make a small file server, just to separate important >> files from my working system. Two disks as Raid 1. Files are to >> be read with NFS. Emphasis: >> >> (1) Data Integrity (not security :). >> >> (2) some degree of indepencence from hardware and operating system. >> Disk are to be readable for many decades. Standard File System >> readable after moving the Disks to another computer, different >> hardware, perhaps with different OS. >> >> I was thinking on doing it with FreeBSD and ZFS. I find the last >> interesting because: (a) it make checksums and corrections if >> a checksum in a disk is wrong (using the other disk in the array), >> (b) many OS are implementing it. But I find horrible how >> resource hungry it is. >> >> Do you have an idea? >> >> I do preffer OpenBSD, but is there an appropriate file system >> for archiving? >> >> I thank for any suggestion >> Rodrigo. >> > > > Hello, > > I have my private file server using OpenBSD. That's not the best system > for that but it works. > If you are comfortable with and you don't need extra speed, that will be > ok. > > For data integrity, you may use sysutils/bitrot to check for data > integrity (bit rot). > With OpenBSD, you won't get snapshots, on-the-fly compression etc... > 2 cents: vnconfig /bioctl for RAID1 + CRYPTO for the partition ? CRYPTO will indirectly check for error and RAID1 create redondancy and a way to snaphots all of that. Maybe CRYPTO compress data , or was it a removed option ? > Don't forget backups, that the most important thing for your file server > :-) > > Regards > > -- -- Knowing is not enough; we must apply. Willing is not enough; we must do
