public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Nishimoto <miken@agami.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: xfs@oss.sgi.com
Subject: Re: Allocating inodes from a single block
Date: Tue, 17 Jul 2007 14:01:58 -0700	[thread overview]
Message-ID: <469D2E46.8080003@agami.com> (raw)
In-Reply-To: <20070717201921.GA26309@tuatara.stupidest.org>

Chris Wedgwood wrote:
> On Tue, Jul 17, 2007 at 11:11:50AM -0700, Michael Nishimoto wrote:
> 
>  > Filesystem free space becomes fragmented over time.  It's possible
>  > for total free space to be a decent size and still not have a chunk
>  > large enough to allocate new inodes.
> 
> by default there is a restriction that indoes shouldn't consume more
> that 25% of the total space
> 
> see the mkfs.xfs man-page for details, search for 'maxpct'
> 
> for existing filesystems you can use xfs_db to rewrite this value

I do know about the 25% restriction, but that isn't what I'm talking
about.  I'm not suggesting to fillup a filesystem 100% with
inodes.

Imagine a case where only 2-3% of the space is inodes but that 94%
of the total space was filled.  If the remaining 6% of space is
highly fragmented, then no new inodes can be allocated.  The dialloc
code couldn't find 8 contiguous blocks.

    Mike

  reply	other threads:[~2007-07-17 21:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 18:11 Allocating inodes from a single block Michael Nishimoto
2007-07-17 20:19 ` Chris Wedgwood
2007-07-17 21:01   ` Michael Nishimoto [this message]
2007-07-18  1:43   ` Eric Sandeen
2007-07-18  2:01     ` Nathan Scott
2007-07-18  3:50       ` David Chinner
2007-07-18 17:53         ` Michael Nishimoto
2007-07-18 19:10         ` Mike Montour
2007-07-19  2:30           ` David Chinner
2007-07-20  1:26             ` Mike Montour
     [not found] <200707231240.23425.david@fromorbit.com>
2007-07-23  5:06 ` David Chinner

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=469D2E46.8080003@agami.com \
    --to=miken@agami.com \
    --cc=cw@f00f.org \
    --cc=xfs@oss.sgi.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