From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Landman Subject: Ok, dumb question time ... Date: Fri, 08 Oct 2010 00:20:35 -0400 Message-ID: <4CAE9C13.3060002@scalableinformatics.com> Reply-To: landman@scalableinformatics.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Sender: linux-raid-owner@vger.kernel.org To: linux-raid@vger.kernel.org List-Id: linux-raid.ids Not having much luck with this. Let me explain ... Imagine we have a RAID1 with 3 elements. It was originally a RAID1 with 2 elements, and we added a 3rd using mdadm /dev/md0 --add /dev/loop1 What I want to do is conceptually very simple. I want to permanently remove loop1, without having the array become dirty, or degraded. That is, I would like mdadm /dev/md0 --fail /dev/loop1 --remove /dev/loop1 to result in a clean array with two members. It doesn't. The array is marked as being in the "clean, degraded" state. Which, as it is the root file system array, has the unfortunate side effect of not allowing the RAID1 to properly assemble at boot (that degraded state). So ... can I force the array to either remove the extra unneeded loop1 device, and update its metadata properly ... or force it into a clean, active state without the loop1 device, or force the assembly on boot to occur regardless of what it thinks it should have? This is quite disconcerting ... I thought it would be simple. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: landman@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615