On Wed, 08 Dec 2010 08:13:21 +0100, Delphine Patron writes: >You're right : the duplicity-full.20101006T231429Z.manifest.gpg >file is empty, as well as parts of the corresponding volumes files :-(
eek. >I guess that's the cause, indeed, but that should propabably make >duplicity overcome, since, in that case, that's not the latest full >backup that needs to be restored (hopefully). actually duplicity should not make such a mess in the first place... quick question: this looks like an external harddisk, right? are you certain that you never-ever unplugged that disk before the system buffers were written out? (also, is write caching enabled for that disk?) that's the simplest explanation i can think of that would explain 'some blank files that shouldn't be blank, without anybody noticing'. >Should I file a bug upstream, then ? to be honest, i'm not sure whether it makes sense to add further complexity to duplicity to deal with this very screwed up situation: an unreadable manifest might be recovered from the actual backup, sure, but as you said some of the actual volumes were also gone... as a workaround for now i'd move the damaged manifest and volumes to a different directory and then retry the restore. regards az -- + Alexander Zangerl + DSA 42BD645D + (RSA 5B586291) Our OS who art in CPU, UNIX be thy name. Thy programs run, thy syscalls done, in kernel as it is in user! -- BSD fortune file
signature.asc
Description: Digital Signature
