mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Simon Kirby <sim@netnation.com>, linux-kernel@vger.kernel.org
Subject: Re: Oops: Quota race in 2.4.12?
Date: Tue, 30 Oct 2001 13:14:31 +0100	[thread overview]
Message-ID: <20011030131431.B6302@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20011028215818.A7887@netnation.com> <15325.60309.91155.683380@notabene.cse.unsw.edu.au>
In-Reply-To: <15325.60309.91155.683380@notabene.cse.unsw.edu.au>

  Hello,

> On Sunday October 28, sim@netnation.com wrote:
> > Some of our dual CPU web servers with 2.4.12 are Oopsing while running
> > quotacheck.  They don't seem to die immediately, but oops many times and
> > eventually break.  The old tools didn't warn about quotachecking on a
> > live file system, so some of our servers were set up to run quotacheck
> > nightly.  The new tools still allow you to do it, but warn that it may
> > not be consistent.  We didn't have any problems with 2.2 kernels.
> 
> quotacheck cannot be reliable on a live system as it scans through the
> filesystem counting the usage for each user and then updates the
> quotas file.  If usage changes between scanning a file and updating
> the quota record, you get an error.   This is particularly a problem
> if quotacheck takes a long time, and on one of my servers (heavily
> loaded NFS server) quotacheck takes a *long* time if the server is
> live (it isn't exactly quick if it isn't live either).
> 
> I wrote a little program which uses libext2fs to scan the block device
> for inodes and add up usage that way (as opposed to walking the
> filetree as I believe quotacheck does).  It runs *much* faster
> (minutes instead of hours).
  Note that quotacheck(8) uses e2fslib too if compiled properly...

								Honza

> 

  reply	other threads:[~2001-10-30 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29  5:58 Simon Kirby
2001-10-29 13:44 ` Jan Kara
2001-10-29 16:30   ` Simon Kirby
2001-10-30 12:12     ` Jan Kara
2001-10-29 23:51 ` Neil Brown
2001-10-30 12:14   ` Jan Kara [this message]
2001-10-30  0:23 ` Neil Brown
2001-10-31 13:47 ` 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=20011030131431.B6302@atrey.karlin.mff.cuni.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=sim@netnation.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

all inboxes | Powered by JetHome®