Re: [BackupPC-users] Problems disk usage after migrated/reinstalled from 3.3 to 4.4

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Would this
https://sourceforge.net/p/backuppc/mailman/message/59193166/

help to answer the question?

Short: Old V3 backups are still in the cpool in "single digit" 
subdirectories. V4 always creates a "two digit" subdirectories. I already 
deleted the V3 subdirs and reclaimed the space.

Adam Pribyl

On Sun, 16 Nov 2025, klxout wrote:

> Hi,
>
> I'll  try to answer your questions:
>
> First let's make sure that there *is* a problem.  In some commands
> below you may need to change the logged-in user ID to one which can
> read the necessary files (often, for example, to user 'backuppc').  --->
> Sorry I don't know how to check this, user is running backuppc is backuppc
> and seems ok, any other check?
>
> 1.
>
> Did you run BackupPC_nightly by hand?
>
> How many times has it been run on the nightly backup schedule since
> your most recent install of BackupPC version 4?
> I have forced executed multiples times changing time, and now after 7 day
> seems that some files were purged but not all  because I have a
> retention full 2 days and incremental 1 day
>
> config
> [image: imatge.png]
>
>
> ***
> 2025-11-16 18:00:00 Running 2 BackupPC_nightly jobs from 0..15 (out of
> 0..15)
> 2025-11-16 18:00:00 Running BackupPC_nightly -m -P 2 0 127 (pid=67245)
> 2025-11-16 18:00:00 Running BackupPC_nightly -P 2 128 255 (pid=67246)
> 2025-11-16 18:00:00 Next wakeup is 2025-11-17 04:00:00
> 2025-11-16 18:00:01 BackupPC_nightly now running BackupPC_refCountUpdate -m
> -s -c -P 2 -r 128-255
> 2025-11-16 18:00:01 BackupPC_nightly now running BackupPC_refCountUpdate -m
> -s -c -P 2 -r 0-127
> 2025-11-16 18:00:01  admin : __bpc_pidStart__ 67259
> 2025-11-16 18:00:01  admin1 : __bpc_pidStart__ 67258
> 2025-11-16 18:00:23  admin1 : __bpc_pidEnd__ 67258
> 2025-11-16 18:00:23 Finished  admin1  (BackupPC_nightly -P 2 128 255)
> 2025-11-16 18:00:47  admin : __bpc_pidEnd__ 67259
> 2025-11-16 18:00:47 BackupPC_nightly now running BackupPC_sendEmail
> 2025-11-16 18:00:47 Finished  admin  (BackupPC_nightly -m -P 2 0 127)
> 2025-11-16 18:00:47 Pool nightly clean removed 0 files of size 0.00GB
> 2025-11-16 18:00:47 Pool is 0.00GB, 0 files (0 repeated, 0 max chain, 0 max
> links), 0 directories
> 2025-11-16 18:00:47 Cpool nightly clean removed 0 files of size 0.00GB
> 2025-11-16 18:00:47 Cpool is 0.00GB, 0 files (0 repeated, 0 max chain, 0
> max links), 0 directories
> 2025-11-16 18:00:47 Pool4 nightly clean removed 0 files of size 0.00GB
> 2025-11-16 18:00:47 Pool4 is 0.00GB, 0 files (0 repeated, 0 max chain, 0
> max links), 0 directories
> 2025-11-16 18:00:47 Cpool4 nightly clean removed 2710 files of size 309.23GB
> 2025-11-16 18:00:47 Cpool4 is 1413.54GB, 95357 files (0 repeated, 0 max
> chain, 1496 max links), 16467 directories
> 2025-11-16 18:00:47 Running BackupPC_rrdUpdate (pid=67276)
> 2025-11-16 18:00:47  admin-1 : RRD updated: date 1763337600; cpoolKb
> 0.000000; total 1351783435.940430; poolKb 0.000000; pool4Kb 0.000000;
> cpool4Kb 1447466560.000000
> 2025-11-16 18:00:47 Finished  admin-1  (BackupPC_rrdUpdate)
> ***
>
> It seems that no tall backups are purge, I suspect...
>
>
> 2.-
>
> find /local/var/lib/backuppc/cpool/ -type f -mtime +9 | head
> root@opencde-backups-1:/local/var/lib/backuppc#  find
> /local/var/lib/backuppc/cpool/ -type f -mtime +7 | head
> /local/var/lib/backuppc/cpool/b2/b2/b3b31903e2aca45f31a482993eaed662
> /local/var/lib/backuppc/cpool/b2/b2/b3b3b58e806d43a38e983909305aa39c
> /local/var/lib/backuppc/cpool/b2/b2/b3b3a0ba5c8b13f51c9a87bfc7c56b3e
> /local/var/lib/backuppc/cpool/b2/b2/b3b3f43686dd71f467b9c14d04f7d993
> /local/var/lib/backuppc/cpool/b2/b2/b3b25f7087776b1a4b1e1698e89c337d
> /local/var/lib/backuppc/cpool/b2/b2/b3b3c6f036d4833e86db3803d88e8023
> /local/var/lib/backuppc/cpool/b2/ba/b2bb85d79e6345166ff714eec5543699
> /local/var/lib/backuppc/cpool/b2/ba/b3ba25b2c0e22981764533d2a25c75a6
> /local/var/lib/backuppc/cpool/b2/ba/b3ba52777bf7a5c8853cdb78ca4def07
> /local/var/lib/backuppc/cpool/b2/ba/b3ba794ee40fc2f1549bd96ba64f1757
>
>
> 3.-
>
>  grep 'my $minMtime'  /usr/share/backuppc/bin/BackupPC_refCountUpdate
>            my $minMtime = time() - 7 * 24 * 3600;
>
>
>
> Missatge de G.W. Haywood <ba...@ju...> del dia dt., 11 de
> nov. 2025 a les 14:50:
>
>> Hi there,
>>
>> On Tue, 11 Nov 2025, klxout wrote:
>>
>>> I have similar issues described in
>>> https://github.com/backuppc/backuppc/issues/418
>>>
>>> I have the same problem recently upgraded debian with 3.3 backuppc to
>>> debian 13 with latest backuppc 4.4 from debian repositories and space is
>>> increasing.... seems files are never purged
>>>
>>> Now I have reinstalled backuppc with a fresh install using apt-get remove
>>> --purge backuppc* and I'm evaluating the results
>>>
>>> in the logs appears always 0 space recovered from v4 pool (only v4 is
>>> enabled as it was a default install)
>>>
>>> 2025-11-10 18:00:00 Running 2 BackupPC_nightly jobs from 0..15 (out of
>> 0..15)
>>> 2025-11-10 18:00:00 Running BackupPC_nightly -m -P 11 0 127 (pid=50769)
>>> 2025-11-10 18:00:00 Running BackupPC_nightly -P 11 128 255 (pid=50770)
>>> 2025-11-10 18:00:00 Next wakeup is 2025-11-11 04:00:00
>>> 2025-11-10 18:00:01 BackupPC_nightly now running BackupPC_refCountUpdate
>> -m -s -c -P 11 -r 128-255
>>> 2025-11-10 18:00:01 BackupPC_nightly now running BackupPC_refCountUpdate
>> -m -s -c -P 11 -r 0-127
>>> 2025-11-10 18:00:01  admin : __bpc_pidStart__ 50783
>>> 2025-11-10 18:00:01  admin1 : __bpc_pidStart__ 50782
>>> 2025-11-10 18:00:16  admin : __bpc_pidEnd__ 50783
>>> 2025-11-10 18:00:16 BackupPC_nightly now running BackupPC_sendEmail
>>> 2025-11-10 18:00:16 Finished  admin  (BackupPC_nightly -m -P 11 0 127)
>>> 2025-11-10 18:00:37  admin1 : __bpc_pidEnd__ 50782
>>> 2025-11-10 18:00:37 Finished  admin1  (BackupPC_nightly -P 11 128
>>> 255)*2025-11-10 18:00:37 Pool nightly clean removed 0 files of size
>> 0.00GB
>>> 2025-11-10 18:00:37 Pool is 0.00GB, 0 files (0 repeated, 0 max chain, 0
>> max links), 0 directories
>>> 2025-11-10 18:00:37 Cpool nightly clean removed 0 files of size 0.00GB
>>> 2025-11-10 18:00:37 Cpool is 0.00GB, 0 files (0 repeated, 0 max chain, 0
>> max links), 0 directories
>>> 2025-11-10 18:00:37 Pool4 nightly clean removed 0 files of size 0.00GB
>>> 2025-11-10 18:00:37 Pool4 is 0.00GB, 0 files (0 repeated, 0 max chain, 0
>> max links), 0 directories
>>> 2025-11-10 18:00:37 Cpool4 nightly clean removed 0 files of size 0.00GB*
>>> 2025-11-10 18:00:37 Cpool4 is 782.54GB, 92649 files (0 repeated, 0 max
>> chain, 1632 max links), 16452 directories
>>> 2025-11-10 18:00:37 Running BackupPC_rrdUpdate (pid=50797)
>>> 2025-11-10 18:00:38  admin-1 : skipping repeated RRD update for the same
>> day: last update time is 1762819200
>>> 2025-11-10 18:00:38 Finished  admin-1  (BackupPC_rrdUpdate)
>>>
>>> Any suggestion to solve this problems?
>>
>> First let's make sure that there *is* a problem.  In some commands
>> below you may need to change the logged-in user ID to one which can
>> read the necessary files (often, for example, to user 'backuppc').
>>
>> 1.
>>
>> Did you run BackupPC_nightly by hand?
>>
>> How many times has it been run on the nightly backup schedule since
>> your most recent install of BackupPC version 4?
>>
>> 2.
>>
>> In the Github issue (#418) on which you commented, did you read
>> Craig's post of Feb 25, 2021 at
>>
>> https://github.com/backuppc/backuppc/issues/418#issuecomment-785825325
>>
>> in which he talks about the mtimes of pool files?  Did you try any of
>> Craig's suggestions there?
>>
>> Does your filesystem properly set the 'x' bit in file metadata?
>>
>> Do you know roughly how old (looking at mtimes of the files) is the
>> oldest file in your 'cpool'?
>>
>> If not, what's the output of
>>
>>    find /POOLDIR/ -type f -mtime +9 | head
>>
>> where /POOLDIR/ is the full path to your cpool ?  (For example on a
>> system *here*, that would be
>>
>>    find /var/lib/BackupPC/cpool/ -type f -mtime +9 | head
>>
>> because the cpool directory *here* is in /var/lib/BackupPC/ - but note
>> that your cpool directory might not be in the same place as mine).
>>
>> 3.
>>
>> What's the output of
>>
>>    grep 'my $minMtime' /path/to/BackupPC_refCountUpdate
>>
>> where /path/to/ is the path to your BackupPC Perl scripts.
>>
>> --
>>
>> 73,
>> Ged.
>>
>>
>> _______________________________________________
>> BackupPC-users mailing list
>> Bac...@li...
>> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
>> Wiki:    https://github.com/backuppc/backuppc/wiki
>> Project: https://backuppc.github.io/backuppc/
>>
>