Date: Wed, 20 Jul 2011 23:47:32 +0300 From: Oleksandr Dudinskyi <dudinskyj@gmail.com> To: soc-status@freebsd.org Subject: Status report Message-ID: <CACOVGaDe8hpoY23p7-F=WwwYfPVmZ_887WZM4sDgQw89pexC8g@mail.gmail.com> In-Reply-To: <CACOVGaAtiR7UE2dmxTSaVB=GPst5QGmWt1zv%2BbHPTmZhU5DFCQ@mail.gmail.com> References: <BANLkTimwNyQ-RyrDKvDusuuw9%2BPFrwwotA@mail.gmail.com> <BANLkTimUOfUOcwS_0-i=99shm5RqXO7SUw@mail.gmail.com> <CACOVGaAWVvAgZ8vsTf5_QbPaE-6gJWVzfZS7YtLCo1sCxRb7VA@mail.gmail.com> <CACOVGaAtiR7UE2dmxTSaVB=GPst5QGmWt1zv%2BbHPTmZhU5DFCQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Currently, I work on schedule , I printed the information of disk error in utility iostat option -E. While only displays four types of errors.. Further analysis will give me the opportunity to identify other types of disk errors. In this week I identified fifth type of error, which includes errors that occurred during the request management / control to disk device.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACOVGaDe8hpoY23p7-F=WwwYfPVmZ_887WZM4sDgQw89pexC8g>