From: Dave Chinner <david@fromorbit.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: xfs@oss.sgi.com
Subject: Re: Disk full during delayed allocation
Date: Wed, 3 Dec 2008 14:24:02 +1100 [thread overview]
Message-ID: <20081203032402.GT18236@disturbed> (raw)
In-Reply-To: <alpine.LNX.1.10.0812022055550.14216@fbirervta.pbzchgretzou.qr>
On Tue, Dec 02, 2008 at 09:02:25PM +0100, Jan Engelhardt wrote:
> Hi,
>
>
> on space-constrained filesystems, I noticed that extracting lots of
> files [about 10k] bumps the Used count up quickly leading to a disk full
> unless the extraction process (rpm here) is halted, synced, and then
> continued. I believe this is fully within XFS's standard behavior, but I
> would like to learn more how exactly this can happen.
Outstanding delayed allocation has reservations for metadata blocks
that *may* be required to do the delayed allocation. most delalloc's
don't require metadata blocks to be allocated and hence when the
data is sync'd the reservation is freed and there is "magically"
more space available.
> My guess is that
> this is due to the "dynamic journal/log" size XFS employs
It is not dynamic. The XFS journal size is fixed at mkfs time - it's
just that it is sized according to the size of the filesystem being
made....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-03 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 20:02 Disk full during delayed allocation Jan Engelhardt
2008-12-03 3:24 ` Dave Chinner [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=20081203032402.GT18236@disturbed \
--to=david@fromorbit.com \
--cc=jengelh@medozas.de \
--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