Two or so weeks ago I upgraded a backuppc 3.3 system to 4.0. Things generally worked pretty well. Pool was 500GB or so, 31 hosts, all using rsync+ssh on the client side and rsync-bpc on the server side.
A larger setup with 40 hosts, 2.7TB pool, and backuppc-4.1.1 has had no problems. I haven't tinkered with it for a week: http://broadley.org/backuppc-pool.png But suddenly the pool is 100% full: $ df -h /backuppc/ Filesystem Size Used Avail Use% Mounted on /dev/md1 3.6T 3.4T 984M 100% /backuppc I poked around a bit without finding anything obvious. Any thoughts on this being worth tracking down? Or just I just upgrade to backuppc 4.1.1 (btw the main backuppc page still lists 4.0) and related rsync-bpc and friends? I'm running du -x on that partition, but I think it's got 55M files so it's going to take awhile. I'm hoping feeding that to xdu or similar will show something obvious. I did stop/start the backuppc daemon, it's not hung file handle from the main backuppc process. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ BackupPC-devel mailing list BackupPC-devel@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
