Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261487AbVE3L6D (ORCPT ); Mon, 30 May 2005 07:58:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261494AbVE3L6D (ORCPT ); Mon, 30 May 2005 07:58:03 -0400 Received: from [81.2.110.250] ([81.2.110.250]:8150 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S261487AbVE3L57 (ORCPT ); Mon, 30 May 2005 07:57:59 -0400 Subject: Re: RAID-5 design bug (or misfeature) From: Alan Cox To: Mikulas Patocka Cc: Bernd Eckenfels , Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1117454144.2685.174.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 30 May 2005 12:55:47 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1241 Lines: 26 On Llu, 2005-05-30 at 03:47, Mikulas Patocka wrote: > > In article you wrote: > > > I think Linux should stop accessing all disks in RAID-5 array if two disks > > > fail and not write "this array is dead" in superblocks on remaining disks, > > > efficiently destroying the whole array. It discovered the disks had failed because they had outstanding I/O that failed to complete and errorred. At that point your stripes *are* inconsistent. If it didn't mark them as failed then you wouldn't know it was corrupted after a power restore. You can then clean it fsck it, restore it, use mdadm as appropriate to restore the volume and check it. > But root disk might fail too... This way, the system can't be taken down > by any single disk crash. It only takes on disk in an array to short 12v and 5v due to a component failure to total the entire disk array, and with both IDE and SCSI a drive fail can hang the entire bus anyway. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/