public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Mukul Malhotra <smilemukul2005@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: How to determine the reserved blocks in xfs filesystem ?
Date: Tue, 18 Nov 2014 08:32:07 -0500	[thread overview]
Message-ID: <20141118133206.GA5226@bfoster.bfoster> (raw)
In-Reply-To: <CAJtCNH0tgtCw0F7322b_qvbM9-uGGSsLLiPQj6jk1yyvWDQMYg@mail.gmail.com>

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.

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.

> Can you provide the specific command.
> 

The following command can get/set the reserved block count on an active
mount:

xfs_io -x -c "resblks" <mnt>

Note that this can lead to problems if reduced too much and all space is
consumed, as sometimes block allocation is required to perform space
freeing operations (removing a file, etc.). This is probably a reason
the resblks command is only available in xfs_io expert mode. ;)

Brian

> Thanks
> Mukul

> _______________________________________________
> 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

  reply	other threads:[~2014-11-18 13:32 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 [this message]
2014-11-18 22:35   ` Dave Chinner
2014-11-19  0:19     ` Brian Foster
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=20141118133206.GA5226@bfoster.bfoster \
    --to=bfoster@redhat.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