NFS newbie troubles

(1) Accessing Windows partition on the NFS server from client
NFS client can't access /mnt/windows dirs and files on the NFS server.

(2) NFS lock
Even after the client unmounts NFS mount point, we can't access files on
the server from THE server itself.

(3) NFS client don't access new hostname of the server
After changing the server host name by hostname command, the mount command
line on the client can't recognize the new host name. Only server's IP
address works on the command line:

mount -t nfs 192.168.11.3:/pub /nfs

I'd like to know the causes/reasons of above phenomenon and workarounds for
those.

Thanks in advance.

On Mon, 11 Oct 2004 22:28:53 -0700, hiwa wrote:

> (1) Accessing Windows partition on the NFS server from client
> NFS client can't access /mnt/windows dirs and files on the NFS server.

Need some additional info... How is your filesystem set up - a single
volume? multiple volumes? When you access volumes via NFS you will only
see the files on the nfs export volume - NFS will not span the entire
filesystem like SAMBA shares will.


>
> (2) NFS lock
> Even after the client unmounts NFS mount point, we can't access files on
> the server from THE server itself.

Again - let's get more info on your filesystem setup. Maybe post your
fstab and exports files.


>
> (3) NFS client don't access new hostname of the server
> After changing the server host name by hostname command, the mount command
> line on the client can't recognize the new host name. Only server's IP
> address works on the command line:
>
> mount -t nfs 192.168.11.3:/pub /nfs
>

Take a look at how the name resolution is occurring (or in this case, 'not
occurring). If you change th ehostname via the command line are you
updating DNS or hosts entries?




> I'd like to know the causes/reasons of above phenomenon and workarounds
> for those.
>
> Thanks in advance.

"William B. Cattell" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> On Mon, 11 Oct 2004 22:28:53 -0700, hiwa wrote:
>
> > (1) Accessing Windows partition on the NFS server from client
> > NFS client can't access /mnt/windows dirs and files on the NFS server.
>
> Need some additional info... How is your filesystem set up - a single
> volume? multiple volumes? When you access volumes via NFS you will only
> see the files on the nfs export volume - NFS will not span the entire
> filesystem like SAMBA shares will.
>
>
> >
> > (2) NFS lock
> > Even after the client unmounts NFS mount point, we can't access files on
> > the server from THE server itself.
>
> Again - let's get more info on your filesystem setup. Maybe post your
> fstab and exports files.
>
>
> >
> > (3) NFS client don't access new hostname of the server
> > After changing the server host name by hostname command, the mount command
> > line on the client can't recognize the new host name. Only server's IP
> > address works on the command line:
> >
> > mount -t nfs 192.168.11.3:/pub /nfs
> >
>
> Take a look at how the name resolution is occurring (or in this case, 'not
> occurring). If you change th ehostname via the command line are you
> updating DNS or hosts entries?
>
>
>
>
> > I'd like to know the causes/reasons of above phenomenon and workarounds
> > for those.
> >
> > Thanks in advance.

Thanks for showing concern.

The /etc/exports entry was:

/ 192.168.11.0/24(ro,no_root_squash)

As seen above, entire file system of the server machine,
including /mnt/windows, was accessible from the client.

No new fstab and hosts entries were added then.

[server file system]
/dev/hda1 ... /mnt/windows
/dev/hda2 ... hda5 ... /arc -- for miscellaneous data files
hda6 ... swap
/dev/hda3 ... /
/dev/hda4 ... /usr

Red Hat 9 init.d/portmap, nfs and nfslock run from rc5.d on
boot up.

> updating DNS or hosts entries?
DNS is completely out of my still shallow Linux knowledge.
I feel sad about that.

And the mount command on the client was:

mount -t nfs 192.168.11.3:/ /nfs

(E-Mail Removed) (hiwa) wrote in message news:<(E-Mail Removed) om>...
> And the mount command on the client was:
>
> mount -t nfs 192.168.11.3:/ /nfs

from the client do

showmount -p 192.168.11.3

and see what comes back

also try

/mnt/windows 192.168.11.0/24(ro,no_root_squash)

in /etc/exports instead

then run

exportfs -a

On Tue, 12 Oct 2004 03:55:28 -0700, hiwa wrote:

> And the mount command on the client was:
>
> mount -t nfs 192.168.11.3:/ /nfs

Remember what I wrote about NFS not automagically spanning filesystems
the way SAMBA does? That means that when you export root '/' which
resides on /dev/hda3 NFS will not automatically include /arc (/dev/hda5),
windows (/dev/hda1) or /usr (/dev/hda4). You would need to export each of
those to have them shareable.

If you loaded SAMBA and shared root '/' then yes, everything would be
available via the share (data on all partitions).

For name resolution - add entries in the /etc/hosts file for all your
machines. Don't worry about DNS yet. It's fun but if you're learning you
can wait on it.

After adding host entries for all machines on each machine you'll be able
to resolve them by name... Again, not neccessary but it makes stuff
easier.

"William B. Cattell" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...

Thanks!

> On Tue, 12 Oct 2004 03:55:28 -0700, hiwa wrote:
>
> > And the mount command on the client was:
> >
> > mount -t nfs 192.168.11.3:/ /nfs
>
> Remember what I wrote about NFS not automagically spanning filesystems
> the way SAMBA does? That means that when you export root '/' which
> resides on /dev/hda3 NFS will not automatically include /arc (/dev/hda5),
> windows (/dev/hda1) or /usr (/dev/hda4). You would need to export each of
> those to have them shareable.
Your word is the savior. It has cleared the fog.

>
> If you loaded SAMBA and shared root '/' then yes, everything would be
> available via the share (data on all partitions).
>
> For name resolution - add entries in the /etc/hosts file for all your
> machines. Don't worry about DNS yet. It's fun but if you're learning you
> can wait on it.
Your word is a load off my mind! Thanks again.

>
> After adding host entries for all machines on each machine you'll be able
> to resolve them by name... Again, not neccessary but it makes stuff
> easier.
I will try /etc/hosts on the client.

On Wed, 13 Oct 2004 01:57:15 -0700, hiwa wrote:

> "William B. Cattell" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
>
> Thanks!
>

snip a lot...

> I will try /etc/hosts on the client.

Glad to help. I learned the same way - trying stuff and asking questions
when it didn't work. 8-}