mount fails

On all my Linux boxen, I use the same exports syntax. e.g.:

/home 192.168.1.0/255.255.255.0(ro,root_squash,sync)


When on OS/2 I do:

mount -gid550 -uid500 X: 192.168.1.2:/home

I get success, because 192.168.1.2 is my SuSE 8.2 box. However, on all
my Linux boxen with newer distros, such as SuSE 9.1, I get failure, such
as:

IBM NFS of OS/2
MOUNT version 3.99
Release: m17

MOUNT: 192.168.1.2:/pub

NFSU1003: Drive X: could not be attached to the filesystem
NFSU1028: Error creating NLM client

Use the following command to show the export list of the server:
showexp 192.168.1.2
Note: The VM NFS server does not support this command

showexp 192.168.1.2 returns:

Export list for 192.168.1.2:
/home 192.168.1.0/255.255.255.0

What do I need to do differently to achieve success using mount with
newer distros?
--
"Congress shall make no law respecting an establishment of religion or
prohibiting the free exercise thereof..." U.S. Constitution, Amendment 1

Team OS/2 ** Reg. Linux User #211409

Felix Miata *** http://members.ij.net/mrmazda/


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

Felix Miata wrote:
> MOUNT: 192.168.1.2:/pub
>
> NFSU1003: Drive X: could not be attached to the filesystem
> NFSU1028: Error creating NLM client
>
Did you ever get the lock manager ("nlockmgr") loaded on your newer
linux system?


--
jmm dash list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)

with this:

> /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)

this will work:

> mount -gid550 -uid500 X: 192.168.1.2:/home

and this won't:

> MOUNT: 192.168.1.2:/pub

try mounting /home instead of /pub

Frank Giessler wrote:

> Felix Miata wrote:

> > On all my Linux boxen, I use the same exports syntax. e.g.:

> > /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)

> > What do I need to do differently to achieve success using mount wit
> > newer distros?

> Try:
> /home/ 192.168.1.0/255.255.255.0(ro,root_squash,sync)

> Hope this helps,

Doesn't look like it does.
--
"Congress shall make no law respecting an establishment of religion or
prohibiting the free exercise thereof..." U.S. Constitution, Amendment 1

Team OS/2 ** Reg. Linux User #211409

Felix Miata *** http://members.ij.net/mrmazda/


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

jmm-list-gn wrote:

> Felix Miata wrote:

> > MOUNT: 192.168.1.2:/pub
> >
> > NFSU1003: Drive X: could not be attached to the filesystem
> > NFSU1028: Error creating NLM client

> Did you ever get the lock manager ("nlockmgr") loaded on your newer
> linux system?

No. Never figured out what package is supposed to provide that facility.
--
"Congress shall make no law respecting an establishment of religion or
prohibiting the free exercise thereof..." U.S. Constitution, Amendment 1

Team OS/2 ** Reg. Linux User #211409

Felix Miata *** http://members.ij.net/mrmazda/


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

/dev/null wrote:

> with this:

> > /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)

> this will work:

> > mount -gid550 -uid500 X: 192.168.1.2:/home

This is what happens when I do that:

IBM NFS for OS/2
MOUNT Version 3.99
Release: m17

MOUNT: 192.168.1.90:/home

NFSU1003: Drive X: could not be attached to the file system.
NFSU1028: Error creating NLM client.

Use the following command to show the export list of the server:
showexp 192.168.0.90
Note: The VM NFS server does not support this command.
--
"Congress shall make no law respecting an establishment of religion or
prohibiting the free exercise thereof..." U.S. Constitution, Amendment 1

Team OS/2 ** Reg. Linux User #211409

Felix Miata *** http://members.ij.net/mrmazda/


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---

"Felix Miata" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> /dev/null wrote:
>
> > with this:
>
> > > /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)
>
> > this will work:
>
> > > mount -gid550 -uid500 X: 192.168.1.2:/home
>
> This is what happens when I do that:
>
> IBM NFS for OS/2
> MOUNT Version 3.99
> Release: m17
>
> MOUNT: 192.168.1.90:/home

ok. So why on the one that works are you telling it to mount 192.168.1.2
and the one that fails you are telling it to mount 192.168.1.90?

What's the IP of the box sharing the mount?

Felix Miata writes:

> On all my Linux boxen, I use the same exports syntax. e.g.:
>
> /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)
>
>
> When on OS/2 I do:
>
> mount -gid550 -uid500 X: 192.168.1.2:/home
>
> I get success, because 192.168.1.2 is my SuSE 8.2 box. However, on all
> my Linux boxen with newer distros, such as SuSE 9.1, I get failure, such
> as:
>
> IBM NFS of OS/2
> MOUNT version 3.99
> Release: m17
>
> MOUNT: 192.168.1.2:/pub
>
> NFSU1003: Drive X: could not be attached to the filesystem
> NFSU1028: Error creating NLM client
>
> Use the following command to show the export list of the server:
> showexp 192.168.1.2
> Note: The VM NFS server does not support this command
>
> showexp 192.168.1.2 returns:
>
> Export list for 192.168.1.2:
> /home 192.168.1.0/255.255.255.0
>
> What do I need to do differently to achieve success using mount with
> newer distros?

I've not had any trouble mounting directories on my Warp 4.52 box that
were exported from a Solaris box, but I get the same error messages
that you're getting when trying to mount directories on my Warp 4.52
box that were exported from a Warp 4.0 box. The reverse works, namely
my Warp 4.0 box can mount a drive exported from the Warp 4.52 box.
Can anybody explain this behavior?

Felix,

What software do I need to do this??
The Mount command isn't recognized on my system.

TIA
Rich Wonneberger
(E-Mail Removed)


Felix Miata wrote:
> On all my Linux boxen, I use the same exports syntax. e.g.:
>
> /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)
>
>
> When on OS/2 I do:
>
> mount -gid550 -uid500 X: 192.168.1.2:/home
>

On Sat, 27 Nov 2004 00:45:11 -0500, Felix Miata
<(E-Mail Removed)> wrote:

>/dev/null wrote:
>
>> with this:
>
>> > /home 192.168.1.0/255.255.255.0(ro,root_squash,sync)
>
>> this will work:
>
>> > mount -gid550 -uid500 X: 192.168.1.2:/home
>
>This is what happens when I do that:
>
>IBM NFS for OS/2
>MOUNT Version 3.99
>Release: m17
>
>MOUNT: 192.168.1.90:/home
>
>NFSU1003: Drive X: could not be attached to the file system.
>NFSU1028: Error creating NLM client.
>
>Use the following command to show the export list of the server:
>showexp 192.168.0.90
>Note: The VM NFS server does not support this command.

I think you have a different problem. Showexp works fine. I'm
beginning to suspect you've managed to corrupt part of your OS/2
installation. I haven't been able to reproduce any of your errors.

Mike-

--
If you can keep your head while those around you are losing theirs...
You may have a great career as a network administrator ahead!
--
Please note - Due to the intense volume of spam, we have installed
site-wide spam filters at catherders.com. If email from you bounces,
try non-HTML, non-encoded, non-attachments,