Bug 286818 - sysutils/lsblk: running "lsblk -d" behaves abnormally when CD/DVD Drive 1 is attached as a "Client Device" on FreeBSD 14.3 Beta2
Summary: sysutils/lsblk: running "lsblk -d" behaves abnormally when CD/DVD Drive 1 is ...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords: vendor
Depends on:
Blocks:
 
Reported: 2025-05-15 10:12 UTC by Yanhui He
Modified: 2025-05-25 21:25 UTC (History)
2 users (show)

See Also:
linimon: maintainer-feedback? (vermaden)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yanhui He 2025-05-15 10:12:26 UTC 
We are testing FreeBSD 14.3 Beta2 guest OS on vSphere. It needs to configure a CD/DVD Driver1 as "Datastore ISO File" attached with FreeBSD 14.3 Beta2 ISO image like "FreeBSD-14.3-BETA1-amd64-dvd1.iso". After installation, it needs often to change the "Datastore ISO file" to "Client Device". There is difference between them.

If set the CD/DVD Drive1 as "Client Device", it hits error when using "lsblk -d".
# lsblk -d
DEVICE SIZE MODEL

Parse error: bad expression
    <stdin>:1


Parse error: bad expression
    <stdin>:1

[: -gt: unexpected operator
cd0      0B NECVMWar VMware SATA CD00

Parse error: bad token
    <stdin>:1

da0    1.0G VMware Virtual disk

Parse error: bad token
    <stdin>:1

da1     40G VMware Virtual disk

Parse error: bad token
    <stdin>:1

printf: : expected numeric value
-        0G TOTAL SYSTEM STORAGE

It's OK if don't use the option of "-d".
 # lsblk
DEVICE         MAJ:MIN SIZE TYPE                                    LABEL MOUNT
da0              0:83  1.0G GPT                                         - -
  <FREE>         -:-   1.0M -                                           - -
  da0p1          0:85  1.0G freebsd-ufs                   gpt/freebsd-ufs -
  <FREE>         -:-   1.0M -                                           - -
da1              0:84   40G GPT                                         - -
  da1p1          0:86  512K freebsd-boot                     gpt/gptboot0 -
  <FREE>         -:-   492K -                                           - -
  da1p2          0:87  2.0G freebsd-swap                 gpt/freebsd-swap -
  da1p3          0:88   38G freebsd-zfs                   gpt/freebsd-zfs <ZFS>
  <FREE>         -:-   1.0M -                                           - -


And it's OK when change the CD/DVD Driver1 from "Client Device" to "Datastore ISO File".
# lsblk -d
DEVICE SIZE MODEL
cd0    2.4G NECVMWar VMware SATA CD00
da0    1.0G VMware Virtual disk
da1     40G VMware Virtual disk
-       43G TOTAL SYSTEM STORAGE

Would you please take a look?

Thanks in advance!
Comment 1 Andriy Gapon freebsd_committer freebsd_triage 2025-05-15 21:48:01 UTC 
Maybe this should be a ports bug.
lsblk is not a part of FreeBSD base system.
Comment 2 Yanhui He 2025-05-16 03:51:26 UTC 
(In reply to Andriy Gapon from comment #1)
Thanks Andriy for your quick response!

So, will FreeBSD solve this problem?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2025-05-16 22:28:55 UTC 
(In reply to Yanhui He from comment #2)
Right now, we haven't even identified where the problem _lives_ yet.
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2025-05-16 22:32:00 UTC 
^Triage: I think I've found it.  I reclassified and did the maintainer notification.
Comment 5 Slawomir Wojciech Wojtczak 2025-05-19 10:34:06 UTC 
Can you check the latest version from here:

https://github.com/vermaden/lsblk/blob/master/lsblk
Comment 6 Yanhui He 2025-05-20 10:13:08 UTC 
(In reply to Slawomir Wojciech Wojtczak from comment #5)
Thanks Slawomir, I'll have a try!
Comment 7 Slawomir Wojciech Wojtczak 2025-05-25 21:25:44 UTC 
Did it helped?