All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Münning" <konstantin@muenning.com>
To: reiserfs-list@namesys.com
Subject: Re: is quotacheck slow with reiserfs
Date: Thu, 05 Oct 2006 09:33:04 +0200	[thread overview]
Message-ID: <4524B530.9060100@muenning.com> (raw)
In-Reply-To: <20061006075016.GA2414@apartia.fr>

Louis-David Mitterrand wrote:
> On Fri, Oct 06, 2006 at 02:09:11AM +0400, Vladimir V. Saveliev wrote:
>> On Friday 06 October 2006 00:34, Louis-David Mitterrand wrote:
>>> On a 200-user mail server with a 500gb reiser3 fs, quotacheck takes an 
>>> hour at boot time. This is a mail server with 200 users. 
>>>
>> which linux version is in use on the server?
> 
> Debian unstable with latest kernel 2.6.17.
> 
>>> Is that normal? Is there a way to speed it up?
>>>
>> How do users store their mails? If they store one mail in a separate 
>> file, then quotacheck is to iterate over
>> a lot files which can be very time consuming.
> 
> We use maildir, so, yes, it's a lot of files.
> 
> Isn't there a way to run quotacheck in the background while daemons 
> start serving users? 
> 
> Or must it absolutely be run at mount time to be effective?

You may run quotacheck at any time if you don't mind slightly incorrect
qotas as changes done on already checked files while qotacheck is
running wouldn't be noticed. You may skip quotacheck at startup at all -
if your server didn't crash quotas should stay in sync. So you could use
some off-peak time for quotacheck at runtime and do this once in a while.

-- 
Konstantin Münning

  reply	other threads:[~2006-10-05  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 20:34 is quotacheck slow with reiserfs Louis-David Mitterrand
2006-10-05 22:09 ` Vladimir V. Saveliev
2006-10-06  7:50   ` Louis-David Mitterrand
2006-10-05  7:33     ` Konstantin Münning [this message]
2006-10-09 12:01     ` Jan Kara

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=4524B530.9060100@muenning.com \
    --to=konstantin@muenning.com \
    --cc=reiserfs-list@namesys.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 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.