From: Chris Mason <mason@suse.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Oops with in nfsd - 2.4.19-pre6
Date: 13 Nov 2002 15:23:21 -0500 [thread overview]
Message-ID: <1037219001.21957.151.camel@tiny> (raw)
In-Reply-To: <20021113194008.6dadeed5.philippe.gramoulle@mmania.com>
On Wed, 2002-11-13 at 13:40, Philippe Gramoullé wrote:
> On 13 Nov 2002 13:14:18 -0500
> Chris Mason <mason@suse.com> wrote:
>
> | Ok, I was hoping for some confirmation that you've seen the bug fixed
> | with the quota code. Which kernel version + list of patches are you
> | best able to test on? I'll make you patch against that.
> |
> | -chris
>
> Unfortunately, we hit the bug again this afternoon :-(
>
> We use to have 2.4.19-pre6 with the quota patches from
> ftp.suse.com:/pub/people/mason/patches/reiserfs/quota-2.4/2.4.19
> ( 0xFFFF test removed in sys_quotactl() in fs/dquot.c to support 32 bit UIDS)
> and IIRC NFS_ALL patch for 2.4.19
>
> Being unable to run the quota anyway with 2.4.19-pre6,as it would make the filer crash, i upgraded to
> 2.4.20rc1 + data-logging patches and mounted the fs witn noatime,nodiratime and data=journal
Ok, I'll make a patch against that.
>
> Filer is still heavily loaded but runs fine. Problem now is that we don't have quota working anymore
> and this is a _big_ issue as warez lovers do test our systems every single minute.
>
> 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 ;-) The races do not cause corruptions or
crashes of any kind.
>
> Ideally, i'd like to stay with 2.4.20rc1 thus having working quota.
> I couldn't check closely enough because of being too busy but i think many important patches have been
> set into RC1 (new block allocator, etc..).
> I tried to have a look to merge the quota code with RC1 but unfortunately my knowledge of quota/reiserfs
> prevent me from doing anything but cosmetic merge :o)
>
> Let me know what are you plans.
Jan and I will get an updated quota patch asap, and I'll have my
attempted fix for the transaction overflow ready for you against that
set of patches in a few hours.
-chris
next prev parent reply other threads:[~2002-11-13 20:23 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 [this message]
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
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=1037219001.21957.151.camel@tiny \
--to=mason@suse.com \
--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.