On 04/08/10 03:16, Rex Chan wrote:
>
>> Honestly, the truth is that free space monitoring isn't Bacula's job.
>> Bacula doesn't know what else it's sharing disk space with.
>>
>> That said, the subject has come up before; there has been discussion
>> of how best to handle the problem. Nothing ha
Am Wed, 07 Apr 2010 16:17:53 +1000 schrieb Rex Chan:
> Hi guys,
>
> once disk space becomes full, our bacula configuration starts writing
> out a whole bunch of 0 byte volumes to disk.
maybe you wan't to delete them with "delete volume=xyz" on bconsole.
>
> I can manually delete all the 0 byt
> Honestly, the truth is that free space monitoring isn't Bacula's job.
> Bacula doesn't know what else it's sharing disk space with.
>
> That said, the subject has come up before; there has been discussion
> of how best to handle the problem. Nothing has been implemented yet
> though. As best
On 04/07/10 02:17, Rex Chan wrote:
> Hi guys,
>
> once disk space becomes full, our bacula configuration starts writing
> out a whole bunch of 0 byte volumes to disk.
>
> I can manually delete all the 0 byte files, but does the catalog
> require cleanup as well?
>
> What changes can I make to
On 7.4.2010 9:17, Rex Chan wrote:
> Hi guys,
>
> once disk space becomes full, our bacula configuration starts writing
> out a whole bunch of 0 byte volumes to disk.
>
> I can manually delete all the 0 byte files, but does the catalog
> require cleanup as well?
>
> What changes can I make to
Hi guys,
once disk space becomes full, our bacula configuration starts writing
out a whole bunch of 0 byte volumes to disk.
I can manually delete all the 0 byte files, but does the catalog
require cleanup as well?
What changes can I make to our configuration to prevent this from
happening?
