Hi Alexander.
Please note that the DC manifest accepts a non-negative padding value,
so there is no need to modify the scripts to enlarge the bootroot.
In XML, the field is
distribution/img_params/output_image/bootroot/size_pad_mb
Thanks,
Jack
On 10/02/09 09:21, Alexander Eremin wrote:
> On Fri, 2009-10-02 at 12:04 +0000, Alexander Eremin wrote:
>
>> Hi all,
>> Just played with Bug 6361 - Calculation of Sparc boot archive doesn't
>> count with dcfs compression.
>> If change overhead for sparc in bootroot_archive.py to ~1.062 I've got
>> a 114mb boot_archive with 23mb free space.
>> That's minimum, in other case I've got cpio errors in br-arch step.
>> If I take usual root_archive script for DC /bootroot directory and add
>> to it line:
>> size=$(($size +
>> 20480))
>>
>>
>> before
>>
>>
>> /usr/sbin/mkfile ${size}k "$TMR"
>> ...
>>
>> I've got a 90mb boot_archive with 13mb free space.
>> Looks like DC python scripts produces bigger size for boot_archive
>> than usual root_archive cmd.
>>
>>
> On my sparc for bootroot directory ('du' there give me 109mb but I know
> that on zfs the disk usage is less than the sum of the file sizes)
> bootroot_archive.py calculate boot_root_size as 109mb before
> ti_create_target, tunefs and compression,
> root_archive - 68mb before mkfile, lofiadm,newfs and compression
> processes.
> root_archive give me smaller miniroot.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20091002/15c3b4c8/attachment.html>
