mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: dev@sw.ru, wli@holomorphy.com, steiner@sgi.com, sandeen@sgi.com
Subject: 21 million inodes is causing severe pauses.
Date: Mon, 15 Nov 2004 13:55:52 -0600	[thread overview]
Message-ID: <20041115195551.GA15380@lnx-holt.americas.sgi.com> (raw)


The subject line is a little deceiving.  That number comes from using
XFS on a 2.4 kernel.  With a 2.6 kernel, we see problems similar to the
ones we are experiencing on 2.4, only less severe.

Digging into this some more, we determined the problem is the large number
of inodes and dentry items held.  For a machine with 32GB of memory and
8 cpus doing build type activity, we have found it stabilizes at between
2 and 8 million entries.

One significant problem we are running into is autofs trying to umount the
file systems.  This results in the umount grabbing the BKL and inode_lock,
holding it while it scans through the inode_list and others looking for
inodes used by this super block and attempting to free them.

We patched a SLES9 kernel with the patch found in the -mm tree which
attempts to address this problem by linking inodes off the sb structure.
This does make the umount somewhat quicker, but on a busy nfs mounted
filesystem, the BKL and inode_lock do still get in the way causing
frequent system pauses on the order of seconds.  This is on a SLES9
kernel which we just put into a test production environment last Thursday.
By 8:00 AM Friday, the system was unusable.

Additionally, we experience NULL pointer dereferences during
remove_inode_buffers.  I have not looked for additional patches in the
-mm tree to address that problem.

While discussing this in the hallway, we have come up with a few possible
alternatives.

1) Have the dentry and inode sizes limited on a per sb basis
   with a mount option as an override for the default setting.

2) Have the vfs limit dentry and inode cache sizes based on
   slab usage (ie, nfs, ext2, and xfs slab sizes are limited independently
   of each other.

3) Have the vfs limit it based on total inode_list entries.

We are not sure which if any is the right direction to go at this time.
We are only hoping to start a discussion.  Any guidance would be
appreciated.

Thank you,
Robin Holt

PS:  The patch referred to above is:
http://marc.theaimsgroup.com/?l=linux-kernel&m=109474397830096&w=2

             reply	other threads:[~2004-11-15 20:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 19:55 Robin Holt [this message]
2004-11-15 20:35 ` Norbert van Nobelen
2004-11-15 20:51   ` Robin Holt
2004-11-15 20:57   ` linux-os
2004-11-15 21:31     ` Robin Holt
2004-11-15 22:57 ` Andrew Morton
2004-11-16 16:28   ` Robin Holt
2004-11-16 19:13     ` Andrew Morton
2004-11-16 19:48       ` Robin Holt
2004-11-17  0:33         ` Andrew Morton
2004-11-17  0:54           ` Robin Holt
2004-11-17  1:05             ` Andrew Morton
2004-11-16 16:32   ` Robin Holt
2004-11-16 19:15     ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041115195551.GA15380@lnx-holt.americas.sgi.com \
    --to=holt@sgi.com \
    --cc=dev@sw.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@sgi.com \
    --cc=steiner@sgi.com \
    --cc=wli@holomorphy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®