Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?
On 4/12/06, Darren J Moffat [EMAIL PROTECTED] wrote: So why not have /export/zfs_0/ /export/zfs_0/jumpstart /export/zfs_0/jumpstart/s10 /export/zfs_0/jumpstart/s10/SXCRb35 all as separate ZFS filesystems, they are cheap after all :-) It is still a bug which should be fixed. The requirement that only the base of a ZFS file system can be shared is a serious limitation which will hamper or even prevent deployment of ZFS at large sites. Simplified example: Someone may want to set up shares temporarily in a sub directory and the requirement to create an extra ZFS file system for that is a overkill, if not even a risk for production usage (I consider changes in a file system setup as a far higher risk than letting people share their data via NFS). Holger ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [zfs-discuss] Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?
On Mon, Apr 17, 2006 at 09:41:21PM +0200, Holger Berger wrote: It is still a bug which should be fixed. The requirement that only the base of a ZFS file system can be shared is a serious limitation which will hamper or even prevent deployment of ZFS at large sites. I haven't quite grokked the original thread completely, but the above statement isn't true. You can _always_ use /etc/dfs/dfstab to share whatever directories you want. The zfs set sharenfs=XXX syntax is just a simplified interface for managing shares, and has the beneficial side effect that such options are kept with your data (in the case of import/export, for example). There will always be things you may want to do (such as sharing it under a different name, or sharing subdirectories of a filesystem) which will exceed the capabilities of this simplified interface. Hope that helps, - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?
Dennis Clarke wrote: What the heck is that /export/zfs_0 is already shared. ?? No its not. So I setup the share manually in /etc/dfs/dfstab thus : # vi /etc/dfs/dfstab /etc/dfs/dfstab 1 lines, 97 characters share -F nfs -o ro=isis,root=isis -d jumpstart /export/zfs_0/jumpstart/s10/SXCRb35 So why did you do that rather than what it suggested you should do which is: # zfs set sharenfs=ro=isis,root=isis zfs_0 -- Darren J Moffat ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] However, the zfs file system /export/zfs_0 must be shared ?? What ?
On Wed, 2006-04-12 at 14:01, Dennis Clarke wrote: I like to perform little experiments. Its my nature. ... So I wondered to myself .. just how small a footprint can SXCR have? I know that Eric Bootilier did some interesting work with the reduced core install cluster and I was thinking of starting there and then ripping out packages until the system fell over or became just barely useable. I spent some time on this too, at about the same time Eric was doing his stuff. I got production servers down to 74 packages in S10 - and you could slash that quite a bit further if you don't mind losing functionality. http://www.petertribble.co.uk/Solaris/miniinstall.html -- -Peter Tribble L.I.S., University of Hertfordshire - http://www.herts.ac.uk/ http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
