https://bugs.kde.org/show_bug.cgi?id=458006
Bug ID: 458006
Summary: System monitor does not recognize LUKS encrypted btrfs
disk
Product: plasma-systemmonitor
Version: 5.25.4
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: risto.paav...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
Created attachment 151384
--> https://bugs.kde.org/attachment.cgi?id=151384&action=edit
Screenshot from available disk sensors
SUMMARY
***
Mounted LUKS encrypted btrfs subvolume cannot be seen in System monitor (e.g.
Disk Usage 1.0 widget).
# fdisk -l
Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: HFS256G39TND-N21
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1ADD023E-D453-CF4C-B74D-F3CE22089BB8
Device Start End Sectors Size Type
/dev/sda1 2048 526335 524288 256M EFI System
/dev/sda2 526336 500118158 499591823 238.2G Linux filesystem
# cryptsetup open --allow-discards /dev/sda2 crypteddisk # Opening the crypted
volume with passwd
# cat /etc/fstab # mounting of subvolume
/dev/mapper/crypteddisk / btrfs
subvol=root,noatime,discard 0 0
sda1 and/or subvolume is missing from sensors under "Disks", see attached
image.
***
STEPS TO REPRODUCE
1. create luks encrypted disk with btrfs formating which has subvolumes
2. decrypt the disk with cryptsetup
3. mount a subvolume of btrfs partition somewhere (e.g. /)
4. try to monitor the mounted subvolume or the encrypted disk itself
OBSERVED RESULT
The disk or the subvolume cannot be seen in disk sensors.
EXPECTED RESULT
The disk or the subvolume usage, throughput, ... can be seen and measured in
disk sensors.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux 2.8
(available in About System)
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
