From: Brian Foster <bfoster@redhat.com>
To: Stefan Ring <stefanrin@gmail.com>
Cc: Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: 50% more blocks allocated than needed
Date: Thu, 31 Jan 2013 14:46:07 -0500 [thread overview]
Message-ID: <510AC9FF.4010007@redhat.com> (raw)
In-Reply-To: <CAAxjCExedk+fWLpD1ypak9HK7b2domtc3aJuBRyEWsvXXsiSWA@mail.gmail.com>
On 01/31/2013 01:28 PM, Stefan Ring wrote:
>> I don't think so at the moment
>
> Really? Even for closed files? I was almost sure that the space would
> be reclaimed before running out of it. I have only slightly less than
> 1 year of XFS experience though...
>
Note that in most cases preallocation is trimmed on file close. The
repeated open-write-close cycle is what causes it to hang around longer
(until inode reclaim).
Somebody else can chime in if I'm missing something, but my
understanding is that we currently run a flush to free up reserved
metadata blocks on ENOSPC and retry. The eofblocks functionality
provides a mechanism that the out of space conditions can use to free up
preallocation, but that part is a work-in-progress.
Brian
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-01-31 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 11:43 50% more blocks allocated than needed Thomas Habets
2013-01-31 18:07 ` Brian Foster
2013-01-31 18:28 ` Stefan Ring
2013-01-31 19:46 ` Brian Foster [this message]
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=510AC9FF.4010007@redhat.com \
--to=bfoster@redhat.com \
--cc=stefanrin@gmail.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