Front page

[BUG] No meaningful error when target run out of space

64efb67a32524df38afec55097b8caaf
FLYTRAP UNRAVEL SCOTLAND

From: Bazyli Brzóska <bazyli.brzoska@gmail.com>
Date: Tue, 21 Apr 2015 12:44:15 +0000

   Hi everybody,
   
   I just wasted some time debugging obnam, while it turns out the repository
   server just run out of space.
   For many commands (forget, backup), obnam just waits a bit and replies with:
   
   ERROR: R681AEX: Couldn't create lock ./lock: timeout
   
   When issuing: fix-lock - it works, but doesn't do anything really.
   
   It would be great if obnam would reply with an actual message that the
   target repository has run out of space, rather than replying with a timeout.
   
   Great work with obnam, by the way!
   
   Best,
   Bazyli
From: Bazyli Brzóska <bazyli.brzoska@gmail.com>
Date: Tue, 21 Apr 2015 12:44:15 +0000

   Hi everybody,
   
   I just wasted some time debugging obnam, while it turns out the repository
   server just run out of space.
   For many commands (forget, backup), obnam just waits a bit and replies with:
   
   ERROR: R681AEX: Couldn't create lock ./lock: timeout
   
   When issuing: fix-lock - it works, but doesn't do anything really.
   
   It would be great if obnam would reply with an actual message that the
   target repository has run out of space, rather than replying with a timeout.
   
   Great work with obnam, by the way!
   
   Best,
   Bazyli
From: Lars Wirzenius <liw@liw.fi>
Date: Sat, 29 Aug 2015 16:33:41 +0300

   On Tue, Apr 21, 2015 at 12:44:15PM +0000, Bazyli Brzóska wrote:
   > I just wasted some time debugging obnam, while it turns out the repository
   > server just run out of space.
   
   I confirm that Obnam seems to be giving unhelpful error messages about
   this. This seems to be at least partly because of the error codes it
   gets from the paramiko ssh implementation, but I'll see if I can make
   Obnam be better.