From: Garrick Staples <garrick@usc.edu>
To: reiserfs-list@namesys.com
Subject: Re: BUG in journal_mark_dirty on 2.6.7/ia64
Date: Tue, 17 Aug 2004 15:17:59 -0700 [thread overview]
Message-ID: <20040817221759.GQ2136@polop.usc.edu> (raw)
In-Reply-To: <1092780643.12138.1591.camel@watt.suse.com>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Tue, Aug 17, 2004 at 06:10:44PM -0400, Chris Mason alleged:
> On Tue, 2004-08-17 at 15:14, Garrick Staples wrote:
> > Hi all,
> > I'm currently not subscribed (the list daemon isn't replying to my subscribe
> > attempts), so please CC me on replies.
> >
> > I got a kernel panic on one of my ia64 servers last night. It's an NFS server
> > for about 1000 clients and ~10 terabytes of data and has been running great
> > since 2.6.7 was released (Jun 15). Last week it was rebooted to pull out an
> > unused scsi raid card.
> >
> > Last night I got the panic message below, which caused one of my LVM LVs to
> > lock up. Please let me know what other info you need.
>
> Well, this should have been fixed, I'll have to review the transaction
> length code again. Updating to 2.6.8 won't fix it, the good news is
> that particular panic should have kept corruption away.
Thanks for the reply. I did a bit of googling before posting and noted a few
similar posts from a year or two ago, and that noone has reported this error in
awhile. And as you mentioned, I didn't see anything in 2.6.8's changelog that
looked related.
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-17 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 19:14 BUG in journal_mark_dirty on 2.6.7/ia64 Garrick Staples
2004-08-17 22:10 ` Chris Mason
2004-08-17 22:17 ` 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=20040817221759.GQ2136@polop.usc.edu \
--to=garrick@usc.edu \
--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.