From: Audio Haven <audiohaven@gmail.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: MVSAS status
Date: Wed, 10 Feb 2010 10:22:35 +0100 [thread overview]
Message-ID: <333bc7e11002100122m5eb97d7ey78a31df91dee2405@mail.gmail.com> (raw)
In-Reply-To: <loom.20100210T002935-813@post.gmane.org>
I'm still experiencing issues with this patched driver (using patches
posted in November '09), but I believe I'm hitting known issues in the
following Western Digital green drives.
WDC WD15EADS-00P8B0
I have five of those 00P8B0, some of them have a really high
Load_Cycle_Count, or they become slow during a raid rebuild, or they
just timeout when not using WDIDLE3.EXE (and using the default 8sec
Intellipark feature which is really bad design) ... they are reported
as BAD and "NOT RECOMMENDED" all over the internet. WD doesn't provide
a decent solution yet for these.
My three newer WD15EADS-00S2B0 are also running on the same Marvell
controller and were never kicked out of the raid. Stable and decent
speed. I didn't see any issue with those newer 00S2B0 drives, so I
believe this is actually a WD issue and not a Marvell issue. Maybe the
timeouts are not handled well by the Marvell driver and we're seeing
mvs_abort_task , but that looks more like a symptom.
I disabled the intellipark feature of the WD drives using WDIDLE3.EXE
via a DOS usb bootable stick, and instead of timing out, the
WD15EADS-00P8B0 just have become extremely slow now, iostat reports
1.5 MB/s writes to the raid rebuild drive.
I believe the current MVSAS patches should be good enough if you avoid
WD Green drives;
Best regards,
Audio Haven
On Wed, Feb 10, 2010 at 12:32 AM, Orion Poplawski <orion@cora.nwra.com> wrote:
> What's the status of the MVSAS patches posted in November '09? I'm just trying
> to get started with mvsas and running into the mvs_abort_task issue. At least
> one person has reported that stability improved, but it looks like there were
> some other issues with the patches. Any chance on seeing this in the mainline
> kernel soon? Are there updated versions? A git tree to pull from?
>
> Thanks!
>
> - Orion Poplawski
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-10 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:32 MVSAS status Orion Poplawski
2010-02-10 9:22 ` Audio Haven [this message]
2010-02-10 9:36 ` Caspar Smit
2010-02-10 9:39 ` Mikael Abrahamsson
2010-02-10 9:53 ` Re[2]: " Erno Kovacs
2010-02-11 9:50 ` Kristleifur Daðason
2010-02-11 11:20 ` Mikael Abrahamsson
2010-02-11 11:21 ` Kristleifur Daðason
2010-02-11 18:30 ` Orion Poplawski
2010-02-11 18:55 ` James Bottomley
2010-02-12 12:12 ` Patch for MVSAS Srinivas Naga Venkatasatya Pasagadugula - ERS, HCL Tech
[not found] ` <6B62480106F2B34D8404CF2FDAA4D9EF71F637D6DB@CHN-HCLT-EVS06.HCLT.CORP.H CL.IN-99D05D88-A0F3-0C58-BFB2-2F138E38F61D>
2010-02-13 9:17 ` Caspar Smit
2010-02-14 10:00 ` Mikael Abrahamsson
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=333bc7e11002100122m5eb97d7ey78a31df91dee2405@mail.gmail.com \
--to=audiohaven@gmail.com \
--cc=linux-scsi@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