All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Haberland <juri.haberland@innominate.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Quota fixes and a few questions
Date: Fri, 27 Oct 2000 11:31:59 +0200	[thread overview]
Message-ID: <39F94B8F.C2293ADD@innominate.de> (raw)
In-Reply-To: <20000927145620.B8484@atrey.karlin.mff.cuni.cz> <20001007003134.B4732@redhat.com> <news2mail-39EAE3A3.7D08CD8B@innominate.de> <news2mail-39EF0906.E7281F12@innominate.de> <20001019190354.A15755@atrey.karlin.mff.cuni.cz> <20001020154204.A1863@redhat.com>

"Stephen C. Tweedie" wrote:
> 
> Hi,
> 
> On Thu, Oct 19, 2000 at 07:03:54PM +0200, Jan Kara wrote:
> >
> > > I stumbled into another problem:
> > > When using ext3 with quotas the kjournald process stops responding and
> > > stays in DW state when the filesystem gets under heavy load. It is easy
> > > to reproduce:
> > > Just extract two or three larger tar.gz files at the same time to a ext3
> > > filesystem with activated quotas...
> 
> Which ext3 version, exactly?  0.0.2f had quota problems because ext3
> wasn't doing quota writethrough, so that inode cleaning could force
> out random dirty quotas at any point.  0.0.3b should fix that.  If it
> doesn't, I'll try to reproduce it here.

Hi Stephen,

unfortunately 0.0.3b has the same problem. I tried it with a stock
2.2.17 kernel + NFS patches + ext3-0.0.3b and the quota rpm you
included. Extracting two larger tar.gz files hits the deadlock reliably.

Juri

-- 
juri.haberland@innominate.de
system engineer                                         innominate AG
clustering & security                               networking people
phone: +49-30-308806-45  fax: -77                http://innominate.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~2000-10-27  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000927145620.B8484@atrey.karlin.mff.cuni.cz>
     [not found] ` <20001007003134.B4732@redhat.com>
     [not found]   ` <news2mail-39EAE3A3.7D08CD8B@innominate.de>
     [not found]     ` <news2mail-39EF0906.E7281F12@innominate.de>
     [not found]       ` <20001019190354.A15755@atrey.karlin.mff.cuni.cz>
     [not found]         ` <20001020154204.A1863@redhat.com>
2000-10-27  9:31           ` Juri Haberland [this message]
2000-10-27 13:10             ` Quota fixes and a few questions Stephen C. Tweedie

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=39F94B8F.C2293ADD@innominate.de \
    --to=juri.haberland@innominate.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@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 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.