From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: linux-ide@vger.kernel.org
Subject: 2.6.15-rc5 mm3 V mm5
Date: Wed, 21 Dec 2005 14:58:48 +0000 [thread overview]
Message-ID: <43A96DA8.8080001@projecthugo.co.uk> (raw)
hi all,
is there anything that anyone would consider "key" to the stability of
the sata_mv or the libata interaction that has been changed between mm1
and mm3
I had terrible usablility and stability using 2.6.15-mm1 with the
sata_mv driver using raid/lvm2, yet in 2.6.15-rc5-mm3 the box has been
up 2 days with a raid 5 array in lvm2 with multiple lvm's hanging off
it. Performance seems good and read/writes seem to be fine, no
corruption yet.
I'm looking through the patches now, and although there does appear to
be libata changes, I can't see anything directly related to the sata_mv
driver, or to anything between libata/sata_mv that would effect
usability this much.
thanks,
Matt.
next reply other threads:[~2005-12-21 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 14:58 Matt Darcy [this message]
2005-12-21 19:05 ` 2.6.15-rc5 mm3 V mm5 Sebastian Kuzminsky
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=43A96DA8.8080001@projecthugo.co.uk \
--to=kernel-lists@projecthugo.co.uk \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).