From: Chris Mason <mason@suse.com>
To: Johan Ekenberg <johan@ekenberg.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SV: Lockups with 2.4.14 and 2.4.16
Date: Tue, 11 Dec 2001 20:15:12 -0500 [thread overview]
Message-ID: <2545860000.1008119712@tiny> (raw)
In-Reply-To: <001001c182a8$8624a670$050010ac@FUTURE>
In-Reply-To: <001001c182a8$8624a670$050010ac@FUTURE>
On Wednesday, December 12, 2001 02:01:25 AM +0100 Johan Ekenberg
<johan@ekenberg.se> wrote:
>> >## Kernel:
>> > - 2.4.14 and 2.4.16
>> > - Patched for reiserfs-quota with patches found at
>> > ftp://ftp.suse.com/pub/people/mason/patches/reiserfs/quota-2.4/
>> > ( * 50_quota-patch
>> > * dquota_deadlock
>> > * nesting
>> > * reiserfs-quota )
>>
>> For the 2.4.16 kernel, you used the quota patches from my 2.4.16 dir?
>
> Yes.
>
>> The fastest way to rule out filesystem deadlocks is to hook up a serial
>> console and send me the decoded output of sysrq-t.
>
> I'll look into this. A bit of a problem since there are 10 servers and you
> never know which one is going to lockup next time. Do I really need 10 PC's
> to monitor them simultaneously or could it be done more efficiently? I'm no
> kernel hacker, any pointers as to what tools to use etc would be most
> welcome.
For this case, it is enough to configure each kernel to allow a serial
console, wait for a machine to lockup, plugin the serial cable to that one
machine, and then do the sysrq-t.
But, test that method first ;-) You can hit sysrq-t at any time without
breaking things.
-chris
prev parent reply other threads:[~2001-12-12 1:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 23:29 Lockups with 2.4.14 and 2.4.16 Johan Ekenberg
2001-12-11 23:47 ` Alan Cox
2001-12-11 23:56 ` SV: " Johan Ekenberg
2001-12-12 0:36 ` Alan Cox
2001-12-14 16:49 ` Chris Mason
2001-12-14 17:26 ` Andrew Morton
2001-12-14 17:53 ` Chris Mason
2001-12-14 18:32 ` Andrea Arcangeli
2001-12-14 18:55 ` Chris Mason
2001-12-14 18:57 ` Andrew Morton
2001-12-14 19:16 ` Andrea Arcangeli
2001-12-20 13:29 ` Chris Mason
[not found] ` <1624652704.1008906979@tiny>
[not found] ` <3C22CC54.D4F5B01@zip.com.au>
2001-12-21 13:29 ` [PATCH] " Chris Mason
2001-12-14 19:26 ` Jan Kara
2001-12-14 19:21 ` Jan Kara
2001-12-12 0:56 ` SV: " Johan Ekenberg
2001-12-12 1:22 ` Alan Cox
2001-12-12 0:12 ` Brad Dameron
2001-12-12 0:47 ` Chris Mason
2001-12-12 1:01 ` SV: " Johan Ekenberg
2001-12-12 1:10 ` Hans Reiser
2001-12-12 1:15 ` Chris Mason [this message]
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=2545860000.1008119712@tiny \
--to=mason@suse.com \
--cc=johan@ekenberg.se \
--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 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.