From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: 2.6.6 lockupy
Date: Wed, 26 May 2004 21:39:00 -0700 [thread overview]
Message-ID: <20040527043900.GC6931@polop.usc.edu> (raw)
In-Reply-To: <20040526215555.GI2827@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Wed, May 26, 2004 at 05:55:56PM -0400, J. Bruce Fields alleged:
> On Wed, May 26, 2004 at 02:44:36PM -0700, Garrick Staples wrote:
> > You didn't misunderstand... but I was at a complete loss with production
> > machines suddenly dropping like flies. I'm now at the stage where I just try
> > random things =P
>
> OK. May as well send us what information you have on the lockups, and
> maybe your .config while you're at it....
Filesystem corruption from the repeated lockups finally showed up today. So I
managed to get those two machines out of production for now. I'll be able to
figure out to trigger the problem and hopefully get you some better info
tomorrow.
Btw, the failover capabilities of 2.6 has been very well tested the last few
days :) Nearly 15TB of data was swapped back and forth during heavy writes.
Good job guys on that!
Btw, reiserfs+lvm2 is very resilient!
(does anyone have advice on triggering a kernel trace on ia64?)
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-05-27 4:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 21:11 2.6.6 lockup Garrick Staples
2004-05-26 21:37 ` 2.6.6 lockupy J. Bruce Fields
2004-05-26 21:44 ` Garrick Staples
2004-05-26 21:55 ` J. Bruce Fields
2004-05-26 22:26 ` Garrick Staples
2004-05-27 4:39 ` Garrick Staples [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=20040527043900.GC6931@polop.usc.edu \
--to=garrick@usc.edu \
--cc=nfs@lists.sourceforge.net \
/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.