# btrfs filesystem df / Data: total=101.57GB, used=75.75GB System, DUP: total=8.00MB, used=24.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=3.00GB, used=2.09GB Metadata: total=8.00MB, used=0.00 # btrfs filesystem df / Data: total=100.57GB, used=77.00GB System, DUP: total=8.00MB, used=24.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=3.50GB, used=2.35GB Metadata: total=8.00MB, used=0.00
I've had btrfs filesystem balance running on a partition of my 120G Intel SSD for almost 7 hours. The above two runs of fi df were before the balance and after it had run for almost 7 hours. The system is in operation during this process, I've used it for email, web browsing, and I downloaded a movie from Youtube. Also during the process the usual cron jobs have been running including the one that makes a snapshot of /home every 15 minutes. Is it considered to be a bad idea to make snapshots while doing a balance? Should a balance take so long anyway? It's been mostly CPU bound an on E4600 CPU, that's a bit dated but it's still dual-core 64bit and whatever the btrfs utility has done to use 327 minutes of CPU time is probably wrong. Any suggestions on other information I should provide? I'm using 3.10.7 in Debian package linux-image-3.10-2-amd64 version 3.10.7-1 and version 0.19+20130705-1 of the btrfs-tools in Debian/Unstable. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
