From: David Ford <david+cert@blue-labs.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: nfs@lists.sourceforge.net, James Pearson <james-p@moving-picture.com>
Subject: Re: NFS problems across reboot
Date: Sun, 07 Apr 2002 01:59:08 -0500 [thread overview]
Message-ID: <3CAFEE3C.8020606@blue-labs.org> (raw)
In-Reply-To: 15535.55222.401084.736426@notabene.cse.unsw.edu.au
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
next prev parent reply other threads:[~2002-04-07 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 19:27 NFS problems across reboot David Ford
2002-04-05 9:12 ` James Pearson
2002-04-07 4:43 ` David Ford
2002-04-07 5:23 ` Neil Brown
2002-04-07 5:44 ` Neil Brown
2002-04-07 6:48 ` David Ford
2002-04-08 13:42 ` James Pearson
2002-04-08 15:23 ` James Pearson
2002-04-08 23:10 ` Neil Brown
2002-04-07 6:39 ` Daniel Freedman
2002-04-08 2:50 ` Neil Brown
2002-04-07 6:59 ` David Ford [this message]
2002-04-08 2:48 ` Neil Brown
2002-04-08 12:15 ` Andreas Unterluggauer
2002-04-08 22:58 ` Neil Brown
[not found] <E16uI1v-00067H-00@usw-sf-list1.sourceforge.net>
2002-04-08 0:43 ` Al Borchers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CAFEE3C.8020606@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=james-p@moving-picture.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.