http://bugzilla.opensuse.org/show_bug.cgi?id=1186825
http://bugzilla.opensuse.org/show_bug.cgi?id=1186825#c4
--- Comment #4 from Ralf K�lmel ---
Created attachment 850175
--> http://bugzilla.opensuse.org/attachment.cgi?id=850175&action=edit
NFSv4.1 client with kernel kernel 5.3.18-lp152.78-default
The problem (CPU Stucks) is replicable with a NFSv4.1 mountpoint on the client
side from a shutdown NFS server.
I've tested with the recent kernel 5.3.18-lp152.78-default on the client side
(s. attachment for detailed stack traces).
The stack traces aren't completely the same in comparison to the "real world"
situations, but the occuring CPU stucks are problematic for the whole client
system (e.g. for libvirtd which is blocking even if it doesn't need this NFS
mountpoint, but this is another problem).
But for now i couldn't replicate the situation, that the clients couldn't
reconnect after startup of the NFS server, as i had in the log
https://bugzilla.opensuse.org/attachment.cgi?id=850148
--
You are receiving this mail because:
You are the assignee for the bug.