Paul Mather wrote:
On May 8, 2019, at 9:59 AM, Michelle Sullivan <[email protected]> wrote:
Paul Mather wrote:
due to lack of space. Interestingly have had another drive die in
the array - and it doesn't just have one or two sectors down it has
a *lot* - which was not noticed by the original machine - I moved
the drive to a byte copier which is where it's reporting 100's of
sectors damaged... could this be compounded by zfs/mfi driver/hba
not picking up errors like it should?
Did you have regular pool scrubs enabled? It would have picked up
silent data corruption like this. It does for me.
Yes, every month (once a month because, (1) the data doesn't change
much (new data is added, old it not touched), and (2) because to
complete it took 2 weeks.)
Do you also run sysutils/smartmontools to monitor S.M.A.R.T.
attributes? Although imperfect, it can sometimes signal trouble
brewing with a drive (e.g., increasing Reallocated_Sector_Ct and
Current_Pending_Sector counts) that can lead to proactive remediation
before catastrophe strikes.
not Automatically
Unless you have been gathering periodic drive metrics, you have no way
of knowing whether these hundreds of bad sectors have happened
suddenly or slowly over a period of time.
no, it something i have thought about but been unable to spend the time on.
--
Michelle Sullivan
http://www.mhix.org/
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[email protected]"
