Description of problem: Btrfs Free + Used != Total. -------------------------------------------------------------------- Pool Type Devices Free Used Total Parent -------------------------------------------------------------------- 4vg lvm 1 6.48 GB 925.03 GB 931.51 GB vg lvm 1 83.64 GB 704.17 GB 787.82 GB 4pool thin 1 384.89 GB 540.11 GB 925.00 GB 4vg thintastic thin 1 671.51 GB 28.49 GB 700.00 GB vg fedoraroot btrfs 1 42.49 GB 50.00 GB 50.00 GB first btrfs 1 540.12 GB 1.00 TB 1024.00 GB -------------------------------------------------------------------- Version-Release number of selected component (if applicable): btrfs-progs-4.13.3-1.fc28.x86_64 system-storage-manager-0.5-0.fc27.noarch How reproducible: Always Steps to Reproduce: 1. create a btfs volume 2. ssm list 3. Actual results: Btrfs Free + Used != Total Expected results: Same as for lvm, and thin; free + used should equal total. Additional info: [chris@f27s ~]$ sudo btrfs fi us /mnt/first Overall: Device size: 1024.00GiB Device allocated: 488.06GiB Device unallocated: 535.94GiB Device missing: 0.00B Used: 484.91GiB Free (estimated): 537.10GiB (min: 269.13GiB) Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 512.00MiB (used: 0.00B) Data,single: Size:484.00GiB, Used:482.84GiB /dev/mapper/first 484.00GiB Metadata,DUP: Size:2.00GiB, Used:1.04GiB /dev/mapper/first 4.00GiB System,DUP: Size:32.00MiB, Used:80.00KiB /dev/mapper/first 64.00MiB Unallocated: /dev/mapper/first 535.94GiB [chris@f27s ~]$ sudo btrfs fi show /mnt/first Label: 'first' uuid: 0f43f49d-6e63-4b1b-bc8c-c54da409872d Total devices 1 FS bytes used 483.88GiB devid 2 size 1024.00GiB used 488.06GiB path /dev/mapper/first The most accurate variant of "used" is from the 'filesystem usage' subcommand, 484.91GiB. That's counting data used 482.84GiB, plus duplicate metadata used 1.04 + 1.04. The older 'filesystem show' command's first used, 'FS bytes used' is off by 1.04 because it counts metadata once, even though there are two copies. What you definitely don't want to use is the second used value from fi show, because that's the value of allocated block groups, some portion of which is empty. So we don't really care about that when talking about pool used value.
system-storage-manager-1.0-0.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a5e9bb0d59
system-storage-manager-1.0-0.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-82590e658c
system-storage-manager-1.0-0.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a5e9bb0d59
system-storage-manager-1.0-0.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-82590e658c
system-storage-manager-1.0-0.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
system-storage-manager-1.2-0.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-7783adc03e
system-storage-manager-1.2-0.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-7783adc03e
system-storage-manager-1.2-0.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.