[indiana-discuss] How much space is actually needed for image-update ?
Lubos Kosco
Lubos.Kosco at Sun.COM
Wed Nov 5 10:23:34 PST 2008
Hmm, put there 1024MB of RAM and ended up with:
Reading Existing Index 9/9
Indexing Packages 567/567
pkg: A system error [Errno 12] Not enough space was caught executing
/sbin/bootadm update-archive -R /tmp/tmpIKW5Mj
A clone of opensolaris-1 exists and has been updated and activated. On
next boot the Boot Environment opensolaris-3 will be mounted on '/'.
Reboot when ready to switch to this updated BE.
---------------------------------------------------------------------------
NOTE: Please review release notes posted at:
http://opensolaris.org/os/project/indiana/resources/rn3/
---------------------------------------------------------------------------
So it seems instead of swap I run out of disk space:
-bash-3.2# df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/opensolaris-1
7.5G 3.7G 444M 90% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 1.0G 300K 1.0G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
4.1G 3.7G 444M 90% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
swap 1.0G 68K 1.0G 1% /tmp
swap 1.0G 40K 1.0G 1% /var/run
rpool/ROOT/opensolaris-1/opt
7.5G 3.6M 444M 1% /opt
rpool/export 7.5G 19K 444M 1% /export
rpool/export/home 7.5G 22M 444M 5% /export/home
rpool 7.5G 62K 444M 1% /rpool
rpool/ROOT 7.5G 18K 444M 1% /rpool/ROOT
# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
opensolaris - - 60.08M static 2008-09-23 11:38
opensolaris-1 N / 23.48M static 2008-09-23 13:33
opensolaris-2 - - 200.08M static 2008-11-05 02:54
opensolaris-3 R - 6.85G static 2008-11-05 19:00
So it seems I am back to my original Q ...
What are the expectations on memory(&disk) space when you plan to do a
pkg image-update ?
Till now my limits were at 3GB of disk and 512MB of ram ... this however
is not true anymore.
Would it make sense to post into image update notes requirements for
free disk/memory to perform the update flawlessly ?
I know it would be hard to make pkg image-update to check for those
limits before doing the image-update, so I don't want to start a talk in
that way, simple setting expectations on minimum free space into release
notes would be more than enough ;)
Cheers & tia
Lubos
Brock Pytlik wrote:
> I believe you're hitting bug 4391:
> http://defect.opensolaris.org/bz/show_bug.cgi?id=4391
>
> I think the general solution is to try to bump your swap space or wait
> to build 101 comes out where we believe we've shrunk our memory footprint.
>
> Brock
>
> Lubos Kosco wrote:
>
>> Hi guys
>> getting this after # pkg image-update -v from b98 to latest :
>>
>> PHASE ACTIONS
>> Removal Phase 11547/11547
>> Install Phase 13652/13864 Action install failed for 'amd_iommu' (pkg:/SUNWckr):
>> OSError: [Errno 12] Not enough space
>> The running system has not been modified. Modifications were only made to a clone of the running system. This clone is mounted at /tmp/tmpDjP6Ks should you wish to inspect it.
>>
>> pkg: An unexpected error happened during image-update: [Errno 12] Not enough space
>> Traceback (most recent call last):
>> File "/usr/bin/pkg", line 2122, in ?
>> __ret = main_func()
>> File "/usr/bin/pkg", line 2069, in main_func
>> return image_update(mydir, pargs)
>> File "/usr/bin/pkg", line 605, in image_update
>> api_inst.execute_plan()
>> File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 467, in execute_plan
>> self.img.imageplan.execute()
>> File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 701, in execute
>> p.execute_install(src, dest)
>> File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 278, in execute_install
>> dest.install(self, src)
>> File "/usr/lib/python2.4/vendor-packages/pkg/actions/driver.py", line 144, in install
>> {"name": self.attrs["name"]})
>> File "/usr/lib/python2.4/vendor-packages/pkg/actions/driver.py", line 65, in __call
>> stderr = subprocess.STDOUT)
>> File "/usr/lib/python2.4/subprocess.py", line 543, in __init__
>> errread, errwrite)
>> File "/usr/lib/python2.4/subprocess.py", line 902, in _execute_child
>> self.pid = os.fork()
>> OSError: [Errno 12] Not enough space
>>
>>
>> pkg: This is an internal error. Please let the developers know about this
>> problem by filing a bug at http://defect.opensolaris.org and including the
>> above traceback and this message. The version of pkg(5) is '71eab3488987'.
>>
>>
>>
>>
>> -bash-3.2$ df -h
>> Filesystem size used avail capacity Mounted on
>> rpool/ROOT/opensolaris-1
>> 7.5G 3.7G 1.8G 67% /
>> /devices 0K 0K 0K 0% /devices
>> /dev 0K 0K 0K 0% /dev
>> ctfs 0K 0K 0K 0% /system/contract
>> proc 0K 0K 0K 0% /proc
>> mnttab 0K 0K 0K 0% /etc/mnttab
>> swap 691M 308K 691M 1% /etc/svc/volatile
>> objfs 0K 0K 0K 0% /system/object
>> sharefs 0K 0K 0K 0% /etc/dfs/sharetab
>> /usr/lib/libc/libc_hwcap1.so.1
>> 5.5G 3.7G 1.8G 67% /lib/libc.so.1
>> fd 0K 0K 0K 0% /dev/fd
>> swap 691M 4K 691M 1% /tmp
>> swap 691M 44K 691M 1% /var/run
>> rpool/ROOT/opensolaris-1/opt
>> 7.5G 3.6M 1.8G 1% /opt
>> rpool/export 7.5G 19K 1.8G 1% /export
>> rpool/export/home 7.5G 22M 1.8G 2% /export/home
>> rpool 7.5G 59K 1.8G 1% /rpool
>> rpool/ROOT 7.5G 18K 1.8G 1% /rpool/ROOT
>> rpool/ROOT/opensolaris-2
>> 7.5G 3.8G 1.8G 68% /tmp/tmpDjP6Ks
>> rpool/ROOT/opensolaris-2/opt
>> 7.5G 3.6M 1.8G 1% /tmp/tmpDjP6Ks/opt
>> -bash-3.2$
>> -bash-3.2$
>> -bash-3.2$ df -h /tmp/tmpDjP6Ks
>> Filesystem size used avail capacity Mounted on
>> rpool/ROOT/opensolaris-2
>> 7.5G 3.8G 1.8G 68% /tmp/tmpDjP6Ks
>>
>>
>>
>> Not sure if this is a bug or just my (virtual) disk too small
>> it says file a bug, but I'll do it only once someone confirms this is a bug indeed
>> can someone advise(evaluate) ?
>>
>> Cheers
>> Lubos
>>
>>
>
>
More information about the indiana-discuss
mailing list