Re: /tmp on mfs is blocked

> On 28 Jun 2024, at 19:39, Kirill A. Korinsky <kirill@korins.ky> wrote:
>
> and here we go:
>
> ~ $ ps auxl | grep D
> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND UID PPID CPU PRI NI WCHAN
> root 40744 0.0 1.3 1049488 218256 ?? D 2:59PM 0:13.90 /sbin/mount_nfs 0 1 0 -18 0 anonget
> catap 13530 0.0 2.0 1039528 330124 ?? DpU 3:04PM 0:23.48 ungoogled-chromi 1000 68942 0 -18 0 fltasgi
> catap 7160 0.0 0.7 821464 107612 ?? DpU 3:04PM 0:04.48 ungoogled-chromi 1000 68942 0 -5 0 biowait
> catap 26061 0.0 0.6 766536 92496 ?? DpU 3:05PM 0:00.77 ungoogled-chromi 1000 68942 0 -5 0 biowait
> catap 81520 0.0 0.0 1528 1176 p3 D+p 5:23PM 0:00.00 ls /tmp 1000 62543 0 10 0 inode
> catap 57257 0.0 0.0 108 384 C0 R+/1 5:24PM 0:00.00 grep D 1000 70049 29 53 0 -
> ~ $ doas sysctl ddb.trigger=1
> Stopped at db_enter+0x14: popq %rbp
> ddb{0}> show locks
> exclusive rwlock sysctllk r = 0 (0xffffffff82739928)
> exclusive kernel_lock &kernel_lock r = 0 (0xffffffff827c32d0)
> ddb{0}>
>
> Thus, doas reboot won't reboot machine from this state. After that
> machine is completly stuck. Reboot from ddb works. shutdown -r now also
> doesn't work.
>
> And easy way to achive this is run VM inside VMD which forces system to
> start using swap. As soon as it uses swap, around 500-700 mb is enough, 300
> doesn't, it goes into this state.
>
> Should I dulicate it inside bugs@?

Sure. It seems you stuck within uvmfault_anonget(), so include mpi@ to
recipients.