Re: Question on setting up NFS
On Tue, Apr 22, 2008 at 01:48:32AM +1000, Owen Townend wrote: > On 22/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > Googling a little finds others that have had the same issue and resolved > it inexplicably by reinstalling nfs-common. I'll throw out this suggestion since I've sometimes got caught: Do you have a firewall running on either box that is trapping the RPC/NFS/whatever packets or connection attempts? What about /etc/host.allow: 8>-- # /etc/hosts.allow: list of hosts that are allowed to access the system. # See the manual pages hosts_access(5), hosts_options(5) # and /usr/doc/netbase/portmapper.txt.gz # # Example:ALL: LOCAL @some_netgroup # ALL: .foobar.edu EXCEPT terminalserver.foobar.edu # # If you're going to protect the portmapper use the name "portmap" for the # daemon name. Remember that you can only use the keyword "ALL" and IP # addresses (NOT host or domain names) for the portmapper. See portmap(8) # and /usr/doc/portmap/portmapper.txt.gz for further information. # ALL:192.168. ALL:127.0.0.1 portmap:192.168. statd: 192.168. 8>-- Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question on setting up NFS
On Mon, 21 Apr 2008, Pete Kay shared this with us all: >--} Reading state information... Done >--} nfs-common is already the newest version. >--} 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. Does the <2 not upgraded> have anything to offer? Maybe there is something that requires an upgrade do: # apt-get dselect upgrade ad maybe that will help with your problem? HTH Charlie -- Registered Linux User:- 329524 *** In this way and that I tried to save the old pail Since the bamboo strip was weakening, about to break Until at last the bottom fell out. No more water in the pail! No more moon in the water! -CHIYONO *** Debian, just the best way to create magic ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question on setting up NFS
On 22/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > Hi Owen: > > Here is the output of running the 4 commands: > > ser:# showmount -e 192.168.1.101 > Export list for 192.168.1.101: > /var/fs 127.0.0.1,192.168.1.104 > Hey, I'm running short on ideas here. Anyone else care to weigh in? Is anything coming through dmesg as you run these commands? The only other mount option that I didn't mention was version2: # mount -vt nfs -o nfsvers=2 192.168.1.101:/var/fs /mnt/nfs Is the IP address of 'ser' definately 192.168.1.104? (It should throw a permission error if it's not though, not this) Are the versions of nfs-common the same on both the server and client? Googling a little finds others that have had the same issue and resolved it inexplicably by reinstalling nfs-common. cheers, Owen.
Re: Question on setting up NFS
Hi Owen: Here is the output of running the 4 commands: ser:# showmount -e 192.168.1.101 Export list for 192.168.1.101: /var/fs 127.0.0.1,192.168.1.104 ser:# mount -v 192.168.1.101:/var/fs /mnt/nfs mount: no type was given - I'll assume nfs because of the colon mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so ser:# mount -vt nfs -o nolock 192.168.1.101:/var/fs /mnt/nfs mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so ser:# mount -vt nfs4 192.168.1.101:/var/fs /mnt/nfs mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so ser:#
Re: Question on setting up NFS
On 21/04/2008, Daniel Burrows <[EMAIL PROTECTED]> wrote: > > On Mon, Apr 21, 2008 at 10:06:38PM +1000, Owen Townend < > [EMAIL PROTECTED]> was heard to say: > > > Do you have the nfs-common package installed? > > > I thought it was nfs-client you needed to connect to an NFS server? > > Daniel Hey, Yeah, nfs-client is a virtual package that depends only on nfs-common. I was testing the commands here on Ubuntu, but firing up an etch vm I noticed that /sbin/mount/nfs doesn't exist but it has no issues mounting nfs. It does have the nfs-common package installed. NFS mounting is handled internally by /bin/mount instead of using /sbin/mount.nfs What is the output of this?: ser:# showmount -e 192.168.1.101 and trying explicit options: ser:# mount -v 192.168.1.101:/var/fs /mnt/nfs ser:# mount -vt nfs -o nolock 192.168.1.101:/var/fs /mnt/nfs ser:# mount -vt nfs4 192.168.1.101:/var/fs /mnt/nfs cheers, Owen. -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > >
Re: Question on setting up NFS
On Mon, Apr 21, 2008 at 10:06:38PM +1000, Owen Townend <[EMAIL PROTECTED]> was heard to say: > Do you have the nfs-common package installed? I thought it was nfs-client you needed to connect to an NFS server? Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question on setting up NFS
Hi Owen, Thank you so much for your guidance. Based on your instruction, I found out the following: 1. /sbin/mount.nfs does not exist in the client machine and server machine 2. I can mount locally on the server machine with no problem. What could have gone wrong? Thanks, Pete On Mon, Apr 21, 2008 at 8:41 PM, Owen Townend <[EMAIL PROTECTED]> wrote: > > > On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Here is the result for the two commands: > > > > ser:# dmesg |tail > > EXT3 FS on hda1, internal journal > > loop: loaded (max 8 devices) > > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > > [EMAIL PROTECTED] > > NET: Registered protocol family 10 > > lo: Disabled Privacy Extensions > > IPv6 over IPv4 tunneling driver > > ACPI: Power Button (FF) [PWRF] > > ACPI: Power Button (CM) [PWRB] > > lp0: using parport0 (interrupt-driven). > > ppdev: user-space parallel port driver > > > > ser:# apt-get install nfs-common > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > nfs-common is already the newest version. > > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > > > I think the nfs-common is already installed... > > > > > > > > Pete > > > > Hey, > Looks ok so far, more things to check: > Does /sbin/mount.nfs exist? > if you add/change the server line to > /var/fs 127.0.0.1(rw,sync) > and re-export can you mount this locally on the server? > debian:# mount localhost:/var/fs /mnt > > Also, in your initial email, either the output of `exportfs` > was truncated or the export isn't working as it should be > listed in the output. Try reloading and/or restarting the > nfs-server: > debian:# invoke-rc.d nfs-kernel-server reload > (or nfs-user-server) > > cheers, > Owen. > >
Re: Question on setting up NFS
On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > Hi, > > Here is the result for the two commands: > > ser:# dmesg |tail > EXT3 FS on hda1, internal journal > loop: loaded (max 8 devices) > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: > [EMAIL PROTECTED] > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > IPv6 over IPv4 tunneling driver > ACPI: Power Button (FF) [PWRF] > ACPI: Power Button (CM) [PWRB] > lp0: using parport0 (interrupt-driven). > ppdev: user-space parallel port driver > > ser:# apt-get install nfs-common > Reading package lists... Done > Building dependency tree > Reading state information... Done > nfs-common is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > I think the nfs-common is already installed... > > > > Pete > Hey, Looks ok so far, more things to check: Does /sbin/mount.nfs exist? if you add/change the server line to /var/fs 127.0.0.1(rw,sync) and re-export can you mount this locally on the server? debian:# mount localhost:/var/fs /mnt Also, in your initial email, either the output of `exportfs` was truncated or the export isn't working as it should be listed in the output. Try reloading and/or restarting the nfs-server: debian:# invoke-rc.d nfs-kernel-server reload (or nfs-user-server) cheers, Owen.
Re: Question on setting up NFS
Hi, Here is the result for the two commands: ser:# dmesg |tail EXT3 FS on hda1, internal journal loop: loaded (max 8 devices) device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: [EMAIL PROTECTED] NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver ser:# apt-get install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done nfs-common is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. I think the nfs-common is already installed... Pete On Mon, Apr 21, 2008 at 8:06 PM, Owen Townend <[EMAIL PROTECTED]> wrote: > > > On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > If I execute the command, I still get error: > > > > ser:# mount -t nfs 192.168.1.101:/var/fs /mnt/nfs/fs > > mount: wrong fs type, bad option, bad superblock on 192.168.1.101: > > /var/fs, > >missing codepage or helper program, or other error > >(for several filesystems (e.g. nfs, cifs) you might > >need a /sbin/mount. helper program) > >In some cases useful info is found in syslog - try > >dmesg | tail or so > > > > > > I can't figure out where. > > > > Thank you in advance for all your help. > > > > Regards, > > Pete > > > Hey, > Does dmesg|tail have anything relevant? > Do you have the nfs-common package installed? > > cheers, > Owen. > >
Re: Question on setting up NFS
On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > Hi, > > If I execute the command, I still get error: > > ser:# mount -t nfs 192.168.1.101:/var/fs /mnt/nfs/fs > mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, >missing codepage or helper program, or other error >(for several filesystems (e.g. nfs, cifs) you might >need a /sbin/mount. helper program) >In some cases useful info is found in syslog - try >dmesg | tail or so > > > I can't figure out where. > > Thank you in advance for all your help. > > Regards, > Pete Hey, Does dmesg|tail have anything relevant? Do you have the nfs-common package installed? cheers, Owen.
Re: Question on setting up NFS
Hi, If I execute the command, I still get error: ser:# mount -t nfs 192.168.1.101:/var/fs /mnt/nfs/fs mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so I can't figure out where. Thank you in advance for all your help. Regards, Pete On Mon, Apr 21, 2008 at 3:14 PM, Owen Townend <[EMAIL PROTECTED]> wrote: > > [snip > On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > > ser:# mount 192.168.1.101:/var/fs /mnt/nfs > > mount: wrong fs type, bad option, bad superblock on 192.168.1.101: > > /var/fs, > >missing codepage or helper program, or other error > >(for several filesystems (e.g. nfs, cifs) you might > >need a /sbin/mount. helper program) > >In some cases useful info is found in syslog - try > >dmesg | tail or so > > > > [snip] > > Any inputs will be greatly appreciated. > > > > > > Regards, > > Pete > > > > > Hey, > Does it still give the error if you explicitly give the type?: > ser:# mount -t nfs 192.168.1.101:/var/fs /mnt/nfs > > cheers, > Owen. >
Re: Question on setting up NFS
[snip On 21/04/2008, Pete Kay <[EMAIL PROTECTED]> wrote: > > ser:# mount 192.168.1.101:/var/fs /mnt/nfs > mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs, >missing codepage or helper program, or other error >(for several filesystems (e.g. nfs, cifs) you might >need a /sbin/mount. helper program) >In some cases useful info is found in syslog - try >dmesg | tail or so > > [snip] > Any inputs will be greatly appreciated. > > > Regards, > Pete > > Hey, Does it still give the error if you explicitly give the type?: ser:# mount -t nfs 192.168.1.101:/var/fs /mnt/nfs cheers, Owen.
Question on setting up NFS
Hi,
I am trying to map the directory /var/fs at remote server ( 192.168.1.101)
to local directory /mnt/nfs/fs
It is giving me the following error. How come? I am following the
procedure at http://www.debianhelp.co.uk/nfs.htm
ser:# mount 192.168.1.101:/var/fs /mnt/nfs
mount: wrong fs type, bad option, bad superblock on 192.168.1.101:/var/fs,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount. helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
In NFS server, I have /etc/exports:
/var/fs 192.168.1.104(rw,sync)
When running exportfs, I am getting
debian:/home/anne# exportfs -a
exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check'
speci$
Assuming default behaviour ('subtree_check').
NOTE: this default will change with nfs-utils version 1.1.0
debian:/home/anne#
Any inputs will be greatly appreciated.
Regards,
Pete
