On Mon, Jul 27, 2015 at 06:26:48PM +0300, Vladmimir Stavrinov wrote:
Yes, this is old problem, You know. But in this case there are no any race
conditions. Only one client is working and only one obnam process are running
at once. And all things are local: client, repository and backed up
On Sat, Aug 01, 2015 at 04:20:37PM +0300, Lars Wirzenius wrote:
In this case it is possible to get opposite situation: orphan chunks
If You remove the reference first, then You may leave it's chunk not
deleted in case of some fault.
obnam fsck already knows how to delete unused chunks. I
On Sat, Aug 01, 2015 at 04:12:10PM +0300, Vladimir Stavrinov wrote:
On Sat, Aug 01, 2015 at 03:52:43PM +0300, Lars Wirzenius wrote:
The next version of Obnam will have fixes related to this, both to not
crash obnam forget if a chunk it wants to remove is missing, and to
In which version?
On Sat, Aug 01, 2015 at 03:52:43PM +0300, Lars Wirzenius wrote:
The next version of Obnam will have fixes related to this, both to not
crash obnam forget if a chunk it wants to remove is missing, and to
In which version? I see 1.13 in repository with some patches related to
this problem. Is it
Package: obnam
Version: 1.12-1
Severity: normal
Dear Maintainer,
Yes, this is old problem, You know. But in this case there are no any race
conditions. Only one client is working and only one obnam process are running
at once. And all things are local: client, repository and backed up
5 matches
Mail list logo
