diff options
| author | Karel Zak | 2017-06-09 11:33:18 +0200 |
|---|---|---|
| committer | Karel Zak | 2017-06-09 11:33:18 +0200 |
| commit | 1d9e35cc1e22f20184daff74ae131453c917d44c (patch) | |
| tree | 0e91a292d500c52927033281821c1d4fd325ac4f /Documentation | |
| parent | libblkid: (vfat) add more debug messages (diff) | |
| download | kernel-qcow2-util-linux-1d9e35cc1e22f20184daff74ae131453c917d44c.tar.gz kernel-qcow2-util-linux-1d9e35cc1e22f20184daff74ae131453c917d44c.tar.xz kernel-qcow2-util-linux-1d9e35cc1e22f20184daff74ae131453c917d44c.zip | |
lsblk: add option --tree
Now lsblk uses --list when --sort <column> is specified. This patch
allows to specify --tree to overwrite this default behavior add to
force tree-like output. In this case tree branches are sorted by the
<column>.
$ lsblk --sort SIZE
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda2 8:2 0 200M 0 part /boot
sda1 8:1 0 200M 0 part /boot/efi
sda6 8:6 0 7.8G 0 part [SWAP]
sda5 8:5 0 35.1G 0 part /home/misc
sda4 8:4 0 50G 0 part /
sdb1 8:17 0 74.5G 0 part /home/archive
sdb 8:16 0 74.5G 0 disk
sda3 8:3 0 130.3G 0 part /home
sda 8:0 0 223.6G 0 disk
$ lsblk --sort SIZE --tree
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 74.5G 0 disk
└─sdb1 8:17 0 74.5G 0 part /home/archive
sda 8:0 0 223.6G 0 disk
├─sda2 8:2 0 200M 0 part /boot
├─sda1 8:1 0 200M 0 part /boot/efi
├─sda6 8:6 0 7.8G 0 part [SWAP]
├─sda5 8:5 0 35.1G 0 part /home/misc
├─sda4 8:4 0 50G 0 part /
└─sda3 8:3 0 130.3G 0 part /home
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/TODO | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/Documentation/TODO b/Documentation/TODO index defca5a0d..1993422c8 100644 --- a/Documentation/TODO +++ b/Documentation/TODO @@ -26,9 +26,6 @@ lscpu lsblk ----- - - (!) add --tree to force tree output for operations like --sort where the - --list is enabled by default. - - currently it does not show mountpoint for all devices in btrfs RAID. It's because /proc/#/mountinfo contains reference to the one device only. Maybe we can add some btrfs specific code to provide a better output for FS based stacks. Not sure. |