[7.1-RELEASE-p2 amd64] NFS mount in fstab hangs duringmountcritremote execution

Fri Jan 30 07:55:23 PST 2009

I've done some further investigation and this is what happens:

The mountcritremote script executes "mount -a -t nfs" and times out. If
this script is aborted, the NFS export is mounted later by the mountlate
script with " mount -a -l", this succeeds. This is the reason that the
export is mounted after sending ctrl-d, the initial mount never
succeeds.

>From what I can see now this is neither a firewall nor a NFS-version
issue, else it would not succeed in the mountlate script.

I'm still puzzled why on other boxes this is not a problem, while it is
at this box.

-- 
Met vriendelijke groet / Kind Regards,
Worldmax Operations B.V.

Arjan van der Oest
Network Design Engineer

T.: +31 (0) 88 001 7912
F.: +31 (0) 88 001 7902
M.: +31 (0) 6 10 62 58 46

E.: arjan.van.der.oest at worldmax.nl
W.:www.worldmax.nl
W.:www.aerea.nl
GPG: https://keyserver.pgp.com/ (Key ID: 07286F78) fingerprint: 2E9F
3AE2 0A8B 7579 75A9  169F 5D9E 5312 0728 6F78

-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org] On Behalf Of Arjan van der
Oest
Sent: vrijdag 30 januari 2009 14:36
To: Mel; freebsd-questions at freebsd.org
Subject: RE: [7.1-RELEASE-p2 amd64] NFS mount in fstab hangs
duringmountcritremote execution

Mel wrote:
>> - why does the system tries to mount the nfs filesystem from the
fstab
>> while nfs_client_enable has been set to no in rc.conf?

>Because there is no relation between the two. You could be using a 3rd
>party nfs kernel module.

Yes, but I am not. I'm using the default kernel option which I believe
is enabled with the mentioned rc.conf switch, or am I wrong here?

>> And more bizarre: when interrupting the 
>> mountcritremote script the share has been actually mounted, so it
seems >> the 'mount -a -t nfs' command has actually been executed
successfully.
>
>Looks more like the server is not sending a "success" message or it got

>lost in transit. If this is 100% reproducable, look into compatibility 
>issues, by scaling down the NFS version for the mount and check
firewall
>rules on both ends.

Firewall has been disabled and seems not the problem, since (even with
the firewall enabled) the manual mount works fine. In case of fw
problems this would be a problem too.

Also what puzzles me is the fact that a new identical setup box has no
problem. As I wrote earlier the only difference is that I did not select
the 'enable nfs client' from the sysinstall this time. I have not used
any of the mentioned flags on the second box too, so why does it work on
that machine?

-- 
Met vriendelijke groet / Kind Regards,
Worldmax Operations B.V.

Arjan van der Oest
Network Design Engineer

T.: +31 (0) 88 001 7912
F.: +31 (0) 88 001 7902
M.: +31 (0) 6 10 62 58 46

E.: arjan.van.der.oest at worldmax.nl
W.:www.worldmax.nl
W.:www.aerea.nl
GPG: https://keyserver.pgp.com/ (Key ID: 07286F78, fingerprint: 2E9F
3AE2 0A8B 7579 75A9  169F 5D9E 5312 0728 6F78)

Internet communications are not secure; therefore, the integrity of this
e-mail cannot be guaranteed following transmission on the Internet. This
e-mail may contain confidential information. If you have received this
e-mail in error, please notify the sender and erase this e-mail. Use of
this e-mail by any person other than the addressee is strictly
forbidden. This e-mail is believed to be free of any virus that might
adversely affect the addressee's computer system; however, no
responsibility is accepted for any loss or damage arising in any way
from its use. All the preceding disclaimers also apply to any possible
attachments to this e-mail.
_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"

No virus found in this incoming message.
Checked by AVG - http://www.avg.com 
Version: 8.0.176 / Virus Database: 270.10.15/1924 - Release Date:
1/29/2009 5:57 PM

Internet communications are not secure; therefore, the integrity of this e-mail cannot be guaranteed following transmission on the Internet. This e-mail may contain confidential information. If you have received this e-mail in error, please notify the sender and erase this e-mail. Use of this e-mail by any person other than the addressee is strictly forbidden. This e-mail is believed to be free of any virus that might adversely affect the addressee's computer system; however, no responsibility is accepted for any loss or damage arising in any way from its use. All the preceding disclaimers also apply to any possible attachments to this e-mail.