Hi all,
one single disk in a zfs mirror failed permanently throwing errors like
kernel: (ada5:ata10:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84
(ICRC ABRT ) and alike.
The pool itself continued working degraded, smartctl showed a very high
199 UDMA_CRC_Error_Count value, which to my know
Hi,
On 2012.11.09 12:18, H. Ingow wrote:
>
> Hi all,
>
> one single disk in a zfs mirror failed permanently throwing errors like
> kernel: (ada5:ata10:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84
> (ICRC ABRT ) and alike.
>
> The pool itself continued working degraded, smartctl showed a
Thanks, looking forward to MFC!
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/buildworld-fails-on-recent-stable-tp5758273p5759526.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
___
freebsd-stable@freebsd.
On Fri, Nov 09, 2012 at 12:28:11AM +0100, Dimitry Andric wrote:
> ...
> I have also looked at merging the snapshot of 3.2 we now have in head to
> stable/9, but it is also quite some work, so I found a better solution:
> I managed to shrink boot2 by enough bytes to make it fit again.
>
> I committ
- Original Message -
From: "Steven Hartland"
...
I've just had another panic, trace below, but it doesn't seem to be related
to my changes so I'd appreciate your feedback on them as they are for now.
While the lock patch fixes the problems I've seen, its not clear to me
why mfi_tbolt_
On Fri, Nov 09, 2012 at 05:06:03PM -, Steven Hartland wrote:
|
| - Original Message -
| From: "Steven Hartland"
| ...
| >I've just had another panic, trace below, but it doesn't seem to be related
| >to my changes so I'd appreciate your feedback on them as they are for now.
| >
| >Whi
Thanks Dimitry. Confirmed successful build here, too.
--
James.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Fri, Nov 9, 2012 at 3:47 AM, Lucas B. Cohen wrote:
> Hi,
>
> On 2012.11.09 12:18, H. Ingow wrote:
>>
>> Hi all,
>>
>> one single disk in a zfs mirror failed permanently throwing errors like
>> kernel: (ada5:ata10:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84
>> (ICRC ABRT ) and alike.
>>
>>
Hi!
> Still smartctl -a displays a value of 199 UDMA_CRC_Error_Count I reckon
> to be way too high, though ( > 3900 ) .
> So is this value now including errors from previous broken cable ?
> In other words, when, if at all, is the cache smartmontools read from
> flushed and values are to be take
If memory serves me right, Kevin Oberman wrote:
> By the way, I believe that some stats do go up and down, but not
> counters. Like in snmp, counters are never supposed to be reset or
> resettable.
Examples of values that go up and down (actually the only examples I can
think of) are the drive te
10 matches
Mail list logo