https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289627
Bug ID: 289627
Summary: Sesutil hangs after repeated usage
Product: Base System
Version: 14.3-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: [email protected]
Reporter: [email protected]
Created attachment 263825
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=263825&action=edit
dmesg.boot file from affected box
The following sequence causes sesutil to hang. The final command does not take
effect (that is, the fault lights remain in the state they were just prior to
the last command.
riviera:/root# for i in 16 4 11 17 15 23 5 10 22 3 9; do sesutil fault da$i on;
done
riviera:/root# sesutil fault all off
riviera:/root# for i in 6 0 8 14 20 1 7 13 12 2 19; do sesutil fault da$i on;
done
riviera:/root# sesutil fault all off
(terminal hung at this point)
Any further attempts to run sesutil in other ttys/ptys once this has happened
only results in hanging those terminals as well.
The only recovery method is a reboot. The sesutil process is hung in D+ state
and connect be killed, and does not respond to Ctrl-C.
USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 33940 0.0 0.0 13980 2580 1 D+ 08:54 0:00.00 sesutil
fault all off
Repeated invocations of `sesutil fault all on` and `sesutil fault all off` will
also cause the hang.
The reason for doing it in a for loop is I was trying to light the fault lights
on each vdev in my zpool so I could verify the physical location of the
corresponding drives.
There are no obvious related messages in /var/log/messages or
/var/log/daemon.log. The last messages before rebooting were 4 hours old at the
time of the reboot.
riviera:/root# uname -m -r -s -v -U
FreeBSD 14.3-RELEASE-p2 FreeBSD 14.3-RELEASE-p2 GENERIC amd64 1403000
--
You are receiving this mail because:
You are the assignee for the bug.
