OpenVZ Forum


Home » Mailing lists » Devel » How Inactive may be much greather than cached?
Re: How Inactive may be much greather than cached? [message #21975 is a reply to message #21952] Thu, 18 October 2007 10:33 Go to previous messageGo to previous message
vaverin is currently offline  vaverin
Messages: 708
Registered: September 2005
Senior Member
Nick Piggin wrote:
> Some filesystems, including I believe, ext3 with data=ordered,
> can leave orphaned pages around after they have been truncated
> out of the pagecache. These pages get left on the LRU and vmscan
> reclaims them pretty easily.
> 
> Try ext3 data=writeback, or even ext2.

thanks, data=writeback helps.

Resume: ext3 with data=ordered gets bh with data and moves it to journal
transaction. If transaction handled immediately, ext3 frees bh on this page, and
then frees this page.
However if journal delays processing of this transaction, ext3 cannot free bh
that is still busy. Later jbd layer decrements bh counter but it makes nothing
with data page that is not freed and stays inactive.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH] Fix again the fl6_sock_lookup() fixed locking
Next Topic: [PATCH 0/4] Fix race between sk_filter reassign and sk_clone()
Goto Forum:
  


Current Time: Fri Aug 22 04:41:07 GMT 2025

Total time taken to generate the page: 0.05911 seconds