> On Apr 26, 2017, at 6:46 PM, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > > On Wed, 2017-04-26 at 15:52 -0700, Chuck Lever wrote: >>> On Apr 26, 2017, at 3:47 PM, scar <scar@xxxxxxxxxx> wrote: >>> >>> Chuck Lever wrote on 04/26/2017 01:32 PM: >>>> If it's every 5 minutes, that's probably the RPC idle timeout >>>> that is closing the connection. >>>> >>>> So this should be entirely harmless. >>> >>> Yes so far it seems harmless, but it is annoying and fills up the >>> log with spam, plus it's not something I see when using NFS/TCP. >> >> That's correct, NFS/TCP does not have the "connected / closed" >> messages, but the idle timeout behavior is the exactly the same. >> >> I tried to remove those messages a few years ago and was told >> to go pound sand. >> > > > By me? No, I filed a bug on bugzilla.kernel.org and I think it was Alan Cox (!) who told me to leave these alone. > I’d be happy to take a patch to remove those messages. I find it > absolutely ridiculous to be logging fully expected behaviour like this. > It should at best be a dprintk() and I'd prefer to replace it with > tracepoints like we do for the socket code. I can send a patch for 4.13 that converts these to dprintks for now. Tracepoints are definitely in plan... -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
