0n Wed, Dec 22, 2004 at 08:29:41PM -0600, Conrad J. Sabatier wrote: >On Tue, 21 Dec 2004 05:51:57 -0600, "Conrad J. Sabatier" ><conrads_at_cox.net> wrote: > >> I'm seeing some real instability in NFS since approximately last >> Friday. Intermittently, I'm seeing messages such as the following: >> >> On the client machine: >> >> Dec 20 23:18:22 dolphin kernel: impossible packet length (1820291) >> from nfs server gateway:/mm >> Dec 21 00:51:47 dolphin kernel: impossible packet length (1746474142) >> from nfs server gateway:/mm >> >> and >> >> Dec 21 01:14:41 dolphin kernel: nfs send error 35 for server >> gateway:/mm Dec 21 01:16:33 dolphin kernel: nfs send error 35 for >> server gateway:/mm Dec 21 01:16:38 dolphin kernel: nfs send error 35 >> for server gateway:/mm Dec 21 01:16:40 dolphin kernel: nfs server >> gateway:/mm: not responding Dec 21 01:16:43 dolphin kernel: nfs server >> gateway:/mm: is alive again >> >> On the server machine: >> >> Dec 20 21:52:48 gateway kernel: nfsd send error 32 >> Dec 20 21:57:50 gateway kernel: nfsd send error 32 >> Dec 20 22:00:45 gateway kernel: nfsd send error 32 >> Dec 20 22:23:29 gateway kernel: nfsd send error 32 >> Dec 20 23:18:23 gateway kernel: nfsd send error 32 >> >> Then, ultimately, all NFS communication just breaks down >> altogether until a reboot. >> >> I'm also seeing "sillyrenames" left behind occasionally in nfs-mounted >> directories. >> >> There were a couple of nfs-related commits last Thursday, which I >> believe are most likely the culprit, although I don't know which ones >> exactly. > >I do believe this problem is related to the new direct i/o mode for nfs. >Disabling it seems to have made the problem disappear. What is the "new direct i/o mode for nfs" all about ? - aWReceived on Thu Dec 23 2004 - 03:27:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC