public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Derfinak <ja@mail.upjs.sk>
To: Dave Chinner <david@fromorbit.com>
Cc: Stan Hoeppner <stan@hardwarefreak.com>, xfs@oss.sgi.com
Subject: Re: ENOSPC at 90% with plenty of inodes
Date: Tue, 12 Oct 2010 15:52:40 +0200	[thread overview]
Message-ID: <4CB46828.2030104@mail.upjs.sk> (raw)
In-Reply-To: <20101012102954.GQ4681@dastard>

Dave Chinner wrote:

>> If so, could/should the OP specify anything
>> during the mkfs.xfs reformat that may help alleviate or mitigate his
>> problem in the future?
> 
> No. These problems usually appear in filesystems that have run at
> greater than 85-90% full for extended periods of time without being
> emptied at all. Once you start to free up space, it naturally
> defragments itself, but if you never free up any significant amount
> of space in the filesytesm, this cannot occur and so fragmentation
> just keeps getting worse....

I'm curious if using noikeep mount option has any effect on free space
fragmentation?

jan

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

  reply	other threads:[~2010-10-12 13:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 17:17 ENOSPC at 90% with plenty of inodes James Braid
2010-10-08 20:40 ` Emmanuel Florac
2010-10-08 20:43 ` Emmanuel Florac
2010-10-08 22:51 ` Dave Chinner
2010-10-11 14:03   ` James Braid
2010-10-11 22:35     ` Dave Chinner
2010-10-12  1:27       ` Stan Hoeppner
2010-10-12 10:29         ` Dave Chinner
2010-10-12 13:52           ` Jan Derfinak [this message]
2010-10-12 23:21           ` Stan Hoeppner
2010-10-13  0:25             ` Dave Chinner
2010-11-24  1:04 ` XIE Zhengmao
  -- strict thread matches above, loose matches on Subject: below --
2010-10-08 20:33 Richard Scobie

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=4CB46828.2030104@mail.upjs.sk \
    --to=ja@mail.upjs.sk \
    --cc=david@fromorbit.com \
    --cc=stan@hardwarefreak.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