[Top] [All Lists]

Re: Disk full during delayed allocation

To: Jan Engelhardt <jengelh@xxxxxxxxxx>
Subject: Re: Disk full during delayed allocation
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 3 Dec 2008 14:24:02 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <alpine.LNX.1.10.0812022055550.14216@xxxxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Jan Engelhardt <jengelh@xxxxxxxxxx>, xfs@xxxxxxxxxxx
References: <alpine.LNX.1.10.0812022055550.14216@xxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
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


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>