Will Murnane wrote:
> On Feb 12, 2008 4:45 AM, Lida Horn <[EMAIL PROTECTED]> wrote:
>
>> The latest changes to the sata and marvell88sx modules
>> have been put back to Solaris Nevada and should be
>> available in the next build (build 84). Hopefully,
>> those of you who use it will find the c
On Feb 12, 2008 4:45 AM, Lida Horn <[EMAIL PROTECTED]> wrote:
> The latest changes to the sata and marvell88sx modules
> have been put back to Solaris Nevada and should be
> available in the next build (build 84). Hopefully,
> those of you who use it will find the changes helpful.
I have indeed f
The latest changes to the sata and marvell88sx modules
have been put back to Solaris Nevada and should be
available in the next build (build 84). Hopefully,
those of you who use it will find the changes helpful.
This message posted from opensolaris.org
I now have a improved sata and marvell88sx driver modules that
deal with various error conditions in a much more solid way.
Changes include reducing the number of required device resets,
properly reporting media errors (rather than "no additional sense"),
clearing aborted packets more rapidly so th
>I can confirm that the marvell88sx driver (or kernel 64a) regularly hangs the
>SATA card (SuperMicr
o 8-port) with the message about a port being reset. The hang is temporary but
troublesome.
>
This could be bug 6553517 which was fixed in build 66.
Casper
> I can confirm that the marvell88sx driver (or kernel
> 64a) regularly hangs the SATA card (SuperMicro
> 8-port) with the message about a port being reset.
> The hang is temporary but troublesome.
> It can be relieved by turning off NCQ in /etc/system
> with "set sata:sata_func_enable = 0x5"
Than
I can confirm that the marvell88sx driver (or kernel 64a) regularly hangs the
SATA card (SuperMicro 8-port) with the message about a port being reset. The
hang is temporary but troublesome.
It can be relieved by turning off NCQ in /etc/system with "set
sata:sata_func_enable = 0x5"
This messa
Al,
That makes so much sense that I can't believe I missed it. One bay was the one
giving me the problems. Switching drives didn't affect that. Switching cabling
didn't affect that. Changing Sata controllers didn't affect that. However,
reorienting the case on it's side did!
I'll be putting in
On Tue, 14 Aug 2007, Richard Elling wrote:
> Rick Wager wrote:
>> We see similar problems on a SuperMicro with 5 500 GB Seagate sata drives.
>> This is using the AHCI driver. We do not, however, see problems with the
>> same hardware/drivers if we use 250GB drives.
>
> Duh. The error is from th
Rick Wager wrote:
> Thanks Richard!
>
> That's the way I read the errors, also, they seem to indicate bad blocks
> on the drives. The bad news is that when they occur access to the zfs
> file system "stops" for quite a long time - seemingly from 30 seconds to
> a minute or longer.
They migh
Rick Wager wrote:
> We see similar problems on a SuperMicro with 5 500 GB Seagate sata drives.
> This is using the AHCI driver. We do not, however, see problems with the same
> hardware/drivers if we use 250GB drives.
Duh. The error is from the disk :-)
> We sometimes see bad blocks reported
We see similar problems on a SuperMicro with 5 500 GB Seagate sata drives. This
is using the AHCI driver. We do not, however, see problems with the same
hardware/drivers if we use 250GB drives.
We sometimes see bad blocks reported (are these automatically remapped somehow
so they are not used
Gary Gendel wrote:
> Thanks for the information. I am using the Marvell8sx driver on a vanilla
> Sunfire v20z server. This project has gone through many frustrating phases...
>
> Originally I tried a Si3124 board with the box running a 5-1 Sil Sata
> multiplexer. The controller didn't understand
>6564677 oracle datafiles corrupted on thumper
wow, must be a huuge database server!
:D
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Thanks for the information. I am using the Marvell8sx driver on a vanilla
Sunfire v20z server. This project has gone through many frustrating phases...
Originally I tried a Si3124 board with the box running a 5-1 Sil Sata
multiplexer. The controller didn't understand the multiplexer so I put in
James C. McPherson wrote:
> Gary Gendel wrote:
>
>> I've got a 5-500Gb Sata Raid-Z stack running under build 64a. I have two
>> problems that may or may not be interrelated.
>>
>> 1) zpool scrub stops. If I do a "zpool status" it merrily continues for
>> awhile. I can't see any pattern in this
Gary Gendel wrote:
> I've got a 5-500Gb Sata Raid-Z stack running under build 64a. I have two
> problems that may or may not be interrelated.
>
> 1) zpool scrub stops. If I do a "zpool status" it merrily continues for
> awhile. I can't see any pattern in this action with repeated scrubs.
>
> 2)
I've got a 5-500Gb Sata Raid-Z stack running under build 64a. I have two
problems that may or may not be interrelated.
1) zpool scrub stops. If I do a "zpool status" it merrily continues for awhile.
I can't see any pattern in this action with repeated scrubs.
2) Bad blocks on one disk. This is
18 matches
Mail list logo
