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 ca
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
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 any
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, ba
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
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 "unsub
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,
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 protoc
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 d
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 err
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
[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 mig
12 matches
Mail list logo
