On Mon, Mar 17, 2014 at 11:47:29AM -0700, Nemo Inis wrote: > I upgraded to obnam 1.7.1 (digression here: the Debian changelog for 1.7.1 > should have carried the same mention of possible repository corruption that > website News did carry. As a debian user, the Debian changelog/alert mechanism > is the only thing I'm likely to see during a 100+ packages upgrade).
Agreed. Mea culpa. > However, 'obnam mount' fails to properly access any file > 64KB. md5 > shows differing checksums, diff fails, and a 'cp backedfile > /tmp/restoredfile' command either fails silently having copied only > part of the file, or else dies with this error: Thank you for noticing this! It turned out to actually be something that depends on how much data the program reading the file from the FUSE filesystem requests at a time. Luckily, it was a simple fix, and I will be uploading a new version of Obnam to fix this soon. -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
