This is primarily a cosmetic issue rather than a functional one, but I'd like to resolve it anyhow.
My BPC server has the backup pool stored on a zfs (raidz2) filesystem. After a couple years of usage, the pool fs was over 90% full, so I copied the backups elsewhere, destroyed the original raidz2 vdev, and created a new pool with a couple more disks in it last week. Functionally, all of this has worked flawlessly. However, the pool usage graphs in the BPC web interface are convinced that pool disk usage has been a consistent 2.79T ever since I restarted with the expanded pool. Actual usage is 50T, and continuing to increase daily as new backups are being taken. The "before pooling and compression" value on the graph is steadily rising and appears to be plausible, and "Pool file system was recently at xx%" is reporting the correct percentage used (currently 60%). It's only the graph of physical space used in the pool fs that is incorrect. The graph displayed physical space usage correctly prior to my teardown and rebuild of the raidz2 pool, and the new pool is mounted at the same location as the old one. Any suggestions for where I should look to get it graphing the correct amount of physical space used?
_______________________________________________ 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/
