[Dirvish] Random --link-dest image being used

Jenny Hopkins hopkins.jenny at gmail.com
Sun Nov 26 10:27:17 UTC 2017


On 25 November 2017 at 13:42, Paul Slootman <paul at debian.org> wrote:
> On Sat 25 Nov 2017, Jenny Hopkins wrote:
>> On 25 November 2017 at 09:50, Jenny Hopkins <hopkins.jenny at gmail.com> wrote:
>> > Hello,
>> >
>> > Does anyone know where dirvish is told to find the --link-dest image
>> > at runtime?  I've got several vaults which all use the image from the
>> > previous day, but then one awkward one, which seems to be selected an
>> > image from 2 weeks previously.  All share the same master config, and
>> > I can't see anything in the default.conf for this vault that would
>> > affect it.
>> >
>> >
>>
>> To answer my own question - the default.hist file seemed to be two
>> weeks out of kilter.  I added some fake history to make it match the
>> other vaults, and all is well.
>
> Check to see whether the summary files from the missing dates do indeed
> show SUCCESS; only then is the current image added to the hist file.
>

That's it - I have "partial transfer" for a couple of weeks (I forgot
to put /run in my new exclude list).  Thanks for this - it's given me
advance notice that one of the other vaults is about to have the same
problem.

Jenny


More information about the Dirvish mailing list