On Wed, August 11, 2010 15:11, Paul Kraus wrote:
> On Wed, Aug 11, 2010 at 10:36 AM, David Dyer-Bennet wrote:
Am I looking for too much here? I *thought* I was doing something
that
should be simple and basic and frequently used nearly everywhere, and
hence certain to work.
On Wed, Aug 11, 2010 at 10:36 AM, David Dyer-Bennet wrote:
>
> On Tue, August 10, 2010 16:41, Dave Pacheco wrote:
>> David Dyer-Bennet wrote:
>
>>> If that turns out to be the problem, that'll be annoying to work around
>>> (I'm making snapshots every two hours and deleting them after a couple
>>>
On Tue, August 10, 2010 16:41, Dave Pacheco wrote:
> David Dyer-Bennet wrote:
>> If that turns out to be the problem, that'll be annoying to work around
>> (I'm making snapshots every two hours and deleting them after a couple
>> of
>> weeks). Locks between admin scripts rarely end well, in my e
On Tue, August 10, 2010 23:13, Ian Collins wrote:
> On 08/11/10 03:45 PM, David Dyer-Bennet wrote:
>> cannot receive incremental stream: most recent snapshot of
>> bup-wrack/fsfs/zp1/ddb does not
>> match incremental source
> That last error occurs if the snapshot exists, but has changed, it has
On 08/11/10 03:45 PM, David Dyer-Bennet wrote:
On 10-Aug-10 13:46, David Dyer-Bennet wrote:
It's possible that a snapshot was *deleted* on the sending pool
during the
send operation, however. Also that snapshots were created (however, a
newly created one would be after the one specified in t
On 10-Aug-10 13:46, David Dyer-Bennet wrote:
On Tue, August 10, 2010 13:23, Dave Pacheco wrote:
David Dyer-Bennet wrote:
My full backup still doesn't complete. However, instead of hanging the
entire disk subsystem as it did on 111b, it now issues error messages.
Errors at the end.
[...]
can
David Dyer-Bennet wrote:
On Tue, August 10, 2010 13:23, Dave Pacheco wrote:
David Dyer-Bennet wrote:
My full backup still doesn't complete. However, instead of hanging the
entire disk subsystem as it did on 111b, it now issues error messages.
Errors at the end.
[...]
cannot receive increment
On Tue, August 10, 2010 13:23, Dave Pacheco wrote:
> David Dyer-Bennet wrote:
>> My full backup still doesn't complete. However, instead of hanging the
>> entire disk subsystem as it did on 111b, it now issues error messages.
>> Errors at the end.
> [...]
>> cannot receive incremental stream: mos
David Dyer-Bennet wrote:
My full backup still doesn't complete. However, instead of hanging the
entire disk subsystem as it did on 111b, it now issues error messages.
Errors at the end.
[...]
cannot receive incremental stream: most recent snapshot of
bup-wrack/fsfs/zp1/ddb does not
match incr
Additional information. I started another run, and captured the exact
expanded commands. These SHOULD BE the exact commands used in the last
run except for the snapshot name (this script makes a recursive snapshot
just before it starts a backup). In any case they ARE the exact commands
used in t
My full backup still doesn't complete. However, instead of hanging the
entire disk subsystem as it did on 111b, it now issues error messages.
Errors at the end.
sending from @bup-daily-20100726-10CDT to
zp1/d...@bup-daily-20100727-10cdt
received 3.80GB stream in 136 seconds (28.6MB/sec)
11 matches
Mail list logo
