![]() # faulty drive and run "zpool scrub" on the affected volume after resilvering. ![]() # are reported an email will be sent out. # on all volumes and all drives using "zpool status". # Errors - Check the columns for READ, WRITE and CKSUM (checksum) drive errors # optimal set of sequential writes and write performance is severely impacted.Ĭapacity= $(/sbin/zpool list -H -o capacity )ĮmailSubject= " $emailSubject - Capacity Exceeded " # ZFS will be have to randomly write blocks. If the pool is at capacity and space limited, This method is true only when the pool has # sequential free blocks first and when the uberblock has been updated the new # probably set the warning closer to 95%. If you have a 60TB raid-z2 array then you can Monitoring hard disk health and temperature. # percentage really depends on how large your volume is. The Autopsy Forensic Browser is a graphical interface to the command line digital investigation analysis. # Capacity - Make sure pool capacities are below 80% for best performance. # any keyword signifying a degraded or broken array.Ĭondition= $(/sbin/zpool status | egrep -i '(DEGRADED|FAULTED|OFFLINE|UNAVAIL|REMOVED|FAIL|DESTROYED|corrupt|cannot|unrecover) ' ) # Health - Check if all zfs volumes are in good condition. ![]() # Peter van der Does - When a scrub is needed the email subject line only has to inform us once.ĮmailSubject= " `hostname ` - ZFS pool - HEALTH check " # I prefer to know a script has run even when there is no problem. # Peter van der Does - Always send an email, even if there is no problem. For now, in FreeBSD 9, we will make our own checks and run this script # 10 there is supposed to be a ZFSd daemon to monitor the health of the ZFS # Check health of ZFS volumes and drives. The disk health information is provided by SMART and is displayed with smartctl.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |