[08:47] <nickmarus69> asl pls
[13:30] <ahasenack> stgraber: hi, did something change in lxd recently? I'm on impish, and `lxc config edit` is hanging. dmesg shows `Lockdown: rpc-worker: debugfs access is restricted; see man kernel_lockdown.7`
[13:31] <ahasenack> process tree shows vim in D state: https://pastebin.ubuntu.com/p/z4YtpBBjmF/
[13:39] <ahasenack> actually, this is what I'm seeing: https://gitlab.com/libvirt/libvirt/-/issues/213
[13:39] <ahasenack> every 3s I get 4 such lockdown messages in dmesg
[13:40] <ahasenack> so underlated to lxc config edit hanging I think
[13:43] <ahasenack> so, on to debugging why lxc config edit is hanging
[13:46] <ahasenack> it hangs when vim is used as editor, hmm
[13:46] <ahasenack> it's using vim from the snap
[13:46] <ahasenack> or no
[13:50] <ahasenack> with `EDITOR= lxc config edit f35-gluster` it works
[14:06] <ahasenack> aha, figured it out
[14:06] <ahasenack> I had a stale nfs mount on my system, in `/srv`, completely unrelated to snaps/lxd
[15:43] <stgraber> ahasenack: that'd explain the D state indeed :)
[15:44] <stgraber> ahasenack: when that happens, you'll often find some pointers in /proc/PID/stack for the process that's stuck
[15:54] <ahasenack> yeah, good tip
[15:54] <ahasenack> the final tip was in the lxd log
[15:55] <ahasenack> which I remembered to look at (in the right place) while filling out the lxd bug template