HAST - detect failure and restore avoiding an outage?
Pawel Jakub Dawidek
pjd at FreeBSD.org
Sat Feb 23 20:49:55 UTC 2013
On Fri, Feb 22, 2013 at 12:00:43AM +0200, Mikolaj Golub wrote:
> It looks currently logs are only way to detect errors from hastd side.
> Here is a patch that adds local i/o error statistics, accessable avia
> hastctl output:
> role: secondary
> provname: test
> localpath: /dev/md102
> extentsize: 2097152 (2.0MB)
> keepdirty: 0
> remoteaddr: kopusha:7771
> replication: memsync
> status: complete
> dirty: 0 (0B)
> reads: 0
> writes: 366
> deletes: 0
> flushes: 0
> activemap updates: 0
> local i/o errors: 269
> Pawel, what do you think about this patch?
I'm fine with the patchi except for missing breaks in switch added to
I'm also wondering... You count all those errors separately just to
print them as one number. If we do that already let's print them
local i/o errors: read(0), write(3), delete(5), flush(9)
BTW. Why not to count activemap update errors as write and flush errors?
Pawel Jakub Dawidek http://www.wheelsystems.com
FreeBSD committer http://www.FreeBSD.org
Am I Evil? Yes, I Am! http://tupytaj.pl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the freebsd-questions