Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Feb 2013 21:51:03 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Mikolaj Golub <trociny@FreeBSD.org>
Cc:        Chad M Stewart <cms@balius.com>, freebsd-questions@freebsd.org
Subject:   Re: HAST - detect failure and restore avoiding an outage?
Message-ID:  <20130223205103.GN1377@garage.freebsd.pl>
In-Reply-To: <20130221220042.GA2900@gmail.com>
References:  <E3C8C9A2-712E-4925-995A-0471CCD3515B@balius.com> <20130221220042.GA2900@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--jh06fhy6YTawvwPV
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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:
>=20
> http://people.freebsd.org/~trociny/hast.stat_error.1.patch
>=20
> hastctl output:
>=20
>   role: secondary
>   provname: test
>   localpath: /dev/md102
>   extentsize: 2097152 (2.0MB)
>   keepdirty: 0
>   remoteaddr: kopusha:7771
>   replication: memsync
>   status: complete
>   dirty: 0 (0B)
>   statistics:
>     reads: 0
>     writes: 366
>     deletes: 0
>     flushes: 0
>     activemap updates: 0
>     local i/o errors: 269
>=20
> Pawel, what do you think about this patch?


I'm fine with the patchi except for missing breaks in switch added to
hastd/primary.c.

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
separately, eg.

	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?

--=20
Pawel Jakub Dawidek                       http://www.wheelsystems.com
FreeBSD committer                         http://www.FreeBSD.org
Am I Evil? Yes, I Am!                     http://tupytaj.pl

--jh06fhy6YTawvwPV
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlEpK7cACgkQForvXbEpPzRiWwCfadfw1ncKUdyvM7J/6ObjAbJO
FYgAoItNIzmXP3U0FRWi0ynG+hSEijKI
=sw5K
-----END PGP SIGNATURE-----

--jh06fhy6YTawvwPV--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130223205103.GN1377>