Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753428Ab0BNV2U (ORCPT ); Sun, 14 Feb 2010 16:28:20 -0500 Received: from relay02.digicable.hu ([92.249.128.188]:33199 "EHLO relay02.digicable.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753021Ab0BNV2S (ORCPT ); Sun, 14 Feb 2010 16:28:18 -0500 X-Greylist: delayed 704 seconds by postgrey-1.27 at vger.kernel.org; Sun, 14 Feb 2010 16:28:17 EST Date: Sun, 14 Feb 2010 22:28:11 +0100 From: Gabor Gombas To: Asdo Cc: Henrique de Moraes Holschuh , Michael Evans , Volker Armin Hemmann , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org Subject: Re: Linux mdadm superblock question. Message-ID: <20100214212811.GB15313@twister.home> Mail-Followup-To: Asdo , Henrique de Moraes Holschuh , Michael Evans , Volker Armin Hemmann , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org References: <201002140251.59668.volkerarmin@googlemail.com> <4877c76c1002132002s20d942c3i7cee5418cdcf369c@mail.gmail.com> <20100214193406.GA15722@khazad-dum.debian.net> <4B786154.8090103@shiftmail.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B786154.8090103@shiftmail.org> X-Copyright: Forwarding or publishing without permission is prohibited. X-Original: 94.21.92.161 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1340 Lines: 30 On Sun, Feb 14, 2010 at 09:47:16PM +0100, Asdo wrote: > 1.x autodetection worked great for me in initramfs. Basically you > only need /etc/mdadm/mdadm.conf copied to initramfs (via > update-initramfs), There is no autodetection with 1.1. Once you have mdadm.conf you have pretty hard rules about what to look for and how to assemble it - ie. there is not much left to "auto" detect. Real autodetection would mean there is _no_ such information available, and you figure out everything by just looking at the devices you find. > initramfs procedure. > Also consider 1.x allows to choose which arrays are autoassembled > (hostname written in the array name equal to hostname in the machine > or specified in mdadm.conf): this is more precise than 0.9 which > autoassembles all, I think. And also causes much more pain when you install machines on an internal network where it gets a random name (in fact all new machines get the same temporary name), then it is moved to its real location and reconfigured with its real name. And you wonder why your arrays aren't assembled any more... Gabor -- 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/