From: Michael Nishimoto <miken@agami.com>
To: xfs@oss.sgi.com
Subject: Allocating inodes from a single block
Date: Tue, 17 Jul 2007 11:11:50 -0700 [thread overview]
Message-ID: <469D0666.6040908@agami.com> (raw)
Hi everyone,
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.
During testing, we managed to create a 111G filesystem which
could no longer create new inodes, but it had 6% free space.
Has anyone thought about how to solve this issue?
Ideally, a solution would still allocate multiple contiguous blocks
of inodes when space is available but would eventually work when
only single free blocks are available. And it would be good if
any change remains backwards compatible with existing ondisk
formats.
thanks,
Michael
next reply other threads:[~2007-07-17 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 18:11 Michael Nishimoto [this message]
2007-07-17 20:19 ` Allocating inodes from a single block Chris Wedgwood
2007-07-17 21:01 ` Michael Nishimoto
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=469D0666.6040908@agami.com \
--to=miken@agami.com \
--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