| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS Inode Size question. |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Tue, 22 Jan 2002 22:56:38 +0100 |
| Cc: | Austin Gonyou <austin@xxxxxxxxxxxxxxx>, Nathan Straz <nstraz@xxxxxxx>, Linux XFS List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1011733555.1279.120.camel@xxxxxxxxxxxxxxxxxxxx> |
| References: | <1011732836.1281.118.camel@xxxxxxxxxxxxxxxxxxxx> <1011733491.2172.18.camel@UberGeek> <1011733555.1279.120.camel@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.22.1i |
On Tue, Jan 22, 2002 at 03:05:55PM -0600, Steve Lord wrote: > On Tue, 2002-01-22 at 15:04, Austin Gonyou wrote: > > Scratch that...it just dropped back down about an hour ago. I wonder why > > that would be? I mounted a loopback device around that time. Could that > > have anything to do with it? > > About the only thing which would shrink it is a memory shortage, one > of the things this can cause is a shrink of the inode cache. It's a known problem in 2.4 that it keeps too many dentries/inodes in memory around. It shouldn't keep more inodes than dentries for example, but it does after some stress. It's one of the things that didn't get fixed in t he VM rewrite. Fortunately it doesn't have too many bad effects except for some wasted memory and longer lookup times for inodes due to overlong hash chains. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS kernel crash and corrupted FS, Luis Montes |
|---|---|
| Next by Date: | Re: XFS Inode Size question., Austin Gonyou |
| Previous by Thread: | Re: XFS Inode Size question., Austin Gonyou |
| Next by Thread: | Re: XFS Inode Size question., Austin Gonyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |