Bug#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)
On Sun, Mar 30, 2014 at 08:49:44PM -0700, Nemo Inis wrote: On 30/03/14 09:39 AM, Lars Wirzenius wrote: I've applied a patch from Valery to fix this, I hope. If you can try Obnam from git master, could you do so and tell me if obnam mount now works for you? You don't need to run a new backup. That seems to have fixed it; I've tried various ways to get backed data out of, or use it directly from, the repository and everything worked fine. Thanks for the hard work, gentlemen! Thanks, Nemo. I'll make a release as soon as I can. -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)
Hi, Nemo, I've applied a patch from Valery to fix this, I hope. If you can try Obnam from git master, could you do so and tell me if obnam mount now works for you? You don't need to run a new backup. To do that, the following steps should work: * git clone git://git.liw.fi/obnam * cd obnam * python setup.py --quiet build_ext -i * ./obnam mount Add your usual command line arguments for obnam mount to that last line, but do run it with the leading ./ so that you run Obnam from the source tree and not the installed version. I am going to be making a new release soon. If you can't test this before then, that's OK, but if you can, that would be nice. An indication later on that it's fixed would also be useful. I'll leave the bug open until you've confirmed it works for you now. On Sat, Mar 22, 2014 at 06:55:56PM -0700, Nemo Inis wrote: Hi Lars, I don't think the problem is fully fixed. I'm still getting weird errors depending how I read the backed up files from the fuse-mounted repository. As an example, I've attached an annoted terminal session showing how if I try to read an epub (with Calibre's ebook-viewer) from a fuse-mounted repo, I get corruption. But if I first copy it out using cp then it's OK. Bizarre stuf... Cheers Nemo backupfuse/Books is an obnam mount of the latest generation /Books is the folder that was backed up ebook-viewer is the Calibre ebook-viewer (v1.23), written in python $ md5 backupfuse/Books/handbook.epub --A) CHECKSUM OK 06d524ff85facfc2993e67ef6494d05f backupfuse/Books/handbook.epub $ ebook-viewer backupfuse/Books/handbook.epub --B1) TRY TO VIEW THE EPUB InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser --B2) EPUB IS CORRUPTED $ ebook-viewer /Books/handbook.epub --C1) LET'S GO CHECK THE ORIGINAL InputFormatPlugin: EPUB Input running on /Books/handbook.epub Found HTML cover OEBPS/Text/cover.html--C2) ORIGINAL READS OK $ md5 /Books/handbook.epub 06d524ff85facfc2993e67ef6494d05f /Books/handbook.epub --C3) BUT ORIGINAL HAS SAME MD5 WE SAW IN STEP A! $ md5 backupfuse/Books/handbook.epub --D) CHECK MD5 OF BACKED FILE AGAIN b8d645db3af61ae2e8de03f496a1788d backupfuse/Books/handbook.epub --D2) CHECKSUM HAS CHANGED!! $ sudo -s # echo 3 /proc/sys/vm/drop_caches --E) DROP LINUX CACHES # exit $ md5 backupfuse/Books/handbook.epub --F1) CHECK MD5 AGAIN 06d524ff85facfc2993e67ef6494d05f backupfuse/Books/handbook.epub --F2) IT'S CORRECT AGAIN $ $ cp backupfuse/Books/handbook.epub /tmp/ --G1) SO NOW COPY IT OUT USING CP $ md5 /tmp/handbook.epub 06d524ff85facfc2993e67ef6494d05f /tmp/handbook.epub --G2) GOOD CHECKSUM $ ebook-viewer /tmp/handbook.epub InputFormatPlugin: EPUB Input running on /tmp/handbook.epub Found HTML cover OEBPS/Text/cover.html --G3) NOW IT READS OK $ ebook-viewer backupfuse/Books/handbook.epub --H1) TRY READING THE BACKUP COPY InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub Found HTML cover OEBPS/Text/cover.html --H2) BACKUP COPY READS OK PROBABLY FROM CACHE $ sudo -s # echo 3 /proc/sys/vm/drop_caches --I) DROPPING CACHE # exit $ ebook-viewer backupfuse/Books/handbook.epub --J1) TRY READING BACKUP COPY AGAIN InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser --J2) CORRUPTED AGAIN -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)
On 30/03/14 09:39 AM, Lars Wirzenius wrote: I've applied a patch from Valery to fix this, I hope. If you can try Obnam from git master, could you do so and tell me if obnam mount now works for you? You don't need to run a new backup. That seems to have fixed it; I've tried various ways to get backed data out of, or use it directly from, the repository and everything worked fine. Thanks for the hard work, gentlemen! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741968: closed by Lars Wirzenius l...@liw.fi (Bug#741968: fixed in obnam 1.7.2-1)
Hi Lars, I don't think the problem is fully fixed. I'm still getting weird errors depending how I read the backed up files from the fuse-mounted repository. As an example, I've attached an annoted terminal session showing how if I try to read an epub (with Calibre's ebook-viewer) from a fuse-mounted repo, I get corruption. But if I first copy it out using cp then it's OK. Bizarre stuf... Cheers Nemo backupfuse/Books is an obnam mount of the latest generation /Books is the folder that was backed up ebook-viewer is the Calibre ebook-viewer (v1.23), written in python $ md5 backupfuse/Books/handbook.epub --A) CHECKSUM OK 06d524ff85facfc2993e67ef6494d05f backupfuse/Books/handbook.epub $ ebook-viewer backupfuse/Books/handbook.epub --B1) TRY TO VIEW THE EPUB InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser --B2) EPUB IS CORRUPTED $ ebook-viewer /Books/handbook.epub --C1) LET'S GO CHECK THE ORIGINAL InputFormatPlugin: EPUB Input running on /Books/handbook.epub Found HTML cover OEBPS/Text/cover.html--C2) ORIGINAL READS OK $ md5 /Books/handbook.epub 06d524ff85facfc2993e67ef6494d05f /Books/handbook.epub --C3) BUT ORIGINAL HAS SAME MD5 WE SAW IN STEP A! $ md5 backupfuse/Books/handbook.epub --D) CHECK MD5 OF BACKED FILE AGAIN b8d645db3af61ae2e8de03f496a1788d backupfuse/Books/handbook.epub --D2) CHECKSUM HAS CHANGED!! $ sudo -s # echo 3 /proc/sys/vm/drop_caches --E) DROP LINUX CACHES # exit $ md5 backupfuse/Books/handbook.epub --F1) CHECK MD5 AGAIN 06d524ff85facfc2993e67ef6494d05f backupfuse/Books/handbook.epub --F2) IT'S CORRECT AGAIN $ $ cp backupfuse/Books/handbook.epub /tmp/ --G1) SO NOW COPY IT OUT USING CP $ md5 /tmp/handbook.epub 06d524ff85facfc2993e67ef6494d05f /tmp/handbook.epub --G2) GOOD CHECKSUM $ ebook-viewer /tmp/handbook.epub InputFormatPlugin: EPUB Input running on /tmp/handbook.epub Found HTML cover OEBPS/Text/cover.html --G3) NOW IT READS OK $ ebook-viewer backupfuse/Books/handbook.epub --H1) TRY READING THE BACKUP COPY InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub Found HTML cover OEBPS/Text/cover.html --H2) BACKUP COPY READS OK PROBABLY FROM CACHE $ sudo -s # echo 3 /proc/sys/vm/drop_caches --I) DROPPING CACHE # exit $ ebook-viewer backupfuse/Books/handbook.epub --J1) TRY READING BACKUP COPY AGAIN InputFormatPlugin: EPUB Input running on backupfuse/Books/handbook.epub EPUB appears to be invalid ZIP file, trying a more forgiving ZIP parser --J2) CORRUPTED AGAIN
