On Friday, 23 September 2016 7:14:15 PM AEST Craig Sanders via luv-main wrote:
> and for logging and graphing all sorts of info about systems (disk space,
> memory utilisation, cpu load, network traffic etc) and the services they're
> running (e.g. postgres/mysql query load, VMs/containers
On Fri, Sep 23, 2016 at 04:06:42PM +1000, russ...@coker.com.au wrote:
> The Nagios model is to have a single very complex monitoring system while
> the mon model tends towards multiple simple installations. Nagios has a
> nrpe daemon on each monitored server while with Mon you have Mon on each
>
On Friday, 23 September 2016 11:24:41 AM AEST Peter Ross via luv-main wrote:
> For the messages: FreeBSD has a sysctl vfs.zfs.debug. This sysctl approach
> was ported to Linux, my Google 'research' (e.g.
> http://askubuntu.com/questions/228386/how-do-you-apply-performance-tuning-se
>
Hi Russell,
I would assume that the resilvering is related to the checksum errors. From
the zpool(8) manpage:
Scrubbing and resilvering are very similar operations. The difference
is that resilvering only examines data that ZFS knows to be out of
date (for example, when attaching a new device to
Below is part of the output of "zpool status". It seems that sdr is
defective, it has a steadily increasing number of checksum errors.
Would the "resilvered 763M" part be about the 121 checksum errors? If so does
that mean each checksum error required resilvering on average 6M of data?
The
