xfs
[Top] [All Lists]

Re: deep chmod|chown -R begin to start OOMkiller

To: CHIKAMA masaki <masaki-c@xxxxxxxxxx>
Subject: Re: deep chmod|chown -R begin to start OOMkiller
From: David Chinner <dgc@xxxxxxx>
Date: Thu, 8 Dec 2005 18:08:41 +1100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20051207183531.5c13e8c5.masaki-c@xxxxxxxxxx>
References: <20051207183531.5c13e8c5.masaki-c@xxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Wed, Dec 07, 2005 at 06:35:31PM +0900, CHIKAMA masaki wrote:
> Hello all.
> 
> I have trouble about a storange behavior on xfs fileststem.
> When I did "chmod -R 755 ." on deep directory, the system became 
> slow down and began to start OOMkiller after a while.

How many files in the directory structure and how deep is it?

What is the machine you are running this test on (CPU, ram,
etc).

> At that time, slabtop showed that the number of xfs_ili, xfs_inode, 
> and linvfs_icache objects are becoming very large.
> 
> My kernel version is 2.6.13.4. 

Can you send the output of /proc/meminfo, /proc/slabinfo
and the OOM killer output at the time of the problem?

> A similar report is found at
>  http://oss.sgi.com/archives/linux-xfs/2003-03/msg00018.html
> 
> 
> Is this a expected bihavior?

No.

> Now I use "find -exec" insted of "chmod -R".
> The usage of slab memory with "find" is calm and does not start
> OOM killker. 

The output of the meminfo and slabinfo files under this test
would also be interesting....

Cheers,

Dave.
-- 
Dave Chinner
R&D Software Enginner
SGI Australian Software Group


<Prev in Thread] Current Thread [Next in Thread>