Still can't find what is using V3 pool should i leave it as is ? or better to find solution and delete unused data?
On 11 June 2017 at 13:00, Craig Barratt via BackupPC-users <[email protected]> wrote: > Alex, > > First you should check to see what's left in the v3 cpool, eg: > > cd /data/BackupPC/cpool > ls -lR [0-9a-f] > du -s ?/?/? > > Next you could pick a file and find its inode number and number of links: > > ls -li 0/1/2/1234567890abcdef > > Are there any files with >1 links? If so, you could try to find where else > that file is hardlinked to, eg: > > cd /data/BackupPC/pc > find . -type f -inum inodeNumber -print > > Craig > > On Tue, Jun 6, 2017 at 6:20 PM, Alexey Safonov <[email protected]> > wrote: >> >> My $Conf{PoolSizeNightlyUpdatePeriod} = 16; is 4 >> >> and i already wait more than 2 weeks. >> >> i was trying to convert pool manually. process finished without any error. >> and i try nightly maintenance several times manually >> >> Alex >> >> On 6 June 2017 at 17:02, Alexander Moisseev via BackupPC-users >> <[email protected]> wrote: >>> >>> On 6/6/2017 4:24 AM, Alexey Safonov wrote: >>>> >>>> Alexander, Craig >>>> >>>> any ideas what can i check and how to find this V3 pool? >>>> >>> I don't know how exactly do this. I guess you need to find files with >>> hardlink count > 1 in the pool and cpool directories. >>> >>> Probably it's not necessary, you just need to wait. >>> >>> Make sure "$Conf{PoolV3Enabled} = 1;" until the last file deleted from v3 >>> pool. >>> By default "$Conf{PoolSizeNightlyUpdatePeriod} = 16;". This means you >>> need to wait 16 days while v3 pool will be emptied. >>> >>> See details in BackupPC_migrateV3toV4 section of >>> https://backuppc.github.io/backuppc/BackupPC.html#Other-Command-Line-Utilities >>> BTW, This section says "You could do this manually". Craig, how'd you >>> suggest to find v3 files in pool and cpool? >>> >>> Since your pool is not big you can set $Conf{PoolSizeNightlyUpdatePeriod} >>> = 1; >>> >>> Also it's not necessary to wait next BackupPC_nightly run. You can start >>> it at any time. >>> # su -m backuppc -c 'BackupPC_serverMesg BackupPC_nightly run' >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> BackupPC-users mailing list >>> [email protected] >>> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >>> Wiki: http://backuppc.wiki.sourceforge.net >>> Project: http://backuppc.sourceforge.net/ >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> BackupPC-users mailing list >> [email protected] >> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki: http://backuppc.wiki.sourceforge.net >> Project: http://backuppc.sourceforge.net/ >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > BackupPC-users mailing list > [email protected] > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
