Networking Forums

Networking Forums > Computer Networking > Linux Networking > NFS newbie troubles

Reply
Thread Tools Display Modes

NFS newbie troubles

 
 
hiwa
Guest
Posts: n/a

 
      10-12-2004, 05:28 AM
(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.
 
Reply With Quote
 
 
 
 
William B. Cattell
Guest
Posts: n/a

 
      10-12-2004, 05:45 AM
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.


 
Reply With Quote
 
hiwa
Guest
Posts: n/a

 
      10-12-2004, 10:52 AM
"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.
 
Reply With Quote
 
hiwa
Guest
Posts: n/a

 
      10-12-2004, 10:55 AM
And the mount command on the client was:

mount -t nfs 192.168.11.3:/ /nfs
 
Reply With Quote
 
Binner
Guest
Posts: n/a

 
      10-12-2004, 03:08 PM
(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
 
Reply With Quote
 
William B. Cattell
Guest
Posts: n/a

 
      10-12-2004, 05:46 PM
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.




 
Reply With Quote
 
hiwa
Guest
Posts: n/a

 
      10-13-2004, 08:57 AM
"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.
 
Reply With Quote
 
Bill Cattell
Guest
Posts: n/a

 
      10-16-2004, 07:28 PM
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-}
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
802.11n troubles Warren Oates Wireless Internet 0 09-23-2007 10:53 AM
RIM's troubles not over! John Navas Wireless Internet 12 05-17-2006 07:25 PM
NFS troubles Kevin Linux Networking 5 03-29-2005 12:01 AM
NAT + FTP = troubles? Massimo Windows Networking 13 05-23-2004 06:48 PM
Lan troubles XP/ME FABIO55 Windows Networking 1 10-30-2003 09:53 PM



1 2 3 4 5 6 7 8 9 10 11