All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: Premature "No Space left on device" on XFS
Date: Fri, 7 Oct 2011 13:40:24 +0200	[thread overview]
Message-ID: <201110071340.25077@zmi.at> (raw)
In-Reply-To: <20111007013711.GW3159@dastard>


[-- Attachment #1.1: Type: Text/Plain, Size: 1083 bytes --]

On Freitag, 7. Oktober 2011 Dave Chinner wrote:
> And with 1.7 million inodes in it. That's a lot for a tiny
> filesystem, and not really a use case that XFS is well suited to.
> XFS will work, but it won't age gracefully under these conditions...

But which FS would fit better for that? We have similar usages, so I'm 
curious.

> As it is, your problem is most likely fragmented free space (an
> aging problem). Inodes are allocated in chunks of 64, so require an
> -aligned- contiguous 16k extent for the default 256 byte inode size.
> If you have no aligned contiguous 16k extents free then inode
> allocation will fail.

Would this be a use case for the "noikeep" mount option?

When would be the time XFS drops inode clusters that are already empty, 
when I use noikeep on an aged XFS with lots of such unused inode 
allocations?

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

// Haus zu verkaufen: http://zmi.at/langegg/

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-10-07 11:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 19:55 Premature "No Space left on device" on XFS Bernhard Schmidt
2011-10-07  0:22 ` Stan Hoeppner
2011-10-07  0:47   ` Bernhard Schmidt
2011-10-07  1:37 ` Dave Chinner
2011-10-07  8:40   ` Gim Leong Chin
2011-10-07 23:20     ` Dave Chinner
2011-10-07 11:40   ` Michael Monnerie [this message]
2011-10-07 23:17     ` Dave Chinner
2011-10-07 13:49   ` Bernhard Schmidt
2011-10-07 23:14     ` Dave Chinner
2011-10-08 12:29       ` Bernhard Schmidt
2011-10-08 13:18         ` Christoph Hellwig
2011-10-08 22:34           ` Dave Chinner
2011-10-09 14:46             ` Christoph Hellwig
2011-10-08 22:30         ` Dave Chinner
2011-10-07 13:58   ` Bryan J Smith
2011-10-07 23:31     ` Dave Chinner
2011-10-08  6:30       ` Bryan J Smith
2011-10-08 13:16         ` Christoph Hellwig

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=201110071340.25077@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.