lvs --sort=devices does not sort properly

Bug #2005112 reported by andrew bezella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu 22.04.1 LTS
Release: 22.04

lvm2:
  Installed: 2.03.11-2.1ubuntu4
  Candidate: 2.03.11-2.1ubuntu4
  Version table:
 *** 2.03.11-2.1ubuntu4 500
        500 http://apt-mirror.us.archive.org/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

expected output:
  Path Devices
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta /dev/md3(0)
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data /dev/md4(24576)
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0 /dev/md5(0)
  /dev/archivevg/lvol0 /dev/md6(0)
  /dev/archivevg/lvol1 /dev/md6(943719)
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk0 /dev/md7(2048)
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0 /dev/md7(4096)
  /dev/vg0/lvol0 /dev/md9(0)
  /dev/vg0/lvol1 /dev/md11(0)
  /dev/vg0/lvol2 /dev/md11(471860)

actual output is incorrect and inconsistent, apparently varying w/list of fields to display:
% sudo lvs -o lv_path,devices --sort=devices
  Path Devices
  /dev/archivevg/lvol0 /dev/md6(0)
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data /dev/md4(24576)
  /dev/vg0/lvol1 /dev/md11(0)
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk0 /dev/md7(2048)
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0 /dev/md5(0)
  /dev/archivevg/lvol1 /dev/md6(943719)
  /dev/vg0/lvol2 /dev/md11(471860)
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta /dev/md3(0)
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0 /dev/md7(4096)
  /dev/vg0/lvol0 /dev/md9(0)
% sudo lvs -o lv_path,lv_size,devices --sort=devices
  Path LSize Devices
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_meta 128.00m /dev/md3(0)
  /dev/vg0/lvol1 1.80t /dev/md11(0)
  /dev/xenvg/ce09ae52-f319-401a-bfa6-96aec7e7b9ee.disk0_data 16.00g /dev/md4(24576)
  /dev/archivevg/lvol1 3.60t /dev/md6(943719)
  /dev/vg0/lvol0 7.13t /dev/md9(0)
  /dev/xenvg/577f8216-dc41-4a88-971c-f27e786325cf.disk0 1.80t /dev/md5(0)
  /dev/archivevg/lvol0 3.60t /dev/md6(0)
  /dev/xenvg/4b754245-b9fb-4c74-baf5-6c660b133e62.disk0 16.00g /dev/md7(4096)
  /dev/vg0/lvol2 128.00g /dev/md11(471860)
  /dev/xenvg/2e63d553-8a4c-42c2-8b63-04589582cb66.disk0 8.00g /dev/md7(2048)

if memory serves, this worked as expected in xenial/16.04.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lvm2 2.03.11-2.1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Feb 3 14:48:50 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.lvm.lvm.conf: [modified]
mtime.conffile..etc.lvm.lvm.conf: 2023-02-02T13:01:26.465746

Revision history for this message
andrew bezella (abezella) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.