Backing up a single desktop computer, BackupPC host ran out of inodes at 15 million inodes used. Reading old messages from this list I was surprised to learn BackupPC uses only one (or two?) inodes per backed up file, no matter how many hard links are used. I am thus at a loss to explain how come 15 million inodes is not enough for backing up this single desktop computer.

But to recover from this situation, I plan to reduce the number of full backups to keep, that is set $Conf{FullKeepCnt} to something lower.

Question: The host is already out of inodes on backuppc partition, can it still remove old backups now obsolete since lower FullKeepCnt? And old files are removed and inodes made available? I assume this happens during nightly cleanup runs, so I have to wait until next day to find out.

From what I learned from reading discussions, copying the pool to larger disk with more inodes is not feasible. Also it seems to me converting the current ext4 filesystem to some other filesystem that does not have a hard limit for inodes is iffy. So it is time to start planning a new backuppc host and use lower bytes-per-inode or use a filesystem with dynamic inodes.

--
Tapio Lehtonen
OSK Satatuuli

<<attachment: tapio_lehtonen.vcf>>

------------------------------------------------------------------------------
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
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to