[s3ql] OSError: [Errno 14] Bad address

I am in the process of crafting a s3ql backed backup solution. During the development/testing I left the store mounted, installed some system updates and rebooted. Now I am unable to mount and/or check the store. Running 2.12 on ArchLinux. It has been several hours since I last wrote to

Re: [s3ql] OSError: [Errno 14] Bad address

Jeff Bogatay j...@bogatay.com writes: I am in the process of crafting a s3ql backed backup solution. During the development/testing I left the store mounted, installed some system updates and rebooted. Now I am unable to mount and/or check the store. Running 2.12 on ArchLinux. It has been

Re: [s3ql] Looking for best practices and some beginners questions: Using s3ql as backup target

Nikolaus Rath nikol...@rath.org writes: 4) How can I realize an additional backup of (the current state of) an s3ql file system e.g. to an external drive? Not easily. Instead I'd suggest to run an rsync job from your data directory to an S3QL mount point, and to your external drive. See

Re: [s3ql] Reduced file handles?

Rabid Mutant rabidmutantstarg...@gmail.com writes: I must admit I see the 'rsync -c' option as a much stronger guarantee than a copy based on file dates sizes, and this could be irrational. But, if 100% cache can be achieved at nearly zero performance impact *and* it supports rsync -c as well