[Bug 257240] glabel(8): glabel status can be difficult to kill when presented with a failing drive

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 18 Jul 2021 05:41:42 UTC 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257240

            Bug ID: 257240
           Summary: glabel(8): glabel status can be difficult to kill when
                    presented with a failing drive
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: grahamperrin@gmail.com

Created attachment 226523
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226523&action=edit
Screenshot: lsblk (not responding to Control-C) running glabel status, `tail -f
-n 0 /var/log/messages` in the background

I used sysutils/lsblk, sysutils/gdisk and newfs(8) to prepare a USB flash drive
to demonstrate use of sysutils/stressdisk

Following a failed test with StressDisk, run as root (comparable to
<https://github.com/ncw/stressdisk/issues/14>) I rebooted the computer then ran
lsblk (as root) to determine the /dev/da⋯ number of the affected device. 

lsblk ran endlessly and did not respond to Control-C, so I used sysutils/htop
to terminate two lsblk processes (two of three in a tree). 

----

root@mowa219-gjp4-8570p:~ # lsblk 
^C    
load: 0.28  cmd: glabel 3767 [g_waitfor_event] 173.22r 0.00u 0.00s 0% 2548k
mi_switch+0xc1 sleepq_timedwait+0x2f _sleep+0x1ab g_waitfor_event+0xc1
sysctl_kern_geom_confany+0xc1 sysctl_root_handler_locked+0x91 sysctl_root+0x24c
userland_sysctl+0x173 sys___sysctl+0x5c amd64_syscall+0x10c
fast_syscall_common+0xf8 
load: 0.67  cmd: glabel 3767 [g_waitfor_event] 423.27r 0.00u 0.00s 0% 2548k
mi_switch+0xc1 sleepq_timedwait+0x2f _sleep+0x1ab g_waitfor_event+0xc1
sysctl_kern_geom_confany+0xc1 sysctl_root_handler_locked+0x91 sysctl_root+0x24c
userland_sysctl+0x173 sys___sysctl+0x5c amd64_syscall+0x10c
fast_syscall_common+0xf8 
Terminated
root@mowa219-gjp4-8570p:~ # 


----

The third process from the tree: 

glabel status

– continues, and does not stop in response to SIGTERM (15) and SIGKILL (9)
issued by htop …

-- 
You are receiving this mail because:
You are the assignee for the bug.