From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Fedyk Subject: Re: recovery of hosed raid5 array Date: Sun, 26 Oct 2003 11:40:51 -0800 Sender: linux-raid-owner@vger.kernel.org Message-ID: <20031026194051.GA4511@matchmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: To: dean gaudet Cc: Jason Lunz , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Sun, Oct 12, 2003 at 10:39:50AM -0700, dean gaudet wrote: > > > On Sun, 12 Oct 2003, Jason Lunz wrote: > > > What was foolish was me provoking /dev/hde by asking it to report > > diagnostics with smartctl at the same time the array was rebuilding > > /dev/hdg. Even if something _was_ wrong with hde, it wouldn't have > > helped me to find out then during the rebuild. Had the resync completed, > > I'd have all my data now and one dead disk. > > querying SMART shouldn't cause this to happen -- but i've seen it occur > with a promise controller and maxtor disks. i used to query the SMART > data once a night just to have a log. then i switched it to once every 5 > minutes so i could graph the drive temperature... and when i went to once > every 5 minutes the system became unstable. the kernel would randomly > lose the ability to talk to a disk. the problem would go away after a > reboot. i assume it was some sort of race condition. 1. Were they maxtor 160GB 8MB cache drives? 2. Is there any package that will take one drive in a raid1/5 array offline, and run badblocks on it?