public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Mukul Malhotra <smilemukul2005@gmail.com>, xfs@oss.sgi.com
Subject: Re: How to determine the reserved blocks in xfs filesystem ?
Date: Tue, 18 Nov 2014 19:19:41 -0500	[thread overview]
Message-ID: <20141119001941.GA37095@bfoster.bfoster> (raw)
In-Reply-To: <20141118223518.GR23575@dastard>

On Wed, Nov 19, 2014 at 09:35:18AM +1100, Dave Chinner wrote:
> On Tue, Nov 18, 2014 at 08:32:07AM -0500, Brian Foster wrote:
> > On Tue, Nov 18, 2014 at 06:05:58PM +0530, Mukul Malhotra wrote:
> > > ​Hello,
> > > 
> > > Does xfs have reserved blocks too, like ext* ? if yes, how can they be
> > > determined ?​
> > > 
> > 
> > XFS reserves blocks internally such that it can perform operations when
> > all free space is consumed, etc. It looks like 5% is the default.
> 
> Not quite.
> 
>         /*
>          * We default to 5% or 8192 fsbs of space reserved, whichever is
>          * smaller.  This is intended to cover concurrent allocation
>          * transactions when we initially hit enospc. These each require a 4
>          * block reservation. Hence by default we cover roughly 2000 concurrent
>          * allocation reservations.
>          */
> 
> So, in most cases, there are 32MB of reserved blocks available for
> internal emergency use.
> 

Yep, I glossed right over the hard cap... thanks. ;)

Brian

> > I don't think it's "like ext4," however, which reserves blocks for the
> > root user. I don't believe the reserved blocks in XFS are accessible for
> > file allocation by any user unless the reserve pool is modified as such.
> 
> Most definitely not "like ext4". The reserved blocks are considered
> "used space" (i.e. not available to any user) and are reported as
> such in statfs() output (e.g. via df).
> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com

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

  reply	other threads:[~2014-11-19  0:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 12:35 How to determine the reserved blocks in xfs filesystem ? Mukul Malhotra
2014-11-18 13:32 ` Brian Foster
2014-11-18 22:35   ` Dave Chinner
2014-11-19  0:19     ` Brian Foster [this message]
2014-11-21 16:36       ` Mukul Malhotra
2015-08-24  4:44 ` Mukul Malhotra
2015-08-24 15:08   ` Emmanuel Florac

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=20141119001941.GA37095@bfoster.bfoster \
    --to=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=smilemukul2005@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