mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Chris Meadors <clubneon@hereintown.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Disk quotas not staying in sync?
Date: Wed, 1 Aug 2001 12:06:17 -0600 (MDT)	[thread overview]
Message-ID: <200108011806.f71I6Ht1006946@webber.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.31.0108011322470.4569-100000@rc.priv.hereintown.net> "from Chris Meadors at Aug 1, 2001 01:43:23 pm"

Chris writes:
> The problem is sometimes after all the messages have been deleted they
> still can't get any new mail.  Looking at their quota usage the machine
> still thinks that they have their quota full, but `du` says otherwise.
> 
> I've tried to reproduce this with a test account.  Just creating a bunch
> of files to run up to the quota and then deleting them.  But no matter
> what I tried the system followed the test account's disk usage exactly.

Maybe the problem is caused by root/admin deleting another users files?

> This doesn't just happen when someone runs up to their quota.  I have also
> seen their quota usage not correctly reflect what is on disk, but as the
> usage goes up and down, both the actual disk usage and the what quota says
> change by the same amount.

Do you run quotacheck at boot time?  It is possible with ext2 that the
on-disk quotas are not in sync with the actual files if there is a crash.
If you use ext3 then the quota updates and other filesystem updates are
kept atomic.

> Any ideas?  This machine is pretty much standard.  ext2 file systems on
> all partitions.  /home is the only one with user disk quotas.  Running
> 2.4.7 kernel (but I've seen it in all 2.4 kernels, I was running
> 2.4.0-prerelease on the machine when I first put it up, so I don't know
> how 2.2 works).

You should also try the -ac kernels.  I'm pretty sure that they have
some fixes to the quota code.  However, I _think_ the changes are not
compatible with the non-ac kernel quota on-disk data, so you will have
to re-build the quota files (a small price to pay if it actually works).

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-08-01 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 17:43 Chris Meadors
2001-08-01 18:06 ` Andreas Dilger [this message]
2001-08-01 19:25   ` Chris Meadors
2001-08-07 15:51     ` Jan Kara
2001-08-07 17:41       ` Chris Meadors
2001-08-07 17:35         ` 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=200108011806.f71I6Ht1006946@webber.adilger.int \
    --to=adilger@turbolinux.com \
    --cc=clubneon@hereintown.net \
    --cc=linux-kernel@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 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®