Apr 29 14:45:59 mwg kernel: nfs: server inx not responding, still trying
Apr 29 14:45:59 mwg kernel: nfs: server inx OK
Apr 29 14:46:19 mwg kernel: nfs: server inx not responding, still trying
Apr 29 14:46:20 mwg kernel: nfs: task 768 can't get a request slot
Apr 29 14:46:20 mwg kernel: nfs: task 769 can't get a request slot
Apr 29 14:46:31 mwg kernel: nfs: server inx OK
Apr 29 14:46:55 mwg last message repeated 2 times
Apr 29 14:46:55 mwg kernel: nfs: task 783 can't get a request slot
Apr 29 14:46:55 mwg kernel: nfs: task 784 can't get a request slot
Apr 29 15:04:30 support kernel: nfs: task 9144 can't get a request slot
Apr 29 15:04:39 support kernel: nfs: server inx not responding, still trying
Apr 29 15:04:41 support kernel: nfs: task 9145 can't get a request slot
Apr 29 15:04:41 support kernel: nfs: task 9146 can't get a request slot
Apr 29 15:04:41 support kernel: nfs: task 9147 can't get a request slot
Apr 29 15:04:58 support kernel: nfs: server inx OK
Apr 29 15:05:16 support kernel: nfs: server inx not responding, still trying
Apr 29 15:05:16 support kernel: nfs: server inx OK
Apr 29 15:05:38 support kernel: nfs: server inx not responding, still trying
Apr 29 15:05:38 support kernel: nfs: server inx OK
inx is the 2.0.36 kernel. This came from copying a file from either mwg or
support to inx. I get a lot of server not responding from mwg and support,
too. Everything is user NFS daemons, because I can't get the kernel daemons
to export all the mount points: kexportfs gets an invalid argument on mount
directories from the kernel. The backup last night (tape drive is on inx)
did not finish because of these problems.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/