Description of problem: As root, running the following command "btrfs filesystem usage /" should show per device usage statistics but instead it shows the following: """ # btrfs --version btrfs-progs v6.2.2 # btrfs filesystem usage / WARNING: cannot read detailed chunk info, per-device usage will not be shown, run as root Overall: Device size: 80.00GiB Device allocated: 56.07GiB Device unallocated: 23.93GiB Device missing: 0.00B Device slack: 0.00B Used: 28.45GiB Free (estimated): 49.25GiB (min: 37.29GiB) Free (statfs, df): 49.25GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 101.23MiB (used: 0.00B) Multiple profiles: no Data,single: Size:52.01GiB, Used:26.69GiB (51.31%) Metadata,DUP: Size:2.00GiB, Used:902.39MiB (44.06%) System,DUP: Size:32.00MiB, Used:16.00KiB (0.05%) """ I tested an up-to-date stream version from "https://github.com/kdave/btrfs-progs/releases" and the issue is resolved so I'm requesting an update of the btrfs-progs package. """ # ./btrfs.static --version btrfs-progs v6.7.1 # ./btrfs.static filesystem usage / Overall: Device size: 80.00GiB Device allocated: 56.07GiB Device unallocated: 23.93GiB Device missing: 0.00B Device slack: 0.00B Used: 28.45GiB Free (estimated): 49.25GiB (min: 37.29GiB) Free (statfs, df): 49.25GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 101.23MiB (used: 0.00B) Multiple profiles: no Data,single: Size:52.01GiB, Used:26.69GiB (51.31%) /dev/mapper/Jupiter_VG-btrfs 52.01GiB Metadata,DUP: Size:2.00GiB, Used:902.39MiB (44.06%) /dev/mapper/Jupiter_VG-btrfs 4.00GiB System,DUP: Size:32.00MiB, Used:16.00KiB (0.05%) /dev/mapper/Jupiter_VG-btrfs 64.00MiB Unallocated: /dev/mapper/Jupiter_VG-btrfs 23.93GiB """ System: Mageia 9, x86_64. Version-Release number of selected component (if applicable): $ rpm -q btrfs-progs btrfs-progs-6.2.2-1.mga9 $ uname -a Linux jupiter 6.6.14-desktop-2.mga9 #1 SMP PREEMPT_DYNAMIC Tue Jan 30 15:48:16 UTC 2024 x86_64 GNU/Linux How reproducible: Always. Steps to Reproduce: 1. Create a btrfs filesystem, if one does not already exist. 2. Mount the btrfs filesystem, if one is not already mounted. 3. As root, run the command "btrfs filesystem usage /path/to/btrfs/" 4. See the warning and missing per device statistics.
CC: (none) => friAssignee: bugsquad => kernel
Depends on: (none) => 32813
Hi, Does btrfs-progs-6.6.3-1.mga9, which is in core/updates_testing solves your problem? Best regards,
CC: (none) => nicolas.salguero
Installed and tested without issues. The updated package fixes the issue. System: Mageia 9, x86_64, AMD Ryzen 5 5600G with Radeon Graphics. $ uname -a Linux jupiter 6.6.14-desktop-2.mga9 #1 SMP PREEMPT_DYNAMIC Tue Jan 30 15:48:16 UTC 2024 x86_64 GNU/Linux $ rpm -qa | grep btrfs lib64btrfs0-6.6.3-1.mga9 btrfs-progs-6.6.3-1.mga9 $ btrfs --version btrfs-progs v6.6.3 # /usr/sbin/btrfs filesystem usage / Overall: Device size: 80.00GiB Device allocated: 56.07GiB Device unallocated: 23.93GiB Device missing: 0.00B Device slack: 0.00B Used: 28.57GiB Free (estimated): 49.24GiB (min: 37.27GiB) Free (statfs, df): 49.23GiB Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 104.16MiB (used: 0.00B) Multiple profiles: no Data,single: Size:52.01GiB, Used:26.70GiB (51.34%) /dev/mapper/Jupiter_LVM-btrfs 52.01GiB Metadata,DUP: Size:2.00GiB, Used:954.44MiB (46.60%) /dev/mapper/Jupiter_LVM-btrfs 4.00GiB System,DUP: Size:32.00MiB, Used:16.00KiB (0.05%) /dev/mapper/Jupiter_LVM-btrfs 64.00MiB Unallocated: /dev/mapper/Jupiter_LVM-btrfs 23.93GiB
Suggested advisory: ======================== The updated packages fix compatibility with kernels 6.6. References: https://bugs.mageia.org/show_bug.cgi?id=32849 https://bugs.mageia.org/show_bug.cgi?id=32813 ======================== Updated packages in core/updates_testing: ======================== btrfs-progs-6.6.3-1.mga9 lib(64)btrfs0-6.6.3-1.mga9 lib(64)btrfs-devel-6.6.3-1.mga9 lib(64)btrfsutil1-6.6.3-1.mga9 from SRPM: btrfs-progs-6.6.3-1.mga9.src.rpm
Assignee: kernel => qa-bugsStatus: NEW => ASSIGNEDDepends on: 32813 => (none)Blocks: (none) => 32813
This update has been in use on my systems for 5 days (see comment 2). No issues noticed. I'm giving it an OK. Please undo if appropriate.
Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarmKeywords: (none) => advisory
Thomas Is good enough one test to validate this?
Certainly. PC LX is a long-standing member of QA whose tests are always thorough. Validating.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0062.html
Resolution: (none) => FIXEDStatus: ASSIGNED => RESOLVED