So he did actually hit a bug? But the bug is not dangerous as it doesnt destroy
data?
But I did not replace any devices and still it showed checksum errors. I think
I did a zfs send | zfs receive? I dont remember. But I just copied things back
and forth, and the checksum errors showed up. So wh
The checksum errors are fixed in build 128 with:
6807339 spurious checksum errors when replacing a vdev
No; you're not losing any data due to this.
- Eric
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolari
On Wed, Nov 11, 2009 at 3:38 AM, Orvar Korvar <
knatte_fnatte_tja...@yahoo.com> wrote:
> Other drivers in the stack? Which drivers? And have anyone of them been
> changed between b125 and b126?
>
Looks like the sd drive for one.
http://dlc.sun.com/osol/on/downloads/b126/on-changelog-b126.html
On Nov 11, 2009, at 12:01 AM, Tim Cook wrote:
On Tue, Nov 10, 2009 at 5:15 PM, Tim Cook wrote:
One thing I'm
noticing is a lot of checksum errors being generated during the
resilver.
Is this normal?
Anyone? It's up to 7.35M checksum errors and it's rebuilding
extremely
slowly (as evi
Other drivers in the stack? Which drivers? And have anyone of them been changed
between b125 and b126?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-
On Tue, Nov 10, 2009 at 5:15 PM, Tim Cook wrote:
>
>
> On Tue, Nov 10, 2009 at 10:55 AM, Richard Elling > wrote:
>
>>
>> On Nov 10, 2009, at 1:25 AM, Orvar Korvar wrote:
>>
>> Does this mean that there are no driver changes in marvell88sx2, between
>>> b125 and b126? If no driver changes, then
On Tue, Nov 10, 2009 at 10:55 AM, Richard Elling
wrote:
>
> On Nov 10, 2009, at 1:25 AM, Orvar Korvar wrote:
>
> Does this mean that there are no driver changes in marvell88sx2, between
>> b125 and b126? If no driver changes, then it means that we both had extreme
>> unluck with our drives, becau
On Nov 10, 2009, at 1:25 AM, Orvar Korvar wrote:
Does this mean that there are no driver changes in marvell88sx2,
between b125 and b126? If no driver changes, then it means that we
both had extreme unluck with our drives, because we both had
checksum errors? And my discs were brand new.
Hi Orvar,
Correct, I don't see any marvell8sx2 driver changes between b125-126.
So far, only you and Tim are reporting these issues.
Generally, we see bugs filed by the internal test teams if they see
similar problems.
I will try to reproduce the RAIDZ checksum errors separately from the
marve
Does this mean that there are no driver changes in marvell88sx2, between b125
and b126? If no driver changes, then it means that we both had extreme unluck
with our drives, because we both had checksum errors? And my discs were brand
new.
How probable is this? Something is weird here. What is
On Mon, Nov 9, 2009 at 2:51 PM, Cindy Swearingen
wrote:
> Hi,
>
> I can't find any bug-related issues with marvell88sx2 in b126.
>
> I looked over Dave Hollister's shoulder while he searched for
> marvell in his webrevs of this putback and nothing came up:
>
> > driver change with build 126?
> not
Hi,
I can't find any bug-related issues with marvell88sx2 in b126.
I looked over Dave Hollister's shoulder while he searched for
marvell in his webrevs of this putback and nothing came up:
> driver change with build 126?
not for the SATA framework, but for HBAs there is:
http://hub.opensolaris.
This is from build 125.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I think you can work out the files for the driver by looking here:
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/pkgdefs/SUNWmv88sx/prototype_i386
So the 32 bit driver is:
kernel/drv/marvell88sx
And the 64 bit driver is:
kernel/drv/amd64/marvell88sx
It a pity that the marvel
On Sun, Nov 8, 2009 at 9:47 AM, Orvar Korvar wrote:
> Great! So if I want another build, for instance b125, I just change step
> 10?
> 10) pkg -R /mnt install ent...@0.5.11-0.125
> Yes?
>
> What is this "0.5.11" thing? Should that be changed too, if I try to
> install b125? Like "0.5.12-0.125"?
>
Great! So if I want another build, for instance b125, I just change step 10?
10) pkg -R /mnt install ent...@0.5.11-0.125
Yes?
What is this "0.5.11" thing? Should that be changed too, if I try to install
b125? Like "0.5.12-0.125"?
--
This message posted from opensolaris.org
_
> "I can't boot into an older version because the last
> version I had was b118 which doesn't have zfs version
> 19 support. I've been looking to see if there's a
> way to downgrade via IPS but that's turned up a lot
> of nothing."
>
> If someone can tell me which files are needed for the
> drive
"I can't boot into an older version because the last version I had was b118
which doesn't have zfs version 19 support. I've been looking to see if there's
a way to downgrade via IPS but that's turned up a lot of nothing."
If someone can tell me which files are needed for the driver I can extrac
I saw the same checksum error problem when I booted into b126. I havent dared
try b126 again, I use b125 now, without problems. Here is my hardware
Intel Q9450 + P45 Gigabyte EP45-DS3P motherboard + Ati 4850
I have the same AOC SATA controller card. And some Samsung Spinpoint F1, 1TB
drives. Bran
On Sat, Nov 7, 2009 at 12:02 PM, Cindy Swearingen
wrote:
> Hi Tim and all,
>
> I believe you are saying that marvell88sx2 driver error messages started
> in build 126, along with new disk errors in RAIDZ pools.
>
> Is this correct? If so, please send me the following information:
>
Yes.
>
> 1. H
RAIDZ pools
include your zpool status output.
I'm not the right person to be diagnosing driver-level issues but I will
investigate.
Thanks,
Cindy
- Original Message -
From: Tim Cook
Date: Saturday, November 7, 2009 10:08 am
Subject: Re: [zfs-discuss] marvell88sx2 driver build1
On Sat, Nov 7, 2009 at 4:27 AM, Orvar Korvar wrote:
> Ok, so you changed drives and you still see errors? Are the drives brand
> new or used? What kind of drives, which brand? 2TB? And if you reboot into
> an earlier build such as b125 you dont see any errors, right?
>
Brand new. I've tried both
Ok, so you changed drives and you still see errors? Are the drives brand new or
used? What kind of drives, which brand? 2TB? And if you reboot into an earlier
build such as b125 you dont see any errors, right?
Right now I am running b125. I dont dare to run b126, if your observation is
correct
On Mon, Nov 2, 2009 at 6:34 AM, Orvar Korvar wrote:
> I have the same card and might have seen the same problem. Yesterday I
> upgraded to b126 and started to migrate all my data to 8 disc raidz2
> connected to such a card. And suddenly ZFS reported checksum errors. I
> thought the drives were fa
I have the same card and might have seen the same problem. Yesterday I upgraded
to b126 and started to migrate all my data to 8 disc raidz2 connected to such a
card. And suddenly ZFS reported checksum errors. I thought the drives were
faulty. But you suggest the problem could have been the drive
I've sent this to the driver list as well, but since the zfs folks tend to
be intimately involved with the marvell driver stack, I figured I'd give you
guys a shot too.
Does anyone happen to know if there was a driver change with build 126? I
had a pool that was 2x5+1 raidz vdev's. I moved all
26 matches
Mail list logo
