Hi,
I've caught bzip2 misbehaving. The following top output is for
compression of /var/log/messages (just over 100kB size) and it's not
finished yet:
21172 root 1 1180 11360K 8248K RUN 11:02 100.00% bzip2
Over 11 minutes, and still going, at 100% CPU. Now that's
Neil Darlow wrote:
Hi,
I've caught bzip2 misbehaving. The following top output is for
compression of /var/log/messages (just over 100kB size) and it's not
finished yet:
21172 root 1 1180 11360K 8248K RUN 11:02 100.00% bzip2
Over 11 minutes, and still going, at 100%
Hi,
Kris Kennaway wrote:
Again, it's not bzip2 that is your underlying problem.
I can't see what else it could be. I watched newsyslog kick-in at
11:00UTC to rotate logs and that's what happened.
There was no esoteric hardware access, e.g. writing to DVD, happening at
the time so I'm at a
Neil Darlow wrote:
Hi,
Kris Kennaway wrote:
Again, it's not bzip2 that is your underlying problem.
I can't see what else it could be. I watched newsyslog kick-in at
11:00UTC to rotate logs and that's what happened.
There was no esoteric hardware access, e.g. writing to DVD, happening at
Neil Darlow wrote:
Hi,
I have recently upgraded from RELENG_6_3 to RELENG_7_0 via the source
method. I followed the upgrade instructions in the 7.0 release notes and
rebuilt all ports successfully.
My hardware is a VIA EPIA PD1 (VIA Centerhauls CPU) with gmirrored
IDE disks and GELI
Hi,
I have recently upgraded from RELENG_6_3 to RELENG_7_0 via the source
method. I followed the upgrade instructions in the 7.0 release notes and
rebuilt all ports successfully.
My hardware is a VIA EPIA PD1 (VIA Centerhauls CPU) with gmirrored
IDE disks and GELI encrypted swap (using
Hi,
Kris Kennaway wrote:
This should be unrelated to bzip since that is purely CPU bound. What
is causing the interrupts? Check vmstat -i. That is likely to be your
real problem.
The cause of the high interrupt incidence was failed DMA operations on
my DVD-RW drive.
The situation arose
On Thursday 06 March 2008 13:14:02 Neil Darlow wrote:
I've rebooted the system and watched cron execute newsyslog to rotate
the logs. I have a bzip2 process that's consuming over 90% of CPU. That
can't be normal?
It's normal.
It's not normal if the files don't get compressed.
--
Mel
