[Caiman-team] not able to create zfs datasets during automated installation

[Rausch, Andreas]

Hi,

 

I'm not sure whether this is the correct mailing list to post a possible issue with the automated installer feature - please direct me to the

correct one if needed.

 

I've spent some time to setup an AI server for Openindiana 151a. When I try to setup a client using a XML manifest, it always fails to create

additional ZFS datasets during the installation. To me it seems that even the <zpool> and <dataset> tags in the XML manifest are not

honored by the AI client.

 

Here is a snippet of the <target> XML definition:

 

    <target>

      <target_device>

        <zpool name="rpool_os" is_root="true">

          <vdev redundancy="mirror">

            <disk>

              <disk_name name="c4t0d0" name_type="ctd"/>

            </disk>

            <disk>

              <disk_name name="c4t1d0" name_type="ctd"/>

            </disk>

          </vdev>

          <dataset>

            <filesystem name="opt" mountpoint="/opt"/>

          </dataset>

        </zpool>

      </target_device>

      <target_device>

        <swap>

          <zvol action="create" name="swap">

            <size val="2gb"/>

          </zvol>

        </swap>

      </target_device>

      <target_device>

        <dump>

          <zvol action="create" name="dump">

            <size val="1gb"/>

          </zvol>

        </dump>

      </target_device>

    </target>

 

The AI client always creates a standard ZFS root pool named rpool and an extra ZFS dataset named export (and not a root pool named "rpool_os"). 

Maybe I've made some mistakes within the XML manifest, but what I'm also wondering is that even the <size> tags in the <dump> and <swap> tags 

are not honored correctly. The above snippets should create a dump vol with a size of 1 gig and a swap vol with a size of 2 gigs. When the AI client runs, 

it creates both zvols with a size of only some megs. Only when the size values are defined as "1024" for 1 gig and "2048" for 2 gigs they 'll be created

correctly. I think the AI client assumes always megabytes for the size values and does not look to the suffixes (mb, gb).

 

Any help is highly appreciated!

 

 

 

 

Thanks in advance,

 

 

Andreas Rausch 

Atmel Automotive GmbH 
IT Operations / Design Center Dresden 
Koenigsbruecker Strasse 61 
D-01099 Dresden 

Phone:   +49 351 6523 110 
Mobile:  +49 172 6128 072 
Fax:         +49 351 6523 5110 
Mail:       andreas.rausch at atmel.com <mailto:andreas.rausch at atmel.com>  
Web:      http://www.atmel.com <http://www.atmel.com/>  

Geschäftsführung: Steven A. Laub, Stephen Cumming * Sitz der Gesellschaft: Heilbronn * Amtsgericht: Stuttgart * HRB 106594

The information contained in this e-mail message may be privileged, confidential and/or protected from unauthorized disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. Please immediately notify the sender by reply if you received this e-mail in error. Thanks for your cooperation

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/caiman-team/attachments/20120112/f46974e5/attachment.html>