All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Johan Ekenberg <johan@ekenberg.se>
Cc: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: SV: Lockups with 2.4.14 and 2.4.16
Date: Wed, 12 Dec 2001 04:10:51 +0300	[thread overview]
Message-ID: <3C16AE9B.5070204@namesys.com> (raw)
In-Reply-To: <001001c182a8$8624a670$050010ac@FUTURE>

Johan Ekenberg 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.
>
>Thanks,
>/Johan Ekenberg
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
You need ten serial ports.  Actually, a lot of machine rooms have all 
their servers connected via serial lines to one machine (or at least 
this was true years ago when I was a sysadmin).  It makes it a lot 
easier to administer them by remote access from home in the middle of 
the night.

Hans



  reply	other threads:[~2001-12-12  1:12 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 [this message]
2001-12-12  1:15     ` 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=3C16AE9B.5070204@namesys.com \
    --to=reiser@namesys.com \
    --cc=johan@ekenberg.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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.