From: Chris Mason <mason@suse.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: reiserfs-list@namesys.com, jack@ucw.cz
Subject: Re: Oops with in nfsd - 2.4.19-pre6
Date: 14 Nov 2002 11:32:51 -0500 [thread overview]
Message-ID: <1037291572.287.277.camel@tiny> (raw)
In-Reply-To: <20021114170409.5f9b9108.philippe.gramoulle@mmania.com>
On Thu, 2002-11-14 at 11:04, Philippe Gramoullé wrote:
> On 13 Nov 2002 15:23:21 -0500
> Chris Mason <mason@suse.com> wrote:
>
> | >
> | > BTW, should i apply the patch posted on LKML ?
> | > Subject:2.[45] fixes for design locking bug in wait_on_page/wait_on_buffer/get_request_wait
> |
> | No, wait for that fix to get into a kernel before using it. There might
> | still be small modifications, and andrea might find a few other places
> | in the kernel with similar races.
> |
> | The bug results in io stalls, and the machines that do see them stall
> | for between 10 minutes and an hour. If you needed the patch you would
> | have already been complaining ;-)
>
> Well, now that you mention this, i may also have it on my bug squash list :o)
> When we feed some files to a MySQL server ( 4 way box, lots of threads), sometimes the
> box does nothing , pretty much like andrea described it , so it may be that.
Ok, that does sound like the stalling bug, especially since you've got 4
cpus. You can make it much less likely to trigger by lowering the
threshold for where bdflush jumps in, but andrea's final patch should
show up shortly.
> |
> | Jan and I will get an updated quota patch asap,
>
> This is just great :o) Do you have a rough idea when it will be
> available ? couple days ? couple weeks ?
Now that I've looked at it, I think the only reject is that parisc-32
already has one hunk applied, and x86-64 needs to have quotav2 support
added. Neither one affects i386, but I'll do some tests here. Jan, am
I missing something?
>
>
> | and I'll have my
> | attempted fix for the transaction overflow ready for you against that
> | set of patches in a few hours.
>
> I already got your fixed and but it on 4 or 5 production boxes that triggered the bug.
>
> So far,it's been running fine :o) but without quotas ;o))
Ok, it survived heavier load here overnight.
-chris
next prev parent reply other threads:[~2002-11-14 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:08 Oops with in nfsd - 2.4.19-pre6 JP Howard
2002-10-31 21:30 ` Chris Mason
2002-11-01 14:46 ` Christopher Barry
2002-11-12 17:29 ` Philippe Gramoullé
2002-11-13 18:14 ` Chris Mason
2002-11-13 18:40 ` Philippe Gramoullé
2002-11-13 20:23 ` Chris Mason
2002-11-14 2:33 ` Chris Mason
2002-11-27 20:54 ` Data-Logging Progess?! (was: Oops with in nfsd - 2.4.19-pre6) Manuel Krause
2002-11-28 10:18 ` Philippe Gramoullé
2002-11-28 19:23 ` Manuel Krause
2002-11-14 16:04 ` Oops with in nfsd - 2.4.19-pre6 Philippe Gramoullé
2002-11-14 16:32 ` Chris Mason [this message]
2002-11-14 17:41 ` Philippe Gramoullé
2002-11-14 17:46 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 22:12 JP Howard
2002-10-29 14:59 Philippe Gramoullé
2002-10-29 15:14 ` Oleg Drokin
2002-10-29 15:20 ` Philippe Gramoullé
2002-10-29 15:26 ` Oleg Drokin
2002-10-31 20:38 ` Chris Mason
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=1037291572.287.277.camel@tiny \
--to=mason@suse.com \
--cc=jack@ucw.cz \
--cc=philippe.gramoulle@mmania.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.