search for: sharenf

I noticed an oddity on my 2008.05 box today. Created a new zfs file system that I was planning to nfs share out to an old FreeBSD box, after I put sharenfs=on for it, I noticed there was a bunch of others shared too: -bash-3.2# dfshares -F nfs RESOURCE SERVER ACCESS TRANSPORT reaver:/store/movies reaver - - reaver:/export reaver - - reaver:/stor...

x86 snv 108 I have a pool with around 5300 file systems called home. I can do: zfs set sharenfs=on home however zfs set sharenfs="sec=krb5,rw" home complains: cannot set property for ''home'': ''sharenfs'' cannot be set to invalid options I feel I must be overlooking something elementary. Thanks, Alastair -------------- next part ------------...

...one large zfs pool; -bash-3.00# df -hl bigpool 16T 1.5T 15T 10% /export that I am starting to populate. Should I simply share /export, or should I separately share the individual dirs in /export like the old dfstab did? I am assuming that one single command; # zfs set sharenfs=ro bigpool would share /export as a read-only NFS point? Opinions/comments/tutoring? Thanks, Neal

...ey are mounted on the clients using automount (from a NIS map). But: only the root exported filesystem shows any contents on the clients. Any sub-directories it has are fine, but any sub-filesystems are empty. ie. NIS map auto.stuff contains "stuff server:/stuff/images" server% zfs get sharenfs stuff/images sharenfs rw=netgroup stuff/images/small sharenfs inherited from stuff/images stuff/images/large sharenfs rw=netgroup client% ls /data/stuff/images large/ small/ other files... But /data/stuff/images/large is empty, as is small/ If I move the files out of the ZFS sub-filesy...

...http://www.opensolaris.org/jive/thread.jspa?threadID=108316&tstart=30 and to obviate to the problem I''m using legacy mounts. Now the system boot without problems, but nfs server doesn''t start because couldn''t find any share. So I''ve disabled nfs with zfs set sharenfs=off on my zfs filesystems and tried to use the share command. The filesystem are correctly mounted at boot, but if I try to configure nfs share with: share -F nfs /pathname I get: Could not share: /pathname: system error I''m very new to solaris... so please bear with me^^ Thanks. -- T...

...) running OpenSolaris 2008.05 pkg upgraded to snv_91 with ~3200 filesystems (and ~27429 datasets, including snapshots). I''ve been encountering some pretty big slow-downs on this system when running certain zfs commands. The one causing me the most pain at the moment is setting the "sharenfs" property on a filesystem takes a little under 7 minutes per operation. Tracing it, I see that it''s making a huge number of ioctl calls: $ truss -f -c zfs set sharenfs=on zpool/test syscall seconds calls errors _exit .000 1 read...

...ve just installed Solaris and have added a 3x500GB raidz drive array. I am able to use this pool (''tank'') successfully locally, but when I try to share it remotely, I can only read, I cannot execute or write. I didn''t do anything other than the default ''zfs set sharenfs=on tank''... how can I get it so that any allowed user can access the pool read/write through nfs? Here is some relevant information: root at mosasaur:/# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank 1.36T 46.1G 1.31T 3%...

...ve just installed Solaris and have added a 3x500GB raidz drive array. I am able to use this pool (''tank'') successfully locally, but when I try to share it remotely, I can only read, I cannot execute or write. I didn''t do anything other than the default ''zfs set sharenfs=on tank''... how can I get it so that any allowed user can access the pool read/write through nfs? Here is some relevant information: root at mosasaur:/# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank 1.36T 46.1G 1.31T 3%...

I started sharing out zfs filesystems via NFS last week using sharenfs=on. That seems to work fine until I reboot. Turned out the NFS server wasn''t enabled - I had to enable nfs/server, nfs/lockmgr and nfs/status manually. This is a stock SXCR b49 (ZFS root) install - don''t think I''d changed anything much. Shouldn''t a ZFS share be...

Author: lling Repository: /hg/zfs-crypto/gate Revision: 470ed1fa8c0b5104bdf6c9dcdb194eb4781ddc19 Log message: 6345875 The zfs "sharenfs" option fails after an alternate-root mount, until reboot Files: update: usr/src/cmd/zpool/zpool_dataset.c update: usr/src/cmd/zpool/zpool_main.c update: usr/src/cmd/zpool/zpool_util.h

...is because it is so tuneable -- compression on these dirs, no atime on those -- so flexible. (But please let me know if I''m not on the right track) But here is the problem I''ve run into -- nfs exporting. In the examples they make tank/home/{ann,bob,etc}. Now if I "zfs set sharenfs=on tank/home", that option gets inherited down and "showmount -e" gives: export list for solaristest: /tank/home (everyone) /tank/home/ann (everyone) etc... So now if I have another server mount solaristest:/tank/home, the {ann,bob,etc} dirs are there, but write...

...hares which point to the same directory. The idea is if you come in via one path, you will have read-only access and can''t delete any files, if you come in the 2nd path, then you will have read/write access. For example, create the read/write nfs share: zfs create tank/snapshots zfs set sharenfs=on tank/snapshots root at grok-zfs1:/# sharemgr show -vp default nfs=() zfs zfs/tank/snapshots nfs=() /tank/snapshots I have had some luck doing it with Samba. Any pointers to making it work with NFS? Thanks, Geoff

My system is OS 8.11, updated to dev build 105. I have two pools constructed from iscsi targets with around 5600 file-systems in each. I was able to enable NFS sharing and CIFS/SMB sharing on both pools, however, after a reboot the SMB shares comes up but the NFS server service does not and eventually times out after about 3 hours of trying. Are there any know issues with large number of NFS

...- rpool/export quota none default rpool/export reservation none default rpool/export recordsize 128K default rpool/export mountpoint /export local rpool/export sharenfs off default rpool/export checksum on default rpool/export compression off default rpool/export atime on default rpool/export devices on...

This is the first time I tried nfs with zfs. I shared the zfs filesystem with nfs, but i can''t write to the files though i mount it as read-write. This is for Solaris 10 update 4. I wonder if there is a bug? ---------------server (sdw2-2) #zfs create -o sharenfs=on data/nfstest #zfs get all data/nfstest NAME PROPERTY VALUE SOURCE data/nfstest type filesystem - data/nfstest creation Thu Jun 5 13:22 2008 - data/nfstest used 40.7K - data/nfstest available 15.4...

-bash-3.2$ zfs share tank cannot share ''tank'': share(1M) failed -bash-3.2$ how do i figure out what''s wrong? This message posted from opensolaris.org

...t/os/sles10sp2 mounted yes - zfs52/export/os/sles10sp2 quota 50G local zfs52/export/os/sles10sp2 mountpoint /export/os/sles10sp2 local zfs52/export/os/sles10sp2 sharenfs ro=@192.168.0.0/16,root=@192.168.0.0/24 inherited from zfs52/export/os zfs52/export/os/sles10sp2 checksum on default zfs52/export/os/sles10sp2 compression gzip local ... I use zfs send...

...stem: root at kronos:/ # zfs destroy -f raid/www/user-testuser cannot unshare ''raid/www/user-testuser'': /raid/www/user-testuser: not shared root at kronos:/ # zfs list | grep testuser raid/www/user-testuser 49K 150M 49K /raid/www/user-testuser root at kronos:/ # zfs set sharenfs=on raid/www/user-testuser root at kronos:/ # zfs destroy raid/www/user-testuser root at kronos:/ # ...the filesystem simply would not go away until I turned on the sharenfs toggle. Then it happily died. Thought I''d mention it. root at kronos:/ # uname -a SunOS kronos 5.10 Generi...

Starting from this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=118786&#118786 I would love to have the possibility to set an ISCSI alias when doing an shareiscsi=on on ZFS. This will greatly facilate to identify where an IQN is hosted. the ISCSI alias is defined in rfc 3721 e.g. http://www.apps.ietf.org/rfc/rfc3721.html#sec-2 and the CLI could be something like: zfs set

I have Solaris 10 U7 that is exporting ZFS filesytem. The client is Solaris 9 U7. I can mount the filesytem just fine but I am unable to write to it. showmount -e shows my mount is set for everyone. the dfstab file has option rw set. So what gives? Phillip -- This message posted from opensolaris.org