Re: 1.6.12: works; disk full handling

[On 29 Apr, @17:35, Boris wrote in "[hdup-user] 1.6.12: works; dis ..."]
> Finally had a chance to upgrade to 1.6.12: the new configuration is 
> great; ./configure && make worked flawlessly on Redhat Linux 8.0 and 
> Mac OS 10.2.4.

ok, good :)

> Then, I finally did it: filled up my backup disk.  I think hdup's 
> handling of this case could be better: what it did is just terminated 
> with no warnings or other messages (I'm not sure what the exit status 
> was - in the future I'll keep track of this clue).  The tar file is 
> there, but truncated, and the inclist file was created but empty -- a 
> situation that could confuse future runs since it looks like a backup 
> was done, but there is no trustworthy backed-up data.

that's not good. The abnormal termination is caused by the fact
that the backup pipe (something like: tar cvf - | gzip) is terminated.
This will yield a SIGPIPE -> only the lock file is removed -> exit.

This is what tar does on a full disk:
$ tar cvf trailer_final_1000_dl.mov.tar trailer_final_1000_dl.mov 
trailer_final_1000_dl.mov
tar: trailer_final_1000_dl.mov.tar: Wrote only 2048 of 10240 bytes
tar: Error is not recoverable: exiting now

> In case it matters, I was running a local, monthly backup with -V.

it's a tar thing - and difficult to detect. Hmmm. It's during the
writout of the archive that something fails -- badly. So subsequent
backups also go wrong. Because the disk is full. One thing would be
to test if the disk if full and then not make the backup and report
that. 

I'll take patches :))

grtz Miek