[indiana-discuss] [pkg-discuss] Updating SUNWipkg? Re: Repository update: snv91

[Chris Ridd]

On 21 Jun 2008, at 22:20, Danek Duvall wrote:

> On Sat, Jun 21, 2008 at 09:55:37PM +0100, Chris Ridd wrote:
>
>>>> Installing the 0.91 version of SUNWipkg now works, and pkg image-
>>>> update is now doing its thing. Yay!
>>>
>>> Cool!
>>
>> Actually, no.
>
> Well, it got past your original problem and on to a new one.
>
> How much memory do you have?  We're pretty sure that we have some  
> memory
> issues, so if you're low on memory -- particularly with ZFS  
> crunching away
> in the background and with the VB instance -- this doesn't surprise  
> me too
> much.

The machine's got 3GB of RAM, and 2GB of swap. My 800MB VirtualBox  
instance isn't helping.

> I'd be curious to see how much memory pkg is taking up at this point,
> assuming you can reproduce the problem.

I'm just trying again while watching using prstat, and it looks like  
initially it was using 37MB of RSS for a few minutes, and then goes up  
to a steady state of 350MB while downloading everything.

In the Removal Phase, it jumps to 376MB.

Update phase: 396MB

And it has failed again at the same point. "swap -lh" was consistently  
reporting 1.2GB free through the whole procedure (2GB - Virtualbox?),  
so it isn't completely clear that it is out of memory.

>> That's a bit confusing - errno 12 is ENOMEM, not ENOSPC.
>
> That's the standard message for ENOMEM, for better or for worse -- a  
> libc
> thing, not pkg, not python.  The message for ENOSPC is "No space  
> left on
> device".

Nod.

>> Sun's xVM VirtualBox is running and probably using lots of memory  
>> so I'll
>> shut it down on Monday and try again. I suspect it won't be useful,  
>> but I
>> can take a look at /tmp/tmph-X54F if you'd like.
>
> Nah, there's nothing in the BE that's useful; you can just blow it  
> away.

OK, thanks.

Cheers,

Chris