From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Webb Subject: Re: MD/RAID time out writing superblock Date: Thu, 17 Sep 2009 14:37:20 +0100 Message-ID: <20090917133720.GM5418@arachsys.com> References: <20090907114442.GG18831@arachsys.com> <20090907115927.GU8710@arachsys.com> <20090909120218.GB21829@arachsys.com> <4AADF3C4.5060004@kernel.org> <4AADF471.2020801@suse.de> <4AAE3B9A.2060306@rtr.ca> <4AAE3F86.8090804@suse.de> <4AAE524C.2030401@rtr.ca> <20090916231921.GL1924@arachsys.com> <4AB239C8.2020203@rtr.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from alpha.arachsys.com ([91.203.57.7]:53027 "EHLO alpha.arachsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754211AbZIQNhW (ORCPT ); Thu, 17 Sep 2009 09:37:22 -0400 Content-Disposition: inline In-Reply-To: <4AB239C8.2020203@rtr.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Mark Lord Cc: Tejun Heo , linux-scsi@vger.kernel.org, Ric Wheeler , Andrei Tanas , NeilBrown , linux-kernel@vger.kernel.org, IDE/ATA development list , Jeff Garzik , Mark Lord Mark Lord writes: > Yes. Is this still happening from time to time now? Hi Mark. We're still seeing the flush timeouts (0xea) with accompanying errors, but not the IDENTIFYs anymore. We now don't have smartd nor smartctl on the systems, and there's nothing else running in userspace that accesses the drives other than via block reads and writes via the md arrays. Cheers, Chris.