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.debian.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 er program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> er 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 er program, or other error
> (for several filesystems (e.g. nfs, cifs) you might
> need a /sbin/mount.<type> er 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 er program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> er 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 .

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 er program, or other error
> > (for several filesystems (e.g. nfs, cifs) you might
> > need a /sbin/mount.<type> er 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 er program, or other error
> (for several filesystems (e.g. nfs, cifs) you might
> need a /sbin/mount.<type> er 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 .
>
> 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 er program, or other error
> > (for several filesystems (e.g. nfs, cifs) you might
> > need a /sbin/mount.<type> er 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 .
> >
> > Regards,
> > Pete
>
>
> Hey,
> Does dmesg|tail have anything relevant?
> Do you have the nfs-common package installed?
>
> cheers,
> Owen.
>
>

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

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.

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

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

On Mon, Apr 21, 2008 at 10:06:38PM +1000, Owen Townend <owen.townend@gmail.com> 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org