From: Kevin Brosius <cobra@compuserve.com>
To: Dave Olien <dmo@osdl.org>
Cc: Samium Gromoff <_deepfire@mail.ru>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Monitor utility (was Re: DAC960 at 2.5.50)
Date: Thu, 05 Dec 2002 07:17:34 -0500 [thread overview]
Message-ID: <3DEF43DE.130064D8@compuserve.com> (raw)
In-Reply-To: 20021203114201.A32313@acpi.pdx.osdl.net
Dave, all,
Did you know about the DAC960 monitor utility? I just ran across it
in the SuSE install set. It's available from
http://varmon.sourceforge.net/
Looks like it's not being maintained anymore (and probably won't work
with the 2.5 driver yet?)
--
Kevin
Dave Olien wrote:
>
>
>
> Let me know if you find any problems at all. I'll try to
> address them.
>
> I think the biggest "imperfection" is just the coding style of
> the whole driver. I might submit some patches over time to clean
> up coding style.
>
> The next problem is that it doesn't handle media errors yet.
> If you have a read or write failure because a sector on your disk
> is bad, it fails the entire read or write. With all the coalescing
> of requests that the block layer does, this might fail ALL of a
> really large transfer just because one sector is bad.
>
> I'm working on a patch that retries failures section at a time,
> so that the failure will be more closely limited to the sector
> that is bad.
>
> On Thu, Nov 28, 2002 at 06:56:22PM +0300, Samium Gromoff wrote:
> > > Samium Gromoff...
> > > > > <alan@lxorguk.ukuu.org.uk>
> > > > > [PATCH] update to OSDL DAC960 driver
> > > > >
> > > > > Its not perfect but it works
> > > > is it supposed to blow my data, or is it relatively safe to use?
> > >
> > > There have been a few poeple using this patch for about 5 versions of
> > > 2.5 so far. I haven't done heavy testing myself, just booting and doing
> > > some other testing of modules and drivers. I am running the DAC960 on
> > > my root/boot filesystem and haven't seen any problems yet.
> > thank you. i`ll join the 2.5 DAC user crowd soon then :-)
> >
> > ---
> > regards,
> > Samium Gromoff
next prev parent reply other threads:[~2002-12-05 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 15:56 DAC960 at 2.5.50 Samium Gromoff
2002-12-03 19:42 ` Dave Olien
2002-12-04 6:57 ` Samium Gromoff
2002-12-05 12:17 ` Kevin Brosius [this message]
2002-12-05 13:06 ` Monitor utility (was Re: DAC960 at 2.5.50) Samium Gromoff
2002-12-05 16:22 ` Randy.Dunlap
2002-12-05 17:45 ` Dave Olien
2002-12-05 19:21 ` Mihai RUSU
2002-12-05 21:33 ` Dave Olien
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=3DEF43DE.130064D8@compuserve.com \
--to=cobra@compuserve.com \
--cc=_deepfire@mail.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmo@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox