FYI, I'm still seeing this in current Linus' HEAD, not just on a single machine, but also when using multiple VMs on the same host. I can't actually test multiple physical hosts, so I wonder if anyone else can still reproduce it, and if yes wit which setup. On Mon, Oct 20, 2014 at 10:36:58AM -0700, Christoph Hellwig wrote: > Running 4.1 against a same host server backed off XFS I run into > a hang in generic/075: > > generic/075 18s ...[ 408.796877] nfs: server 127.0.0.1 not responding, still trying > [ 408.799131] nfs: server 127.0.0.1 not responding, still trying > [ 408.801357] nfs: server 127.0.0.1 not responding, still trying > [ 443.676971] nfs: server 127.0.0.1 not responding, timed out > [ 623.837009] nfs: server 127.0.0.1 not responding, timed out > [ 628.716855] nfs: server 127.0.0.1 not responding, timed out > [ 803.996883] nfs: server 127.0.0.1 not responding, timed out > [ 813.783542] nfs: server 127.0.0.1 not responding, timed out > [ 984.156873] nfs: server 127.0.0.1 not responding, timed out > [ 998.876901] nfs: server 127.0.0.1 not responding, timed out > ---end quoted text--- -- 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
