public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Flophouse Joe <flophousejoe-gentoo-user-xdzvn3@halibutdepot.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NFS Wont mount
Date: Tue, 14 Nov 2006 18:31:15 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0611141825260.28625@becky16.halibutdepot.org> (raw)
In-Reply-To: <3767b850611141518g3782e0ddye9f03034c57723d0@mail.gmail.com>

On Tue, 14 Nov 2006, timothy johnson wrote:

> Joe, I have tried this and got the same results
>
> On 11/14/06, Flophouse Joe <flophousejoe-gentoo-user-xdzvn3@halibutdepot.org>
> wrote:
>>
>>  On Tue, 14 Nov 2006, timothy johnson wrote:
>> 
>> >  mount 10.250.107.10:/home /mnt/pdc1Home
>> >  returns
>> >  mount: 10.250.107.10:/home failed, reason given by server: Permission
>>  denied
>> > 
>> >  /etc/exports
>> >  /home   (no_root_squash,rw)
>>
>>  Try explicitly listing the IP address of the host(s) that need to be
>>  able to mount this filesystem.  man exports(5) will give you the
>>  details, but you'd probably want something like the following:
>>
>>  /etc/exports:
>>          /home   192.168.1.100(no_root_squash,rw)

I'm going out on a limb here, but it's worth asking if the spacing in
/etc/exports is "sane".  It's notoriously easy to misconfigure NFS due
to an errant space, as whitespace is significant in exports(5).

 	/home	192.168.1.100(no_root_squash,rw)

means something very different from

 	/home	192.168.1.100 (no_root_squash,rw)

So, is it possible that there's a misplaced space, anywhere on the line?

You might also get a "sanity check" with the command exportfs(8).  This
will parse your /etc/exports as NFS sees it and report back to you how
NFS interprets it.

If those don't turn up any leads, then I don't immediately have any
ideas that spring out.

If you're going into sanity check mode, it never hurts to temporarily 
throw out your firewall rulesets on each machine (but I don't really see 
how that could be an issue in this case).

Joe
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-11-14 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 22:06 [gentoo-user] NFS Wont mount timothy johnson
2006-11-14 22:06 ` timothy johnson
2006-11-14 22:11 ` Flophouse Joe
2006-11-14 23:18   ` timothy johnson
2006-11-14 23:31     ` Flophouse Joe [this message]
2006-11-14 22:17 ` [gentoo-user] " Regis Decamps
2006-11-14 23:18   ` timothy johnson
2006-11-15  7:24 ` [gentoo-user] " Alan McKinnon

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=Pine.LNX.4.64.0611141825260.28625@becky16.halibutdepot.org \
    --to=flophousejoe-gentoo-user-xdzvn3@halibutdepot.org \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox