From: Dave Chinner <david@fromorbit.com>
To: Jorge Garcia <jorge.garcia101011@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS quotas: Skipping quotacheck in the initial mount
Date: Tue, 1 May 2018 08:48:49 +1000 [thread overview]
Message-ID: <20180430224849.GG13766@dastard> (raw)
In-Reply-To: <CAN==6Xc9aNnEShwAtCfdtNeYHVFORFjJhzOss=x2KBSp0Qb2=Q@mail.gmail.com>
On Thu, Apr 26, 2018 at 04:58:00PM +0200, Jorge Garcia wrote:
> Hi all,
>
> I tried to add XFS quotas in a fileserver with a capacity of 260TB
> (112TB occupied), but after adding the user and project quota options
> for this disk in the fstab file and remounting it, the mount rest
> hanged running the quota check process. I waited for 20 minutes, but
> this process did not finish. Due to this server can't be unavailable,
> I had to cancel the process and remove the quota options from fstab
> file.
>
> My question is: Would it be possible to run the quota check process in
> the background? If not, how could I get the estimated time to finish
> this process?
>
> Additional info:
>
> This server is running 3.10.0-693.21.1.el7.x86_64 kernel (CentOS 7.4),
> and here the number of inodes:
>
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/sda 5625717696 39592403 5586125293 1% /export
FYI, you have 39.5 million allocated inodes. Given optimal inode
chunk distribution, that requires (39.5 / 32) million IOs to run
a quota scan. If you have spinning disks, then you are looking at
300 IOs/s here, and so somewhere around (1.25 x 10^6 / 3 x 10^2) =
~4200 seconds.
So I'd expect quota check to take somewhere between 1.5-2 hours to
complete on a filesystem like this.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-04-30 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 14:58 XFS quotas: Skipping quotacheck in the initial mount Jorge Garcia
2018-04-30 9:27 ` Carlos Maiolino
2018-04-30 22:48 ` 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=20180430224849.GG13766@dastard \
--to=david@fromorbit.com \
--cc=jorge.garcia101011@gmail.com \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.