Package: obnam Version: 1.0-1 Severity: normal Hello,
obnam is not able to fsck-fix my backup repo. The error reported is: "ERROR: Larch B-tree is in read-only mode, no changes allowed" The fsck-errors were artificially created by aborting several times a backup. This may be the normal behaviour, but it does not seem clear to me why this occurs. The fsck command reports unused chunks, I rerun fsck in fix mode immediately after and get this error: $ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck chunk 17152530288956314516 not used by anyone chunk 17152530288956314520 not used by anyone (etc...) $ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck --fsck-fix ERROR: Larch B-tree is in read-only mode, no changes allowed regards, Damien -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (450, 'stable-updates'), (450, 'stable'), (300, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages obnam depends on: ii libc6 2.13-32 ii python 2.7.2-10 ii python-cliapp 0.29-1 ii python-larch 0.31-1 ii python-paramiko 1.7.7.1-2 ii python-tracing 0.6-2 ii python-ttystatus 0.18-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 obnam recommends no packages. obnam suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
