Hi all,
from time to time I am upgrading my /hipster image. I have tried that
this morning too...
$ uname -rosv
SunOS 5.11 illumos-4f4d460 Solaris
$ pfexec pkg refresh --full
$ pfexec pkg update -v --be-name oi151_181hipster_20140130
Creating Plan (Checking for conflicting actions): -
pkg
If a share was mounted on the client and you change the underlying NFS
version on the server then you will need to get the client to unmount all
shares from the server before they can see the version 3 shares ... is this
the case in your instance?
Are your shares auto-mounted? if so it depends on
From: Jonathan Adams [mailto:t12nsloo...@gmail.com]
Sent: Thursday, January 30, 2014 4:06 AM
If a share was mounted on the client and you change the underlying NFS
version on the server then you will need to get the client to unmount all
shares from the server before they can see the
On Thu, Jan 30, 2014 at 02:57:14PM +, Edward Ned Harvey (openindiana) wrote:
I wondered if maybe I have firewall enabled on the server. So I used nc
and telnet from the client to confirm the port is open. (111 and 2049).
No problem.
In addition to ports 111 and 2049 you need a port for
to test if it is a permissions problem, can you just set sharenfs=on? and
then try to access from the other machines?
On 30 January 2014 14:57, Edward Ned Harvey (openindiana)
openindi...@nedharvey.com wrote:
From: Jonathan Adams [mailto:t12nsloo...@gmail.com]
Sent: Thursday, January 30,
From: Jonathan Adams [mailto:t12nsloo...@gmail.com]
to test if it is a permissions problem, can you just set sharenfs=on? and
then try to access from the other machines?
Thanks for the help everyone. I decided to take it a step further than that:
On both the 151a7 (homer) and 151a9 (marge)
From: Edward Ned Harvey (openindiana)
It *appears* that NFSv4 is fine in both 151a7 and 151a9.
It *appears* that NFSv3 is broken in 151a9. Which was unfortunately, necessary
to support ESXi client and Ubuntu 10.04 client.
___
OpenIndiana-discuss
I ran into a similar issue on OmniOS 151008j recently.
When I ran 'rpcinfo -p {nfs_server}' it returned access denied.
Restarting the rpc service fixed it:
svcadm restart svc:/network/rpc/bind:default
I don't know what put the server in that state, but it's happened only once
on the heavily
On 01/30/14 09:14 AM, Predrag Zecevic [Unix Systems Administrator] wrote:
Hi all,
from time to time I am upgrading my /hipster image. I have tried that
this morning too...
$ uname -rosv
SunOS 5.11 illumos-4f4d460 Solaris
$ pfexec pkg refresh --full
$ pfexec pkg update -v --be-name
