From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ford Subject: Re: NFS problems across reboot Date: Sun, 07 Apr 2002 01:59:08 -0500 Sender: nfs-admin@lists.sourceforge.net Message-ID: <3CAFEE3C.8020606@blue-labs.org> References: <3CACA93C.5010304@blue-labs.org> <3CAD6A78.4205CD61@moving-picture.com> <3CAFCE8C.5030300@blue-labs.org> <15535.55222.401084.736426@notabene.cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: nfs@lists.sourceforge.net, James Pearson Received: from 60.54.252.64.snet.net ([64.252.54.60] helo=hotmale.boyland.org ident=kaliuser) by usw-sf-list1.sourceforge.net with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.31-VA-mm2 #1 (Debian)) id 16u6bP-0002MV-00 for ; Sat, 06 Apr 2002 22:56:40 -0800 To: Neil Brown Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: That was the problem. Everything mounts just fine normally. When the server reboots, the client loses access. All the client has to do is unmount and remount and everything is fine again. If it were a matter of what was exported, then the remount should fail, but it doesn't. Why does the client lose the access but with no action on the server part, the client regains access? (to whom know the answer, please don't let this thread just die away, ambiguity like this doesn't do anyone any good) The fix was to run exportfs. I wasn't running exportfs on boot. I didn't realize it was needed because mounting worked just fine without it. It is needed for already established connections. David Neil Brown wrote: >On Saturday April 6, david+cert@blue-labs.org wrote: > >>Well, I'm an all Linux shop here, here are a few points to consider, >>Trond, please help us out. >> >>a) All machines are Linux >>b) this is 100% repeatable >>c) this is entirely unacceptable, every user (/home is mounted) has to >>log out of their machine in order to remount, daemons need shut down. >> >>Here's the scoop: >> >>a) Linux 2.4.18-pre6 on one nfs server, 2.4.19-pre6 on the other >>b) 2.4.18-pre7 through 2.4.19-pre6 on clients >>c) mount options are all like: defaults,rsize=8192,wsize=8192 >>d) programs run/ning, portmap, kmountd, knfsd 5, lockd, and statd. >>e) no firewall rules, /etc/exports is setup using individual IPs since >>the friggen system can't deal with ranges or hostnames properly, >>"Hostname is the same as "hostname" in DNS land, it should be in NFS >>land as well. exports is like: /path 1.2.3.4(rw,no_root_squash). >>f) hosts.allow is basically *:all >> >>When the server reboots (cleanly), the clients get the following, from >>rebooting to running: >>nfs: server james not responding, still trying >>nfs: server james not responding, still trying >>nfs: server james OK >>nfs: server james OK >>nfs_statfs: statfs error = 13 >>nfs_statfs: statfs error = 13 >>nfs_statfs: statfs error = 13 >> > >13 == EACCES. Looks like the filesystem isn't exported. > >Show us the relevent /etc/init.d file. >My guess is that "exportfs -a" is being run *After* rpc.nfsd. >It must must run *before* for correct operation. > >NeilBrown > _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs