Date: Tue, 14 Feb 2012 06:37:10 -0800 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Mike Tancsa <mike@sentex.net> Cc: Alexander Motin <mav@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: siisch1: Error while READ LOG EXT Message-ID: <20120214143710.GA99700@icarus.home.lan> In-Reply-To: <4F3A7005.7000909@sentex.net> References: <4F32FB5E.7050102@FreeBSD.org> <4F33DB75.1080202@sentex.net> <20120209152240.GA95470@icarus.home.lan> <4F33F056.6070300@sentex.net> <20120209163415.GA96451@icarus.home.lan> <4F34124F.9090808@sentex.net> <4F358DB6.4030203@sentex.net> <20120211012753.GA29375@icarus.home.lan> <4F35C7D8.5050707@sentex.net> <4F3A7005.7000909@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 14, 2012 at 09:30:29AM -0500, Mike Tancsa wrote: > On 2/10/2012 8:43 PM, Mike Tancsa wrote: > > On 2/10/2012 8:27 PM, Jeremy Chadwick wrote: > >> Mike, > >> > >> I wanted to make you aware of this commit that just came through: > >> > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cam/ata/ata_da.c > > > > Thanks, I did see that. I was going to wait until Monday to csup up > > once all the weekend level zeros are done. The prior kernels from Nov > > 28th never saw these READ LOG EXT errors on either of these 2 big zfs boxes > > > So far so good. Unfortunately, I had to make 2 changes to the box > showing the problem the most. I changed the cable (the new one does seem > to fit more snug) as well as updated the code. I havent done many level > 0 dumps to it (the real test will be the weekend), but so far so good. > On the other box that did show the same READ LOG EXT error, I also > updated the kernel, but made no hardware changes. It too has not yet > shown any errors since the upgrade. > > I changed the cable at 8am local time yesterday, and I take snapshots of > smartctl at 5am Cool. > I did see this error increase in 24hrs, but that was on a disk that was > off the motherboard. Perhaps a new cable for it too. > > < 0x000a 2 12 Device-to-host register FISes sent due to a > COMRESET > --- > > 0x000a 2 6 Device-to-host register FISes sent due to a > COMRESET This ID tracks the number of times an actual communication reset command was sent from the drive to the controller via a FIS packet. This is at the SATA layer, not the ATA command layer. It's completely normal/okay for a drive to have this number increase, especially if the machine is shut off, force-reset (via reset button), or in some cases simply soft rebooted. Nothing to worry about here; no need to adjust cables or otherwise. Values 6, 12, etc. are all perfectly reasonable and will vary from system to system based on use. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120214143710.GA99700>