On Aug 28, 2012, at 2:08 PM, Bryan Schumaker <bjschuma@xxxxxxxxxx> wrote: > On 08/28/2012 02:06 PM, Myklebust, Trond wrote: >> On Tue, 2012-08-28 at 14:01 -0400, Frank Nicholas wrote: >>> On Aug 28, 2012, at 1:46 PM, Frank Nicholas <frank@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: >>> >>>> >>>> On Aug 28, 2012, at 1:43 PM, Jim Rees <rees@xxxxxxxxx> wrote: >>>> >>>>> Frank Nicholas wrote: >>>>> >>>>> Thanks for the quick reply. >>>>> >>>>> The patches applied cleanly. I've rebuilt my kernel. The reboot will >>>>> have to wait until I have physical access to the machine to do a hard >>>>> power off… Unless you know of some way to clean up the hung NFS items so >>>>> I can do a reboot. Currently if I try a 'shutdown -r now', the system >>>>> hangs on trying to clean up the NFS items. >>>>> >>>>> Did you try "reboot -f"? >>>> >>>> >>>> Yep - Remembering back to the old Solaris days, 'sync ; sync ; sync ; reboot -f'. >>>> >>>> That got it. The 'emerge --sync' ran fine & the VM's that are using stores from NFS shares are working ok. So far no NFS issues. >>>> >>>> Thanks. >>>> >>> >>> After the reboot, doing an 'emerge --sync' & starting a VM, I have the following in my syslog: >>> >>> Aug 28 13:52:09 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:52:19 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> Aug 28 13:54:05 martin rpc.idmapd[2899]: nfscb: write(/var/lib/nfs/rpc_pipefs//nfs/clnt0/idmap): No space left on device >>> >>> I believe each group of these (by date/time) were when I did the 'emerge --sync' & when I started the VM who has a virtual drive on an NFS share. I don't remember seeing anything like this before. Is this due to the patch? Should I be concerned? I know this is a pipe, but I've confirmed there is plenty of free disk space everywhere. The pipe does exist on the file system. There is plenty of free memory. Any suggestions? >> >> An early version of those patches did indeed cause problems such as the >> above. Are you sure that you applied the patches that actually went >> upstream in > > No, I don't think he did. I forgot you fixed up a few things, so I sent him the last copy I had. > > - Bryan > >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=c5066945b7ea346a11424dbeb7830b7d7d00c206 >> and >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=12dfd080556124088ed61a292184947711b46cbe >> > rpc.idmapd is running. I applied the patches Bryan e-mailed me. I'll apply the linked patches & confirm they clear up the log entries. Thanks.-- 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
