bareos-dbcheck - No space left on device

[Rogerio Pereira]

Hi

When I delete some volumes I always run bareos-dbcheck -v -f after with option 15 (15 Run ALL checks).

Checking for orphaned Path entries. This may take some time! Query failed: SELECT DISTINCT Path.PathId, File.PathId, Path.Path FROM Path LEFT JOIN File USING (PathId) LEFT JOIN PathHierarchy ON (Path.Pathid = PathHierarchy.PPathId) WHERE File.PathId IS NULL AND PathHierarchy.PPathId IS NULL LIMIT 300000 : ERR=ERROR: could not write to file "base/pgsql_tmp/pgsql_tmp106408.0.fileset/o1209284of2097152.p0.0": No space left on device

But now it is giving the message above of disk full, even though there is 159 GB of disk available on the partition.

Monitoring the execution by another shell it is possible to see that option 15 really fills the disk at a certain point. Is there any way to optimize PostgreSQL so that it doesn't run out of disk space?

Debian 12.10
BareOS 24.0.2

Thanks in advance.

[Philippe]

Hi Rogerio,

try setting work_mem to 32MB or something in postgresql.

- Philippe

Am 20.03.25 um 18:48 schrieb Rogerio Pereira:
> <https://translate.google.com/about/?hl=pt-BR>
> <https://policies.google.com/?hl=pt-BR><https://support.google.com/
> translate/?hl=pt-BR><https://www.google.com/about?hl=pt-BR>
> Hi
>
> When I delete some volumes I always run *bareos-dbcheck -v -f* after
> with option 15 *(15 Run ALL checks)*.

>
> Checking for orphaned Path entries. This may take some time! Query
> failed: SELECT DISTINCT Path.PathId, File.PathId, Path.Path FROM Path
> LEFT JOIN File USING (PathId) LEFT JOIN PathHierarchy ON (Path.Pathid =
> PathHierarchy.PPathId) WHERE File.PathId IS NULL AND
> PathHierarchy.PPathId IS NULL LIMIT 300000 : ERR=ERROR: could not write
> to file "base/pgsql_tmp/pgsql_tmp106408.0.fileset/

> o1209284of2097152.p0.0":*No space left on device*

>
> But now it is giving the message above of disk full, even though there
> is 159 GB of disk available on the partition.
>
> Monitoring the execution by another shell it is possible to see that
> option 15 really fills the disk at a certain point. Is there any way to
> optimize PostgreSQL so that it doesn't run out of disk space?
>
> Debian 12.10
> BareOS 24.0.2
>
> Thanks in advance.

> <https://translate.google.com.br/history>
> <https://translate.google.com.br/saved>
>
> --
> You received this message because you are subscribed to the Google
> Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to bareos-users...@googlegroups.com <mailto:bareos-
> users+un...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/bareos-
> users/04d7e462-e18a-4003-a2cb-e3c19c6adb0en%40googlegroups.com <https://
> groups.google.com/d/msgid/bareos-users/04d7e462-e18a-4003-a2cb-
> e3c19c6adb0en%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Rogerio Pereira]

Thank you Phillippe!

Works like a charm!