From: "Russell Johnson" <rjohnson@rtlogic.com>
To: res1uo0c@verizon.net
Cc: 'Tom Coughlan' <coughlan@redhat.com>, linux-scsi@vger.kernel.org
Subject: RE: Megaraid corruption?
Date: Thu, 9 Dec 2004 11:26:06 -0700 [thread overview]
Message-ID: <003401c4de1c$8c5fddc0$1e01a8c0@rtlogic.com> (raw)
In-Reply-To: <1102613697.8512.31.camel@TroysLinux.verari.com>
I'm running 2.6.7.
Did you try running a test without the megamgr running? The bug that I had
didn't exhibit itself if nothing was running ioctls to the driver. So by
disabling megamgr you would be possibly getting rid of the source of the
data corruption if your bug is the same that mine was.
Once you figure that out you can determine if you want to update to the 2.6
series or not.
Russ
> -----Original Message-----
> From: Troy Klein [mailto:res1uo0c@verizon.net]
> Sent: Thursday, December 09, 2004 10:35 AM
> To: Russell Johnson
> Cc: 'Tom Coughlan'; linux-scsi@vger.kernel.org
> Subject: RE: Megaraid corruption?
>
>
> What kernel version are you running? I am running
> 2.4.21-20.ELsmp (RedHat EL).
>
> Does the megaraid compile with 2.4 kernels and if so how is
> that done the source appears to be for 2.6?
>
> Troy
>
> On Thu, 2004-12-09 at 10:26 -0700, Russell Johnson wrote:
> > There was a recent patch to the megaraid2 driver that fixed
> corruption
> > while some ioctl's were executing during file operations. You
> > mentioned using
> > megamgr. If that is running in the background while you are
> > performing the
> > file copies, it could be causing the bug that was fixed in the most
> > recent
> > megaraid2 driver.
> >
> > Try disabling megamgr and run your test...
> >
> > Or try updating megaraid2 to the latest version. I'm using
> > megaraid cmm: 2.20.2.0 (Release Date: Thu Aug 19 09:58:33 EDT 2004)
> > megaraid: 2.20.4.0 (Release Date: Mon Sep 27 22:15:07 EDT)
> >
>
>
next prev parent reply other threads:[~2004-12-09 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 2:17 Megaraid corruption? Troy Klein
2004-12-09 14:14 ` Tom Coughlan
2004-12-09 15:03 ` Troy Klein
2004-12-09 17:26 ` Russell Johnson
2004-12-09 17:34 ` Troy Klein
2004-12-09 18:26 ` Russell Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 14:18 Mukker, Atul
2004-12-09 14:54 ` Troy Klein
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='003401c4de1c$8c5fddc0$1e01a8c0@rtlogic.com' \
--to=rjohnson@rtlogic.com \
--cc=coughlan@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=res1uo0c@verizon.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.