2/2024 I did upgrade of debian to 12 with a new backuppc version 4. Now
after several month of further backups the backuppc reports a full disk.
There is 1TB disk, df shows twice as much occupied compared to backuppc
pool size. On V3 the pool was around 400GB, now the V4 pool reports also
cca 400GB, but actuall disk usage is over 800GB.
2024-09-25 00:00:01 Disk too full (usage 96%; inode 0%; thres 95%/%););
skipped 55 hosts
2024-09-25 00:00:01 Running 2 BackupPC_nightly jobs from 0..7 (out of
0..15)
2024-09-25 00:00:01 Running BackupPC_nightly -m -P 9 0 63 (pid=548913)
2024-09-25 00:00:01 Running BackupPC_nightly -P 9 64 127 (pid=548914)
2024-09-25 00:00:01 Next wakeup is 2024-09-25 02:00:00
2024-09-25 00:00:01 BackupPC_nightly now running BackupPC_refCountUpdate
-m -s -c -P 9 -r 0-63
2024-09-25 00:00:01 BackupPC_nightly now running BackupPC_refCountUpdate
-m -s -c -P 9 -r 64-127
2024-09-25 00:00:02 admin : __bpc_pidStart__ 548924
2024-09-25 00:00:02 admin1 : __bpc_pidStart__ 548925
2024-09-25 00:09:34 admin1 : __bpc_pidEnd__ 548925
2024-09-25 00:09:34 Finished admin1 (BackupPC_nightly -P 9 64 127)
2024-09-25 00:09:35 admin : __bpc_pidEnd__ 548924
2024-09-25 00:09:35 BackupPC_nightly now running BackupPC_sendEmail
2024-09-25 00:10:14 Finished admin (BackupPC_nightly -m -P 9 0 63)
2024-09-25 00:10:14 Pool nightly clean removed 0 files of size 0.00GB
2024-09-25 00:10:14 Pool is 0.00GB, 0 files (0 repeated, 0 max chain, 0
max links), 0 directories
2024-09-25 00:10:14 Cpool nightly clean removed 0 files of size 0.00GB
2024-09-25 00:10:14 Cpool is 0.00GB, 0 files (0 repeated, 0 max chain, 0
max links), 0 directories
2024-09-25 00:10:14 Pool4 nightly clean removed 0 files of size 0.00GB
2024-09-25 00:10:14 Pool4 is 0.00GB, 0 files (0 repeated, 0 max chain, 0
max links), 0 directories
2024-09-25 00:10:14 Cpool4 nightly clean removed 25965 files of size
1.40GB
2024-09-25 00:10:14 Cpool4 is 425.56GB, 4255998 files (0 repeated, 0 max
chain, 140045 max links), 16512 directories
The space is _definitely_ occupied by the backuppc pc and cpool dirs even
thou I am trying now to confirm with du (that is known to take ages). I
found here some possible bug in dirent problem
https://github.com/backuppc/backuppc/issues/418
but I am far from telling this is the reason.
To me it looks like old V3 cpool is not reallly removed or something but
backuppc thinks its empty? Or what does it mean that cpool is 0GB while
cpool4 is 425G? There are still vaiid V3 backups in the backup chain...
Any hints how to analyze the sizes what's in the pools?
Adam Pribyl
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
