Created attachment 1628207 [details] gnome-disk-utility 3.34.0 – presence of mention of LUKS volume format Enhancement request: using command lsblk, mentions of LUKS volumes versions to be informed as it is the case under gnome-disk-utility 3.34.0, UDisks 2.8.4 (built against 2.8.4); see gnome-disk-utility_3.34.0_LUKS_volume_format.png. Version-Release number of component: util-linux.x86_64 2.34-3.fc31 At best, information related to LUKS volumes can be as follow: $ lsblk -o name,type,fstype NAME TYPE FSTYPE [...] sdb disk └─sdb1 part crypto_LUKS └─luks-bd68a5e2-9679-430f-8280-7796fb0db0af crypt ext4
I have added FSVER column to the util-linux upstream, for example (last column): $ lsblk --fs -o+FSVER NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT FSVER loop0 btrfs d1e506dc-776e-4d18-855b-d335ed92afd8 sda ├─sda1 vfat EFI F2BC-BFEC 191.9M 4% /boot/efi FAT16 ├─sda2 ext4 BOOT c5490147-2a6c-4c8a-aa1b-33492034f927 42.6M 70% /boot 1.0 ├─sda3 ext4 empty b1230e08-280f-41fe-a0ac-f095fee44a92 1.0 ├─sda4 ext4 ROOT d834bc84-0089-4be1-9013-cd8bf35d5ffa 17G 60% / 1.0 └─sda5 linux_raid_member ws:0 3e6af563-e0cf-366c-af0c-b6589bc106c3 1.2 sdb btrfs 57615bf5-9192-42d9-97f7-bb39a391105b 72.5G 0% /mnt/C nvme0n1 ├─nvme0n1p1 swap SWAP e6f9f489-774e-43f9-8121-41789e6d5d7f 1 ├─nvme0n1p2 ext4 HOME 1774a3ed-9fe6-4537-a44f-46bc50fcb6bd 86.9G 51% /home 1.0 └─nvme0n1p3 Note that we cannot change output of the current FSTYPE due to regression (frankly, nowhere is type and version used together in low-level tools).
Good job even if output of the current FSTYPE could not be changed. Your added column would deserve to be part of the set covered by option --fs. LUKS version, which you referred as "filesystem version", looked fine to me as separated column. Strangely in your reported output, under column FSTYPE no mention of crypto_LUKS was present.
OK, I have added FSVER to --fs, example with LUKS (see sdb): # lsblk --fs NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat FAT16 EFI F2BC-BFEC 191.9M 4% /boot/efi ├─sda2 ext4 1.0 BOOT c5490147-2a6c-4c8a-aa1b-33492034f927 42.6M 70% /boot ├─sda3 ext4 1.0 empty b1230e08-280f-41fe-a0ac-f095fee44a92 ├─sda4 ext4 1.0 ROOT d834bc84-0089-4be1-9013-cd8bf35d5ffa 17G 60% / └─sda5 sdb crypto_LUKS 2 aa5e08ff-9b0a-4d25-8896-577544d8647c nvme0n1 ├─nvme0n1p1 swap 1 SWAP e6f9f489-774e-43f9-8121-41789e6d5d7f ├─nvme0n1p2 ext4 1.0 HOME 1774a3ed-9fe6-4537-a44f-46bc50fcb6bd 86.6G 51% /home └─nvme0n1p3
What a time-saving on command-line systems compared to the use of tool cryptsetup which till now we would have had to rely on in order to open each LUKS volume alone in order to check its LUKS version.