Clearing out inactive memory in the in_d state without a reboot.

[Andrew.Bridgeman at corusgroup.com]

We are running 2.4.21-20.

Regards

[IMAGE]
|+--------------------------+---------------------------------------------|
||   "Mike Burger"          |                                             |
||   <mburger at bubbanfriends.|           To:        "General Red Hat Linux |
||   org>                   |   discussion list" <redhat-list at redhat.com> |
||   Sent by:               |           cc:                               |
||   redhat-list-bounces at red|           Subject:        RE: Clearing out  |
||   hat.com                |   inactive memory in the in_d state without |
||                          |   a  reboot.                                |
||   17/08/2005 22:02       |                                             |
||   Please respond to      |                                             |
||   General Red Hat Linux  |                                             |
||   discussion list        |                                             |
||                          |                                             |
|+--------------------------+---------------------------------------------|







On Wed, August 17, 2005 8:38 am, Smith, Albert said:
>
>
>> -----Original Message-----
>> From: redhat-list-bounces at redhat.com
>>
>> Sorry about before i meant in_d not inet.d as previously stated.
>>
>> Any advice on this problem would be great.
>>
>> Regards
>>
>> Andrew Bridgeman
>>
>> --------------------------------------------------------------
>>
>> Old Question
>>
>> Could someone please advise on the best way of clearing
>> Init_d memory so it gets flushed out to disk. I am running
>> Redhat WS and ES version 3. However i cannot reboot these
>> machines at present so i need to do it while they are
>> on-line. We are having a problem with all of our Linux
>> machines not automatically flushing to disk. Below is what i
>> see currently on the top command.
>>
>> Mem:  3599032k av, 2926964k used,  672068k free   82052k buff
>>  469844k actv, 1731916k in_d,   54940k in_c  Swap: 2044072k
>> av,  0k used, 2044072k free   2614264k cached
>
> I actually have a service call open with Dell Gold Support about this.
> Apparently this is a known issue in the kernel with kswapd not releasing
> the memory properly. They are currently working with RedHat engineering
to
> develop a solution.

Out of curiosity, with which kernel(s) are you seeing this type of issue?

I ask because, running FC3, I find that if I stick with the old
kernel-2.6.11-1.27, I'm doing well, but running any of the released
kernel-2.6.12 packages (currently, I have 2.6.12-1.372 installed), I've
been experiencing system freezes, after 2-3 days of uptime.

Unfortunately, nothing shows up in dmesg, /var/log/messages, and with
screen blanking, I can't see what was on the console, to get a better idea
of what is going on.

I've reverted back to 2.6.11-1.27, for now.

--
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000

To be notified of updates to the web site, visit
http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a
message to:

site-update-request at bubbanfriends.org

with a message of:

subscribe

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

(Embedded image moved to file: pic05097.jpg)

**********************************************************************
This transmission is confidential and must not be used or disclosed by
anyone other than the intended recipient. Neither Corus Group Plc nor
any of its subsidiaries can accept any responsibility for any use or
misuse of the transmission by anyone.
**********************************************************************