You are not logged in.
Is anyone saving par2 data with their backups? I like keeping my backups as full filesystems rather than tar/dar etc files as it's a bit easier to grab a single file and I like that par2 data gets stored in external files.
I'm looking at adding it to my backups to help with degradation or the occasional bad command line. It looks like you can create par2 files recursively on a directory. Does anyone else do this? I'd be interested to hear suggestions on choosing a block size or if there are any other tools worth investigating. par2commandline doesn't seem to give much information on efficiency to help guide on a choice of parameters like some of the windows-based par2 programs do.
My first attempt was with a command like this one:
$ nice -n 19 ionice -c3 par2create -n1 -r1 -m1024 -R -a $backupdir.par2 $backupdir
Block count (2000) cannot be smaller than the number of files(20711).But the default blocksize/blockcount is apparently too small for the number of files. I played around with the -s and -c parameters bouncing between these two errors:
Block size is too small. It would require 410424blocks.
Block count (2000) cannot be smaller than the number of files(20711).Eventually I decided to just pick a block count a bit higher than the number of files I have (21000) and it completed successfully but the resulting par2 files used about 29GB to store 1% parity on a 33GB directory. Not very efficient. It would be great to learn a strategy for choosing some more useful parameters or a more suitable tool.
Offline