From: Nathan Scott <nscott@aconex.com>
To: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
Cc: xfs@oss.sgi.com
Subject: Re: is quotacheck fast with xfs?
Date: Fri, 06 Oct 2006 08:15:01 +1000 [thread overview]
Message-ID: <1160086501.32536.57.camel@edge> (raw)
In-Reply-To: <20061005204240.GA7922@apartia.fr>
On Thu, 2006-10-05 at 22:42 +0200, Louis-David Mitterrand wrote:
> Hello,
>
> We have a 500GB mail server with 200 users presently with reiserfs. At
> boot time quotacheck takes close to one hour.
>
> Would quotacheck be faster on xfs?
>
Yes, typically - XFS uses its internal "bulkstat" code to speed up
the inode scanning process (and it only needs to be done once, on the
initial mount, and then XFS "remembers" that the check has been done,
for subsequent mounts and it journals all updates to the quota files),
whereas the userspace quotacheck(1) program is filesystem independent
(IIRC) and doesn't implement such optimisations.
FWIW, quotacheck time is a function of the number of inodes in the
filesystem, not the number of users.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-10-05 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 20:42 is quotacheck fast with xfs? Louis-David Mitterrand
2006-10-05 22:15 ` Nathan Scott [this message]
2006-10-06 7:52 ` Louis-David Mitterrand
2006-10-07 19:42 ` Chris Wedgwood
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=1160086501.32536.57.camel@edge \
--to=nscott@aconex.com \
--cc=vindex+lists-xfs@apartia.org \
--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