Ceri:

This is a known issue and you have to specify a size:

            <ai_device_vtoc_slices>
                <slice_action>delete</slice_action>
                <slice_number>1</slice_number>
                <slice_size>512</slice_size>
                <slice_size_units>mb</slice_size_units>
            </ai_device_vtoc_slices>



http://defect.opensolaris.org/bz/show_bug.cgi?id=7794

7794 - delete/preserve slice action in AI manifest fails if no size 
specified

The workaround is just you need to specify a size and unit #.  The size 
can be anything and it will work.


Ceri Davies wrote:
> I spoke too soon...
> 
>   <ai_device_vtoc_slices>
>               <slice_action>delete</slice_action>
>               <slice_number>7</slice_number>
>  </ai_device_vtoc_slices>
> 
> Fails on installadm
> 
> Does it need the <slice_size> ? I added slice size on the delete and the 
> installadm works now, but the problem I have it I dont know the slice 
> size I am deleting...
> 
> Mr. Ceri Davies - Staff Engineer (Software)
> Sun Microsystems - Data Management Group
> Ceri.Davies at Sun.com
> W:(303) 272-7810 (x77810)
> H:(303) 442-2795
> Typically work from home on Fridays
> 
> 
> 
> 
> On Jun 24, 2009, at 9:12 AM, William Schumann wrote:
> 
>> Ceri,
>> It sounds as if slice 0 was a preexisting slice.  AI will attempt to 
>> preserve existing slices.
>> First, delete slice 0, either manually by format(1m), or automatically 
>> by deleting it explicitly in the manifest:
>> Then you can specify slice 0 to use the entire disk explicitly. The 
>> following manifest tags will cause first the deletion, then recreation 
>> using the entire disk:
>> <ai_device_vtoc_slices>
>>   <slice_action>delete</slice_action>
>>   <slice_number>0</slice_number>
>> </ai_device_vtoc_slices>
>> <ai_device_vtoc_slices>
>>   <slice_action>create</slice_action>
>>   <slice_number>0</slice_number>
>>   <slice_size>max_size</slice_size>
>> </ai_device_vtoc_slices>
>>
>> William
>> Ceri Davies wrote:
>>> It looks like when I did my (successful!) AI install, it used the 
>>> existing ufs partition table on the disk and then used slice 0, so 
>>> only used less than half the disk.
>>>
>>> 1) Can I force AI to use the whole disk (re-partition?).  There is 
>>> obviously a catch 22 in repartitioning the root disk before I invoke 
>>> AI, so how do I do this...
>>> 2) Can I get AI to installed a mirrored rpool?
>>>
>>> Mr. Ceri Davies - Staff Engineer (Software)
>>> Sun Microsystems - Data Management Group
>>> Ceri.Davies at Sun.com
>>> W:(303) 272-7810 (x77810)
>>> H:(303) 442-2795
>>> Typically work from home on Fridays
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> caiman-discuss mailing list
>>> caiman-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
> 
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss


Reply via email to