On 2019-03-03 07:07, Shawn Rappaport wrote:
I just purged a 100GB volume (my maximum volume size) and it shows as
purged but didn't free up disk space. Maybe I misunderstood what the
purge command is for since I expected the file size of daily-0 to drop
to 0GB but it still shows as 100GB:
|
When your storage is DISK. the volumen use "format" Bacula.
If the file (volumen) example volumen0001,FULL to 5GB. Recicle,
prune o purge... no free space.
du -sch volumen0001 (always 5GB). is a normal.
I do.if sda1 free total 100GB. then recommend i can create
only 18 v
On 3/2/19 1:35 PM, Shawn Rappaport wrote:
> I'm running Bacula 9.06 on CentOS 7.5 with MariaDB version 5.5.56-2. The
> Bacula-web interface shows the DB is 69.10GB in size. However, the MySQL
> files on my server are consuming 442GB of disk space, which is starting to
> fill up the disk on my Di
Am 02.03.2019 um 19:35 schrieb Shawn Rappaport:
> I'm running Bacula 9.06 on CentOS 7.5 with MariaDB version 5.5.56-2.
> The Bacula-web interface shows the DB is 69.10GB in size. However, the
> MySQL files on my server are consuming 442GB of disk space, which is
> starting to fill up the disk on m
I'm running Bacula 9.06 on CentOS 7.5 with MariaDB version 5.5.56-2. The
Bacula-web interface shows the DB is 69.10GB in size. However, the MySQL files
on my server are consuming 442GB of disk space, which is starting to fill up
the disk on my Director server. I see 374 mysql-bin files which are
I just purged a 100GB volume (my maximum volume size) and it shows as purged
but didn't free up disk space. Maybe I misunderstood what the purge command is
for since I expected the file size of daily-0 to drop to 0GB but it still shows
as 100GB:
| 1 | daily-0| Purged| 1 | 107
Hello,
From the code, it is *very* clear that the programmer (not me) knew that
the code was not portable. He provided what appears to be correct
#ifdefing to handle the case, including the appropriate modifications to
configure.in to detect whether or not accept4() exists. The programmer
handle
