hmm, odd situation
did:
.bvfs_clear_cache yes
bareos-dbcheck
check came back with:
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 USIN
G (PathId) LEFT JOIN PathHierarchy ON (Path.Pathid = PathHierarchy.PPathId)
WHERE File.PathId I
S NULL AND PathHierarchy.PPathId IS NULL LIMIT 300000 : ERR=ERROR: could
not resize shared mem
ory segment "/PostgreSQL.447978704" to 16777216 bytes: No space left on
device
CONTEXT: parallel worker
but my shm_size is already 64 MB, so 16 MB as needed above should be no
problem
Filesystem Size Used Available Use% Mounted on shm 64.0M 1.0M 63.0M 2%
/dev/shm
what can i do now?
using postgres 15.5 by the way
Markus Dubois schrieb am Freitag, 26. Januar 2024 um 19:25:17 UTC+1:
> i've using latest bareos v23
> i've switched from an always inceremental to an fairly easy 2 weekly full
> and incremental in between
>
> Now just for accident i discovered that the second full, which was
> sucessfull acording to the logs seems to be "empty".
>
> When i want to restore and select the second full as the source for
> restore, then then db gets browsed and instead delivering the folder tree,
> just comes back with an empty screen. No errors, nothing to select.
>
> What happen here?
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/9328477f-d46e-4be6-b76a-6f631a4c062fn%40googlegroups.com.
