> I lost my snapshots on swap now. do I need them ?
No, snapshots on a swap zvol are just a waste of disk space.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On 02/23/10 12:11 AM, david.co...@sun.com wrote:
I've noticed that since b132 my laptop freezes under load. Just dies
without any message other than "memory pressure, tcp defensive mode
on". Probably short of memory. I've _only_ 1GB which used to be quite
ok for a laptop.
Are you certain it's
after 1 day :
DOWNLOAD PKGS FILESXFER (MB)
Completed 1591/1591 10557/10557 381.9/381.9
PHASEACTIONS
Removal Phase10069/10069
Install Phase
I've noticed that since b132 my laptop freezes under load. Just dies
without any message other than "memory pressure, tcp defensive mode
on". Probably short of memory. I've _only_ 1GB which used to be quite
ok for a laptop.
Are you certain it's actually frozen or just being *very* slow? If you
Try single user mode---It definitely helps
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
stuck for sevrall hours trying to update from 132 to 133. ( macmini 1gb )
strangely top shows 0% swap.
still saying : creating plan
CPU states: 95.3% idle, 0.1% user, 4.6% kernel, 0.0% iowait, 0.0% swap
Kernel: 40789 ctxsw, 153 trap, 949 intr, 1379 syscall, 74 flt, 296 pgin, 36
pgout
Memory:
On 02/21/10 05:29 PM, Alan Coopersmith wrote:
Jürgen Keil wrote:
it freezes during the "Creating plan" when running pkg image-update,
either from b131 be or b132 (I kept both).
A "pkg" process that is using huge amounts of memory could explain this...
The upgrade from previou
Well my machines have been running for about 4.5 hours in creating plan phase.
Unfortunately didn't read the post about single-user mode until after starting
the upgrade.
I guess if they don't succeed or I get an error message, tomorrow I will try
again in single user mode, Part of me wants to
On 02/21/10 07:02 PM, Jürgen Keil wrote:
Tried once again, it seems to freeze each time when
there is about 4K ram left.
Is that a 32- or a 64-bit system?
64-bit
I do have 4G swap, almost not used at all.
Hmm, that is unexpected. How did you watch
swap space usage? swap -l
On 02/21/10 03:58 PM, B wrote:
Unfortunately my vm has already been running for quite some time at about only
1GB. I would have to stop the whole process to increase memory now.
My notebook is not running in vm and only has 1GB, but so far it is a pretty
miminal install, not much added beyond
Unfortunately my vm has already been running for quite some time at about only
1GB. I would have to stop the whole process to increase memory now.
My notebook is not running in vm and only has 1GB, but so far it is a pretty
miminal install, not much added beyond the basic build.
If these two sy
> > A few data points, for those who are about to do
> > this. On a single-CPU 2GB system I get:
> >
> > PID USERNAME NLWP PRI NICE SIZE RES STATE
> TIMECPU COMMAND
> root1 600 1231M 1131M sleep6:10
> 1.36% pkg
> This system had lots of extra ips packages installed
>
> Do you think that it will continue and complete the
> update? My vm build is still in creating plan phase
> but I can see/hear the hardrive reading and writing
> and every once and a while I see the network icon
> flicker...
>
> My notebook which was started earlier is doing the
> same...Neither
Do you think that it will continue and complete the update? My vm build is
still in creating plan phase but I can see/hear the hardrive reading and
writing and every once and a while I see the network icon flicker...
My notebook which was started earlier is doing the same...Neither is
downloadi
> That is not good..Won't the machine just page to
> compensate, though?
That's what I've been observing, with a 1GB virtualbox guest
and pkg image-update. It pages and is slow, but doesn't freeze.
But in my experiment the pkg process size is ~ 650 - 700 mbyte.
--
This message posted from opens
That is not good..Won't the machine just page to compensate, though?
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
> A few data points, for those who are about to do
> this. On a single-CPU 2GB system I get:
>
> PID USERNAME NLWP PRI NICE SIZE RES STATE TIMECPU COMMAND
> 37 root1 600 1231M 1131M sleep6:10 1.36% pkg
This system had lots of extra ips packages installed on top of
th
Thanks for the update. I have 2 boxes running update now. Both have been in the
creating plan phase for about 60 minutes. I wasn't sure if they were stuck or
just renaming the files etc. Starting to get worried althoughI can hear the
hard drives working
One machine is running in a vm the ot
A few data points, for those who are about to do this. On a single-CPU 2GB
system I get:
load averages: 0.30, 0.27, 0.27; up 6+07:48:2120:10:07
120 processes: 119 sleeping, 1 on cpu
CPU states: 91.6% idle, 0.4% user, 8.0% kernel, 0.0% iowait, 0.0% swap
Kernel: 38225
> I just tried to pkg image-update a 64-bit b132 vbox guest.
> 768 MB of memory, and 512 MB swap. It failed during
> "Creating Plan" because the system was running out of
> memory.
With 1 GB of memory and 1 GB of swap the pkg image-update
from b132 to b133 worked. The pkg process had a maximum
p
> Tried once again, it seems to freeze each time when
> there is about 4K ram left.
Is that a 32- or a 64-bit system?
> I do have 4G swap, almost not used at all.
Hmm, that is unexpected. How did you watch
swap space usage? swap -l ?
I just tried to pkg image-update a 64-bit b132 vbox gue
Jürgen Keil wrote:
>> it freezes during the "Creating plan" when running pkg image-update,
>> either from b131 be or b132 (I kept both).
>
> A "pkg" process that is using huge amounts of memory could explain this...
The upgrade from previous builds to 133 is known to make pkg use more
memory tha
On 02/21/10 04:35 PM, Jürgen Keil wrote:
it freezes during the "Creating plan" when running pkg image-update,
either from b131 be or b132 (I kept both).
it freezes during the "evaluating SUNWgcc package"
when trying to ugrade from gui
I know the memory pressure msg is not directly related, but
On 02/21/10 01:46 PM, Bruno Damour wrote:
On 02/21/10 12:12 PM, Jürgen Keil wrote:
I've noticed that since b132 my laptop freezes under
load. Just dies without any message other than
"memory pressure, tcp defensive mode on".
Probably short of memory. I've _only_ 1GB which used
to be quite ok for
> it freezes during the "Creating plan" when running pkg image-update,
> either from b131 be or b132 (I kept both).
> it freezes during the "evaluating SUNWgcc package"
> when trying to ugrade from gui
>
> I know the memory pressure msg is not directly related, but I can see
> the memory being e
On 02/21/10 12:12 PM, Jürgen Keil wrote:
I've noticed that since b132 my laptop freezes under
load. Just dies without any message other than
"memory pressure, tcp defensive mode on".
Probably short of memory. I've _only_ 1GB which used
to be quite ok for a laptop.
AFAIK, the warning messag
> Same here with me - thought that it may be some
> problem in the versions since 128a - but it happens
> more often. with 133 not as often as with 132 but
> yesterday 2 times.
>
> Thinkpad T61p with 4GB RAM - Virtualbox with win64 running .
Do you always get the freezes when virtualbox wa
> I've noticed that since b132 my laptop freezes under
> load. Just dies without any message other than
> "memory pressure, tcp defensive mode on".
> Probably short of memory. I've _only_ 1GB which used
> to be quite ok for a laptop.
AFAIK, the warning message is wrong. Although all
memory is in
> I thought it was a problem with the graphics driver, but you are right
> as soon as I start gdm the box dies and my remote ssh session are dead..
What graphics hardware is that?
Intel video? Could be 6914386, which is not yet fixed in b133
http://bugs.opensolaris.org/bugdatabase/view_bug.do?b
I thought it was a problem with the graphics driver, but you are right
as soon as I start gdm the box dies and my remote ssh session are dead..
I will try again to see if I can get any error messages... Only got 1GB!
Same here with me - thought that it may be some problem in the versions sin
Same here with me - thought that it may be some problem in the versions since
128a - but it happens more often. with 133 not as often as with 132 but
yesterday 2 times.
Thinkpad T61p with 4GB RAM - Virtualbox with win64 running .
Freeze occurs in the same manner - tcp defensive mode on
Hello,
I've noticed that since b132 my laptop freezes under load. Just dies without
any message other than "memory pressure, tcp defensive mode on".
Probably short of memory. I've _only_ 1GB which used to be quite ok for a
laptop.
Now trying to upgrade to b133 and hoping for the best, it just di
32 matches
Mail list logo
