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.<type> 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

[snip
On 21/04/2008, Pete Kay <petedao@gmail.com> 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.<type> 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.

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.<type> 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 <owen.townend@gmail.com> wrote:


[snip
On 21/04/2008, Pete Kay <petedao@gmail.com> 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.<type> 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.

On 21/04/2008, Pete Kay <petedao@gmail.com> 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.<type> 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.

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: dm-devel@redhat.com

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 <owen.townend@gmail.com> wrote:



On 21/04/2008, Pete Kay <petedao@gmail.com> 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.<type> 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.