I would also try it without the /zones mountpoint. Putting the zone root dir on 
an alternate mountpoint caused problems for us. Try creating /datastore/zones 
for a zone root home, or just make the zones in  /datastore

Solaris seems to get very easily confused when zone root is anything out of the 
ordinary ( and it really bites you at patch time!)



On Dec 7, 2011, at 9:50 PM, Ian Collins <i...@ianshome.com> wrote:

> On 12/ 7/11 05:12 AM, Mark Creamer wrote:
>> I'm running OI 151a. I'm trying to create a zone for the first time, and am 
>> getting an error about zfs. I'm logged in as me, then su - to root before 
>> running these commands.
>> 
>> I have a pool called datastore, mounted at /datastore
>> 
>> Per the wiki document http://wiki.openindiana.org/oi/Building+in+zones, I 
>> first created the zfs file system (note that the command syntax in the 
>> document appears to be wrong, so I did the options I wanted separately):
>> 
>> zfs create datastore/zones
>> zfs set compression=on datastore/zones
>> zfs set mountpoint=/zones datastore/zones
>> 
>> zfs list shows:
>> 
>> NAME                         USED  AVAIL  REFER  MOUNTPOINT
>> datastore                   28.5M  7.13T  57.9K  /datastore
>> datastore/dbdata            28.1M  7.13T  28.1M  /datastore/dbdata
>> datastore/zones             55.9K  7.13T  55.9K  /zones
>> rpool                       27.6G   201G    45K  /rpool
>> rpool/ROOT                  2.89G   201G    31K  legacy
>> rpool/ROOT/openindiana      2.89G   201G  2.86G  /
>> rpool/dump                  12.0G   201G  12.0G  -
>> rpool/export                5.53M   201G    32K  /export
>> rpool/export/home           5.50M   201G    32K  /export/home
>> rpool/export/home/mcreamer  5.47M   201G  5.47M  /export/home/mcreamer
>> rpool/swap                  12.8G   213G   137M  -
>> 
>> Then I went about creating the zone:
>> 
>> zonecfg -z zonemaster
>> create
>> set autoboot=true
>> set zonepath=/zones/zonemaster
>> set ip-type=exclusive
>> add net
>> set physical=vnic0
>> end
>> exit
>> 
>> That all goes fine, then...
>> 
>> zoneadm -z zonemaster install
>> 
>> which returns...
>> 
>> ERROR: the zonepath must be a ZFS dataset.
>> The parent directory of the zonepath must be a ZFS dataset so that the
>> zonepath ZFS dataset can be created properly.
>> 
> That's odd, it should have worked.
> 
>> Since the zfs dataset datastore/zones is created, I don't understand what 
>> the error is trying to get me to do. Do I have to do:
>> 
>> zfs create datastore/zones/zonemaster
>> 
>> before I can create a zone in that path? That's not in the documentation, so 
>> I didn't want to do anything until someone can point out my error for me. 
>> Thanks for your help!
>> 
> You shouldn't have to, but it won't do any harm.
> 
> If you don't get any further, try zones-discuss.
> 
> -- 
> Ian.
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to