Hi this question is along the lines of datasets and number of zfs file systems available per zone. I suspect I am missing something obvious. We have added 8 datasets to one non-global Zone. While logged in and doing a ZFS list in that zone, I am only able to see the first 7 available ZFS file systems. The 8th one is not available; however a zonecfg:info from the Global Zone shows it is indeed added to the zone. How do I go about making a Zone see more (eg mounting) more than 7 ZFS file systems? Note my datasets all are originating from one pool sitting on top of a StorEdge 3320 RAID. Regards Ken
Hi. Can you post zonecfg -z XXXX export and zfs list in that XXX zone? This message posted from opensolaris.org
Hi Robert -- Here are the outputs. I cannot seem to see the last isapps dataset via zfs list. The non-global zone will be used to host a 10G Oracle. //** From the global zone ** //** Pool is named telecom # zonecfg -z production export create -b set zonepath=/zones/production set autoboot=true add inherit-pkg-dir set dir=/lib end add inherit-pkg-dir set dir=/platform end add inherit-pkg-dir set dir=/sbin end add inherit-pkg-dir set dir=/usr end add dataset set name=telecom/oracle/production/backup end add dataset set name=telecom/oracle/production/logs end add dataset set name=telecom/oracle/production/oraapp end add dataset set name=telecom/oracle/production/oradata end add dataset set name=telecom/oracle/production/oradmp end add dataset set name=telecom/oracle/production/oramirror1 end add dataset set name=telecom/oracle/production/oramirror2 end add dataset set name=telecom/oracle/production/isapps end //**from my non-global zone called production /** I have used zfs set mountpoint= to adjust the mounts where i need them /** Telecom and telecom/oracle remain accessible only to the global as desired # zfs list NAME USED AVAIL REFER MOUNTPOINT telecom 799K 669G 51K /telecom telecom/oracle 490K 669G 49K /telecom/oracle telecom/oracle/production 441K 669G 49K /telecom/oracle/production telecom/oracle/production/backup 49K 20.0G 49K /backup telecom/oracle/production/logs 49K 5.00G 49K /logs telecom/oracle/production/oraapp 49K 15.0G 49K /oraapp telecom/oracle/production/oradata 49K 20.0G 49K /oradata telecom/oracle/production/oradmp 49K 2.00G 49K /oradmp telecom/oracle/production/oramirror1 49K 5.00G 49K /oramirror1 telecom/oracle/production/oramirror2 49K 5.00G 49K /oramirror2 If I do a zfs mount in either the global zone or the non-global zone, I do not see telecom/oracle/production/isapps. The zoned flag is set. Regards and Thanks for your help Ken University of New Hampshire On Wed, 2006-09-06 at 08:36, Robert Milkowski wrote:> Hi. > > Can you post zonecfg -z XXXX export and zfs list in that XXX zone? > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Well, that''s interesting. Looks like some limit/bug here. However whatever the limit is have you considered to add dataset into a zone? That way you can actually create new file systems as needed inside a zone without changing zone configuration, etc. You can also utilize snapshots, clones inside a zone. That''s what I did. That way DB admins can create file systems, snapshots, etc. add dataset set name=pool/dataset end This message posted from opensolaris.org
Hmmm. I thought I was doing this via zonecfg -z production, which zonecfg is run from the global zone. add dataset set name=telecom/oracle/production/oraapp end ... repeat add dataset set name=telecom/oracle/production/isapps end commit exit The zone took all the datasets (shown in the earlier export), yet the zone only reveals/mounts the first seven when it runs. Are you suggesting that I not get too granular with datasets and use a higher level one versus several? thanks ken On Wed, 2006-09-06 at 09:21, Robert Milkowski wrote:> Well, that''s interesting. Looks like some limit/bug here. However whatever the limit is have you considered to add dataset into a zone? That way you can actually create new file systems as needed inside a zone without changing zone configuration, etc. You can also utilize snapshots, clones inside a zone. That''s what I did. That way DB admins can create file systems, snapshots, etc. > > add dataset > set name=pool/dataset > end > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Hmmm. I thought I was doing this via zonecfg -z production, which zonecfg is run from the global zone. add dataset set name=telecom/oracle/production/oraapp end ... repeat add dataset set name=telecom/oracle/production/isapps end commit exit The zone took all the datasets (shown in the earlier export), yet the zone only reveals/mounts the first seven when it runs. Are you suggesting that I not get too granular with datasets and use a higher level one versus several? thanks ken On Wed, 2006-09-06 at 09:21, Robert Milkowski wrote:> Well, that''s interesting. Looks like some limit/bug here. However whatever the limit is have you considered to add dataset into a zone? That way you can actually create new file systems as needed inside a zone without changing zone configuration, etc. You can also utilize snapshots, clones inside a zone. That''s what I did. That way DB admins can create file systems, snapshots, etc. > > add dataset > set name=pool/dataset > end > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On 06/09/06, Kenneth Mikelinich <ken.mikelinich at unh.edu> wrote:> Are you suggesting that I not get too granular with datasets and use a > higher level one versus several?I tihnk what he''s saying is you should only have to delegate one dataset (telecom/oracle/production, for example), and all the ''child'' datasets can be created/administered/snapshotted etc. in the non -global zone itself. -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
Thanks. I will try this out Ken Mikelinich Computer Operations Manager Telecommunications and Client Services University of New Hampshire 603.862.4220 -----Original Message----- From: Dick Davies [mailto:rasputnik at gmail.com] Sent: Wednesday, September 06, 2006 9:54 AM To: Mikelinich, Ken Cc: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] Re: Re: datasets,zones and mounts On 06/09/06, Kenneth Mikelinich <ken.mikelinich at unh.edu> wrote:> Are you suggesting that I not get too granular with datasets and use a > higher level one versus several?I tihnk what he''s saying is you should only have to delegate one dataset (telecom/oracle/production, for example), and all the ''child'' datasets can be created/administered/snapshotted etc. in the non -global zone itself. -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
On Wed, Sep 06, 2006 at 09:01:00AM -0400, Kenneth Mikelinich wrote:> Hi Robert -- Here are the outputs. I cannot seem to see the last isapps > dataset via zfs list. The non-global zone will be used to host a 10G > Oracle.Yes, this is definitely a bug somewhere. I''ll try to reproduce this on a test machine and see what''s going on. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
Robert Milkowski
2006-Sep-06 16:11 UTC
[zfs-discuss] Re: Re: Re: datasets,zones and mounts
No, remove all other datasets from zone config and just put: add dataset set name=telecom/oracle/production end and that''s it. That way you will see all filesystem beneath tyelecom/oracle/production. Additionally in a zone production you will be able to create more file systems inside without changing zone configuration. Additionally snapshots and clones will work inside zone. You are not only not loosing granulity you are adding flexibity that way. Sorry for not being clear. This message posted from opensolaris.org