Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932176AbWHHJi2 (ORCPT ); Tue, 8 Aug 2006 05:38:28 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932173AbWHHJi2 (ORCPT ); Tue, 8 Aug 2006 05:38:28 -0400 Received: from mx1.redhat.com ([66.187.233.31]:8841 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S932168AbWHHJi1 (ORCPT ); Tue, 8 Aug 2006 05:38:27 -0400 To: linux-raid , linux-kernel Subject: modifying degraded raid 1 then re-adding other members is bad From: Alexandre Oliva Organization: Red Hat OS Tools Group Date: Tue, 08 Aug 2006 06:38:19 -0300 Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b27 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1168 Lines: 27 Assume I have a fully-functional raid 1 between two disks, one hot-pluggable and the other fixed. If I unplug the hot-pluggable disk and reboot, the array will come up degraded, as intended. If I then modify a lot of the data in the raid device (say it's my root fs and I'm running daily Fedora development updates :-), which modifies only the fixed disk, and then plug the hot-pluggable disk in and re-add its members, it appears that it comes up without resyncing and, well, major filesystem corruption ensues. Is this a known issue, or should I try to gather more info about it? This happened with 2.6.18rc3-git[367] (not sure which), plus Fedora development patches. -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Secretary for FSF Latin America http://www.fsfla.org/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - 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/