Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Share ZFS file system read/write to root

1,745 views
Skip to first unread message

Dave

unread,
Jun 25, 2009, 12:04:56 PM6/25/09
to
I'm trying to share a NFS file system from a server 'disk' to a client 't2'

On the server

root@disk:~# zfs set sharenfs='rw=128.208.128.194,root=128.208.128.194'
tank/Solaris-SPARC

root@disk:~# zfs share tank/Solaris-SPARC


On the client, I can't seem to sort out the options to make the file
system read/writable to root.

root@t2 # mount -F nfs disk:/tank/Solaris-SPARC /usr/local/tmp
nfs mount: mount: /usr/local/tmp: Permission denied


I thought the option rw=root' had to be given, though I admin I can't
see that in the man page. Anyway, it does not work.

root@t2 # mount -F nfs -o rw=root disk:/tank/Solaris-SPARC /usr/local/tmp
nfs mount: mount: /usr/local/tmp: Permission denied


If I don't set the option on the server to make it writable to root,
then the file system will mount on the client ok. But as soon as I have
set it to be writable to root, so I can't mount it.

Any ideas?


--
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange' take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.

cindy

unread,
Jun 25, 2009, 12:30:37 PM6/25/09
to

Hi Dave,

I haven't had a chance to reproduce this problem, but I think it might
be an underlying permission problem on the /usr/local/tmp mount point.

Could you try mounting this file system on the client on something
like
/mnt? If it mounts on /mnt, then you need to fix the permission
problem
on /usr/local/tmp.

Cindy

Richard B. Gilbert

unread,
Jun 25, 2009, 1:05:13 PM6/25/09
to
Dave wrote:
> I'm trying to share a NFS file system from a server 'disk' to a client 't2'
>
<BIG SNIP>

>I respectfully request that this message is not archived by companies
>as unscrupulous as 'Experts Exchange' . In case you are unaware,
<snip>

It should be sufficient to add your Copyright notice!

I they then use what you wrote without your permission, you can sue them
and probably win a substantial monetary judgement!

Copyright 2009 Richard B. Gilbert

Oscar del Rio

unread,
Jun 25, 2009, 1:35:53 PM6/25/09
to
Dave wrote:
> I'm trying to share a NFS file system from a server 'disk' to a client 't2'
>
> On the server
>
> root@disk:~# zfs set sharenfs='rw=128.208.128.194,root=128.208.128.194'

ISTR that the (legacy) NFS server checks for the hostname or FQDN and
not the IP address; it might be the same with zfs sharing (?). Try
using the hostname or FQDN, or the "network" @ syntax (see "man share_nfs")

rw=@128.208.128.194/32,root=@128.208.128.194/32

Dave

unread,
Jun 25, 2009, 3:12:21 PM6/25/09
to

Hi Cindy,

I already tried that, and it did not mount. I had in fact made the
permissions on /usr/local/tmp 777, as I thought anything else when you
mounted a file system would always be a limitation that you can't easily
control.

Dave

unread,
Jun 25, 2009, 3:13:21 PM6/25/09
to


Thank you, that worked. I'd already tried the host names, which are in
/etc/inet/hosts, so i don't know why it did not work. But your
suggestion above did work. Thank you.

Darren Dunham

unread,
Jun 29, 2009, 6:34:09 PM6/29/09
to
Dave <f...@coo.com> wrote:
> Thank you, that worked. I'd already tried the host names, which are in
> /etc/inet/hosts, so i don't know why it did not work. But your
> suggestion above did work. Thank you.

Are you using DNS? What matters is the reverse lookup. Mountd will do
a reverse lookup on the IP and try to match the result to the access
list. If the hostname lookup returns a "long" name, that will not match
a short name.

rw=foo will fail to match if the IP resolves to foo.company.com.

--
Darren

0 new messages