https://bugzilla.suse.com/show_bug.cgi?id=1217488 Petr Vorel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petr.vorel@suse.com, | |yosun@suse.com See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1217128 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217488 https://bugzilla.suse.com/show_bug.cgi?id=1217488#c2 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Neil Brown --- pynfs only waits for 10 seconds for the DELAY error to go away. I guess that isn't long enough. I think that failing the OP_SETCLIENTID just because there are already lots of clients is a bad choice. Certainly fail if there is a real shortage of memory, but not otherwise. Certainly look for idle clients to clean up, but don't fail. I'll post a patch upstream and see what they think. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1217488 https://bugzilla.suse.com/show_bug.cgi?id=1217488#c4 --- Comment #4 from Petr Vorel --- Based on upstream maintainer's comment about 1 GB not being enough [1] I tested with more RAM (QEMURAM=3600) and it solved the problem [2]. Let's see if Neil's v2 fix [3] is merged in upstream or not. [1] https://lore.kernel.org/linux-nfs/ZiZnbV+htcvGuGQl@tissot.1015granger.net/ [2] http://quasar.suse.cz/tests/3237 [3] https://lore.kernel.org/linux-nfs/171385732687.7600.2864936377155228614@nobl... -- You are receiving this mail because: You are on the CC list for the bug.