On 25/01/12 04:50, Sylvain wrote: > On 24. 01. 12 09:28, Scott Ferguson wrote: >> On 24/01/12 18:50, Sylvain wrote: >>> I tried to SIGKILL the [nfsiod] process but it didn't get killed. I >>> also tried to kill the various rpcbind processes but it didn't change >>> anything. >>> >>> I also tried autofs as Scott suggested, but the same problem occured >>> when I unplugged the network cable (most of the system hangs, can't >>> reboot nor halt). Here's how I configured autofs: >>> >>> /etc/auto.misc: >>> bazinga -retry=1,rw,hard,size=8192,wsize=8192 >>> 192.168.2.77:/DataVolume/Public
bazinga -fstype=nfs,bg,-retries=1,timeo=1,rw,soft,size=8192,wsize=8192 192.168.2.77:/DataVolume/Public >>> >>> /etc/auto.master: >>> /misc /etc/auto.misc --timeout 20 /misc /etc/auto.misc >>> >>> Here's what I found in the syslog: >>> >>>> Jan 23 22:59:17 cid kernel: [ 510.944160] nfs: server 192.168.2.77 >>>> not responding, still trying >>>> Jan 23 23:01:22 cid kernel: [ 635.616161] nfs: server 192.168.2.77 >>>> not responding, still trying >>>> Jan 23 23:01:46 cid sm-notify[841]: DNS resolution of Bazinga.local >>>> failed; retrying later >>>> Jan 23 23:03:51 cid sm-notify[841]: DNS resolution of Bazinga.local >>>> failed; retrying later >>>> Jan 23 23:05:56 cid sm-notify[841]: DNS resolution of Bazinga.local >>>> failed; retrying later >>>> Jan 23 23:07:56 cid sm-notify[841]: Unable to notify Bazinga.local, >>>> giving up >>> >>> I'm not sure why it's trying to resolve the "bazinga.local" name, and >>> even when it gave up with the resolution, it didn't unfreeze anything. >>> Also nfs seems to be still trying to reach the server (the cable was >>> unplugged at 22:56). >>> >>> Thanks for your help, >>> Sylvain >>> >>> >> What do you have in /etc/hosts? > > Just the usual stuff: > >> 127.0.0.1 localhost >> 127.0.1.1 cid.localdomain cid >> >> # The following lines are desirable for IPv6 capable hosts >> ::1 ip6-localhost ip6-loopback >> fe00::0 ip6-localnet >> ff00::0 ip6-mcastprefix >> ff02::1 ip6-allnodes >> ff02::2 ip6-allrouters > > On 24. 01. 12 09:28, Tom H wrote: >> It's avahi that's trying to resolve "Bazinga" through "Bazinga.local". >> >> Is Bazinga the hostname of 192.168.2.77? >> >> Did ifs quit after avahi failed? > > No, nfs didn't quit after avahi failed (the nfsiod process is still > here). Also I don't know the hostname of 192.168.2.77, because it's just > a NAS box on which I don't have any control. > > Sylvain > > I suspect avahi is the problem (as suggested by Brian). Do you really need avahi? Where does the NAS box get it's IP address from? Try adding bazinga to /etc/hosts Cheers -- Iceweasel/Firefox extensions for finding answers to Debian questions:- https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/ NOTE: new update available for Debian Buttons (New button for querying Debian Developer Package):- https://addons.mozilla.org/en-US/firefox/addon/debian-buttons/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f1f257f.1070...@gmail.com
