Why continually pgpgout ?

bob123 · External Since: Nov 04, 2010 Posts: 8

Hi,

RHEL 5.2
My system is idle
but I have continually pgpgout/s ~100

do you know why this ?

Thanks in advance

07:20:01 pgpgin/s pgpgout/s fault/s majflt/s
07:30:01 0.00 116.34 3585.00 0.00
07:40:01 0.00 104.80 3838.14 0.00
07:50:01 0.00 100.96 3680.28 0.00
08:00:01 0.00 101.83 3767.02 0.00
08:10:01 0.18 110.75 3766.50 0.00
08:20:01 0.00 97.35 3837.23 0.00
08:30:01 0.00 101.94 3602.46 0.00
08:40:01 0.00 102.53 3836.61 0.00
08:50:01 0.00 101.62 3684.73 0.00

Nico Kadel-Garcia · External Since: Jul 05, 2009 Posts: 42

On Jan 6, 3:13 am, "bob123" wrote:
> Hi,
>
> RHEL 5.2
> My system is idle
> but I have continually pgpgout/s ~100

Well, first, jump to RHEL 5.5. This saves a *LOT* of old faults.

Second, what exactly is this system doing?

> do you know why this ?
>
> Thanks in advance
>
> 07:20:01 pgpgin/s pgpgout/s fault/s majflt/s
> 07:30:01 0.00 116.34 3585.00 0.00
> 07:40:01 0.00 104.80 3838.14 0.00
> 07:50:01 0.00 100.96 3680.28 0.00
> 08:00:01 0.00 101.83 3767.02 0.00
> 08:10:01 0.18 110.75 3766.50 0.00
> 08:20:01 0.00 97.35 3837.23 0.00
> 08:30:01 0.00 101.94 3602.46 0.00
> 08:40:01 0.00 102.53 3836.61 0.00
> 08:50:01 0.00 101.62 3684.73 0.00

Nico Kadel-Garcia · External Since: Jul 05, 2009 Posts: 42

On Jan 8, 7:10 am, "bob123" wrote:
> The system is idle ...

Well, that's never *quite* completely true. You're running sysstat
occasionally to get sar data, you've got cron and probably a mail
server running, and you probably have an SSH daemon running, getty's
and possibly even X are enable on particular console sessions, etc.
But I take it that you're not running any noticeable active services:
backup tools, file service that might be hammering it, etc. I also
wonder what you use this system for the rest of the time? A webserver,
or what? Maybe you have a Samba or NFS server running that someone
else on your network is accessing?

It should be possible to use "lsof" to see what files are being
accessed, and what programs are running. It should also be possible to
do a system update to avoid a whole stack of old memory flaws: RHEL
5.2 is seriously out of date.

bob123 · External Since: Nov 04, 2010 Posts: 8

The system is idle ...

"Nico Kadel-Garcia" a écrit dans le message de groupe de
discussion :
b4b6401f-bbc0-4c47-af4f-96e5f17f4521.DeleteThis@15g2000vbz.googlegroups.com...
> On Jan 6, 3:13 am, "bob123" wrote:
>> Hi,
>>
>> RHEL 5.2
>> My system is idle
>> but I have continually pgpgout/s ~100
>
> Well, first, jump to RHEL 5.5. This saves a *LOT* of old faults.
>
> Second, what exactly is this system doing?
>
>
>> do you know why this ?
>>
>> Thanks in advance
>>
>> 07:20:01 pgpgin/s pgpgout/s fault/s majflt/s
>> 07:30:01 0.00 116.34 3585.00 0.00
>> 07:40:01 0.00 104.80 3838.14 0.00
>> 07:50:01 0.00 100.96 3680.28 0.00
>> 08:00:01 0.00 101.83 3767.02 0.00
>> 08:10:01 0.18 110.75 3766.50 0.00
>> 08:20:01 0.00 97.35 3837.23 0.00
>> 08:30:01 0.00 101.94 3602.46 0.00
>> 08:40:01 0.00 102.53 3836.61 0.00
>> 08:50:01 0.00 101.62 3684.73 0.00
>

Doug Freyburger · External Since: Dec 06, 2010 Posts: 10

bob123 wrote:
>
> The system is idle ...

It's clearly not idle as it's doing plenty of faults. It has pages out
and faults. A page out is when a page goes out of use. A fault is when
it is put back into use by some other process. A major fault is when
the data in a page is retrieved from disk. What's missing here is the
rate data is being written to disk. In a way that doesn't matter - The
rate it's being red back from disk is zero.

I get that it's not running anything you intend it to run. That does
not equal actually idle. Time to use "top", "ps -ef" and such to see
what the system is actually running. Some process(es) that you consider
overhead is/are busy.