On Tue, Nov 10, 2009 at 5:15 PM, Tim Cook <t...@cook.ms> wrote:
>
>
> On Tue, Nov 10, 2009 at 10:55 AM, Richard Elling <richard.ell...@gmail.com
> > 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, because we both had checksum errors? And my discs
>>> were brand new.
>>>
>>
>> There are other drivers in the software stack that may have changed.
>> -- richard
>>
>>
>>
>>> How probable is this? Something is weird here. What is your opinion on
>>> this? Should we agree that there was a hardware error, and it was just a
>>> coincidence?
>>>
>>
>
> So... I do appear to have reached somewhat of a truce with the system and
> b126 at the moment. I'm now going through and replacing the last of my old
> maxtor 300GB drives with brand new hitachi 1TB drives. One thing I'm
> noticing is a lot of checksum errors being generated during the resilver.
> Is this normal? Furthermore, since I see "no known data errors", is it safe
> to assume it's all being corrected, and I'm not losing any data? I still do
> have a separate copy of this data on a box at work that should be completely
> consistent... but I will need to re-purpose that storage soon, and will be
> without a known good backup for a while (I know, I know). I'd rather do a
> fresh zfs send/receive than find out 6 months from now I lost something.
>
> pool: fserv
> state: DEGRADED
> status: One or more devices is currently being resilvered. The pool will
> continue to function, possibly in a degraded state.
> action: Wait for the resilver to complete.
> scrub: resilver in progress for 0h8m, 0.89% done, 15h14m to go
>
> config:
>
> NAME STATE READ WRITE CKSUM
> fserv DEGRADED 0 0 0
> raidz2-0 DEGRADED 0 0 0
> c8t0d0 ONLINE 0 0 0
> c8t1d0 ONLINE 0 0 0
> c8t2d0 ONLINE 0 0 0
>
> c8t3d0 ONLINE 0 0 0
> c8t4d0 ONLINE 0 0 0
> c8t5d0 ONLINE 0 0 0
> c7t0d0 ONLINE 0 0 0
> c7t1d0 ONLINE 0 0 0
> c7t2d0 ONLINE 0 0 0
> replacing-9 DEGRADED 0 0 161K
> 14274451003165180679 FAULTED 0 0 0 was
> /dev/dsk/c7t3d0s0/old
> c7t3d0 ONLINE 0 0 0 2.05G
> resilvered
>
> c7t4d0 ONLINE 0 0 0
> c7t5d0 ONLINE 0 0 0
> spares
> c7t6d0 AVAIL
>
>
> errors: No known data errors
>
>
> --Tim
>
>
Anyone? It's up to 7.35M checksum errors and it's rebuilding extremely
slowly (as evidenced by the 10 hour time). The errors are only showing on
the "replacing-9" line, not the individual drive.
pool: fserv
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scrub: resilver in progress for 6h56m, 39.61% done, 10h34m to go
config:
NAME STATE READ WRITE CKSUM
fserv DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
c8t0d0 ONLINE 0 0 0
c8t1d0 ONLINE 0 0 0
c8t2d0 ONLINE 0 0 0
c8t3d0 ONLINE 0 0 0
c8t4d0 ONLINE 0 0 0
c8t5d0 ONLINE 0 0 0
c7t0d0 ONLINE 0 0 0
c7t1d0 ONLINE 0 0 0
c7t2d0 ONLINE 0 0 0
replacing-9 DEGRADED 0 0 7.35M
14274451003165180679 FAULTED 0 0 0 was
/dev/dsk/c7t3d0s0/old
c7t3d0 ONLINE 0 0 0 91.9G
resilvered
c7t4d0 ONLINE 0 0 0
c7t5d0 ONLINE 0 0 0
spares
c7t6d0 AVAIL
errors: No known data errors
--Tim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
