On Mon, Feb 22, 2010 at 7:15 PM, Russ Cox wrote:
> I am not sure, but I have seen things like this since
> I tried to expand the venti protocol to >16-bit blocks.
> I have since decided that was a mistake, too intrusive
> a change, but I have not yet gotten around to rolling
> back to the old vers
I am not sure, but I have seen things like this since
I tried to expand the venti protocol to >16-bit blocks.
I have since decided that was a mistake, too intrusive
a change, but I have not yet gotten around to rolling
back to the old versions of the files.
That might make the bug go away, whateve
> I've been running a vac-based backup on a few unix systems for a while
> now. A bit over a week ago, one of them started failing with this
> error:
>
> vac: vtcachelocal: asked for block #6289076; only 6288808
> blocks
>
[...]
>
> If a new cache block must be allocated... b
I've been running a vac-based backup on a few unix systems for a while
now.
A bit over a week ago, one of them started failing with this error:
vac: vtcachelocal: asked for block #6289076; only 6288808 blocks
Adding -v to the vac invocation, it seems to be failing in the same
place e
