public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why isn't quota dependant on ext2?
Date: Wed, 22 Jan 2003 13:48:44 -0800	[thread overview]
Message-ID: <20030122134844.2a74c588.akpm@digeo.com> (raw)
In-Reply-To: <200301222105.h0ML5t719018@devserv.devel.redhat.com>

Pete Zaitcev <zaitcev@redhat.com> wrote:
>
> >> > ext3, ufs and udf also use the core quota code.
> >> 
> >> The documentation says it only works with ext2 where would I find working
> >> utilities to get it working on ext3 ?
> > 
> > ext3 uses the same tools as ext2 - checkquota, quotaon, etc.
> > 
> > http://quota-tools.sourceforge.net/ (site seems to be broken)
> 
> The bad news is that quota on ext3 is virtually guaranteed
> to deadlock, so you can do it, but you do not want to do it.

Darnit, I had all that working 18 months ago ;)

> The original memo describes a deadlock in RH 2.4.18-5, which
> I assure you, was NOT fixed in Marcelo 2.4.20.

Yes, that's a common ext3 problem.  A journal_start()/journal_stop() pair is
the same, for locking purposes, as down()/up().  So they need to be ranked
consistently.

Let me crunch on that a bit...


  reply	other threads:[~2003-01-22 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22  1:47 why isn't quota dependant on ext2? Gerhard Mack
2003-01-22  2:59 ` Andrew Morton
2003-01-22  4:00   ` Gerhard Mack
2003-01-22  4:12     ` Andrew Morton
     [not found]     ` <mailman.1043208901.31378.linux-kernel2news@redhat.com>
2003-01-22 21:05       ` Pete Zaitcev
2003-01-22 21:48         ` Andrew Morton [this message]
2003-01-23  4:25           ` Gerhard Mack
2003-01-24  1:32         ` Jakob Oestergaard
2003-01-23  7:59 ` Oleg Drokin

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=20030122134844.2a74c588.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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