Hi tech@,

Please let me know if this isn't the best list for this, and I'll send
similiar reports elsewhere in the future.

I had the most bizarre issue. I ran `fstat | grep 8080` and fstat hang.
This caused a bunch of other things to not work, but the system was
partly usable.

There was barely any disk I/O after this. System did not seem to just
heat up, spinning cycles. Was quite responsive.

What worked:

I could switch workspaces in i3, get to xterms. Could not launch new
xterms.
sync
Writing files with echo (verified after reboot).
I could run some commands like /usr/bin/true, /usr/bin/false.

What did not:
tmux seemed to freeze, effectively.
Reading files with cat.
vi
dmesg
fstat
ps
pkill

Any of these commands would hang, but were easily killable with ctrl+c.

I have no idea where to begin on this. I couldn't reproduce it after
rebooting. Never had any issues with fstat before. Maybe I need more
open file descriptors?

The last thing I see on fstat from the lists is that it was unlocked:
https://marc.info/?l=openbsd-tech&m=173607167913668&w=2

I don't see anything interesting in /var/log/messages or
/var/log/daemon. ntpd did move the clock a half second forward within
the hour before this. Couple of apmd logs.

Thank you!

-Henrich