[Bug 1192996] New: Changed 'lsblk' Behavior Breaks OpenQA Tests and Customer Scripts
https://bugzilla.suse.com/show_bug.cgi?id=1192996 Bug ID: 1192996 Summary: Changed 'lsblk' Behavior Breaks OpenQA Tests and Customer Scripts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: shundhammer@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Command: lsblk Package: util-linux-systemd-2.37 Affected Code Streams: Tumbleweed, SLE-15-SP4, Leap 15.4 This bug was cloned / split off from bug #1192972. PROBLEM ======= The 'lsblk' command changed its behavior: It used to report only the first / primary mount point of a filesystem; now it reports ALL mount points. This is a problem because 'lsblk' used to be a simple check if a directory is on a separate filesystem: lsblk | grep '/home' But now this will also show a Btrfs subvolume with that path. This breaks a lot of OpenQA tests, and it will also break a lot of customer / end user scripts. WORKAROUNDS =========== The man page says that by default it does the same as if the '--fs' option was specified which alledgedly does the same as lsblk -o NAME,FSTYPE,FSVER,LABEL,UUID,FSAVAIL,FSUSE%,MOUNTPOINTS so a script using this could also use the singular form MOUNTPOINT to list only one, but that does not list the primary one, but the one that was last mounted (?): [sh @ balrog-tw-dev] ~ 22 % lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 30G 0 disk ������sda1 8:1 0 8M 0 part ������sda2 8:2 0 28G 0 part /mnt ��� / ������sda3 8:3 0 2G 0 part [SWAP] sdb 8:16 0 300M 0 disk sr0 11:0 1 1024M 0 rom [sh @ balrog-tw-dev] ~ 22 % lsblk -o NAME,MAJ:MIN,RM,SIZE,RO,TYPE,MOUNTPOINT NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 30G 0 disk ������sda1 8:1 0 8M 0 part ������sda2 8:2 0 28G 0 part /mnt ������sda3 8:3 0 2G 0 part [SWAP] sdb 8:16 0 300M 0 disk sr0 11:0 1 1024M 0 rom Notice that it shows /mnt, an additional mount of /dev/sda2, not / as I would expect. So this is not really helpful. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c1 --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- See also bug #1192972 and bug #1192971 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c2 --- Comment #2 from Stefan Hundhammer <shundhammer@suse.com> --- I assume this change comes from upstream, so reverting it may not be an option for us. I split off this bug from the other ones because I expect quite a number of bugs as a consequence. It is up to the QA team / the release managers and the maintainers of 'lsblk' to make a decision about this; it may end up as WONTFIX or similar. The QA team and customers relying on the old behavior may have to find a suitable workaround. But we, the YaST team, need a collecting point for all incoming bugs for this problem, and it needs to be clear what the root cause is. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c3 --- Comment #3 from Stefan Hundhammer <shundhammer@suse.com> --- For some possible workarounds and related tools, see https://github.com/shundhammer/qdirstat/blob/master/doc/Shadowed-by-Mount.md... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c4 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh@inai.de, | |jeriveramoya@suse.com, | |meissner@suse.com, | |shundhammer@suse.com Assignee|screening-team-bugs@suse.de |sbrabec@suse.com --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- [sh @ balrog-tw-dev] ~ 20 % osc maintainer -e util-linux-systemd Defined in package: Base:System/util-linux bugowner of util-linux-systemd : sbrabec@suse.com maintainer of util-linux-systemd : meissner@suse.com, sbrabec@suse.com, jengelh@inai.de -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c5 --- Comment #5 from Stefan Hundhammer <shundhammer@suse.com> --- *** Bug 1192972 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c6 --- Comment #6 from Stefan Hundhammer <shundhammer@suse.com> --- *** Bug 1192971 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Changed 'lsblk' Behavior |Changed 'lsblk' behavior |Breaks OpenQA Tests and |breaks OpenQA tests and |Customer Scripts |customer scripts -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c7 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #7 from Dominique Leuenberger <dimstar@opensuse.org> --- Related to https://progress.opensuse.org/issues/102795 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c8 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa@suse.com --- Comment #8 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- For the records, I have checked that this change should not affect yast2-users, which uses lsblk too[1]. [1] https://github.com/yast/yast-users/blob/0e361ce62ebaf4bac1e0bb6f44a19f9c8c93... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c9 --- Comment #9 from Stefan Hundhammer <shundhammer@suse.com> --- The upstream release notes mention this as a new feature: https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.37/v2.37-Relea... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 https://bugzilla.suse.com/show_bug.cgi?id=1192996#c10 --- Comment #10 from Stefan Hundhammer <shundhammer@suse.com> --- LSBLK(8) System Administration LSBLK(8) NAME lsblk - list block devices SYNOPSIS lsblk [options] [device...] DESCRIPTION ... ... ... This is the reason why lsblk provides MOUNTPOINT and MOUNTPOINTS (pl.) columns. The column MOUNTPOINT displays only one mount point (usually the last mounted instance of the filesystem) ----------------------------------------- This behavior is indeed documented, but still I consider this broken by design: If it tells me only ONE mount point, I want to know the primary one, i.e. the first one that was mounted, not the most recent one; that is completely useless information in all circumstances that I can think of. I know that in the kernel world, they think that all mount points are created equal, and that there is no such thing as a primary one; but in the real world, there certainly is, and that is always the one that was first mounted. Even more so in the context of Btrfs: It clearly has a main mount point, and then there are the subvolumes with their mount points. At least in that case I'd expect that one to be chosen for MOUNTPOINT. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1192996 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com