Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 3 Oct 2002 09:18:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 3 Oct 2002 09:18:22 -0400 Received: from unthought.net ([212.97.129.24]:9445 "EHLO mail.unthought.net") by vger.kernel.org with ESMTP id ; Thu, 3 Oct 2002 09:18:19 -0400 Date: Thu, 3 Oct 2002 15:23:50 +0200 From: Jakob Oestergaard To: Roy Sigurd Karlsbakk Cc: Kernel mailing list , linux-raid@vger.kernel.org Subject: Re: AARGH! Please help. IDE controller fsckup Message-ID: <20021003132349.GE7350@unthought.net> Mail-Followup-To: Jakob Oestergaard , Roy Sigurd Karlsbakk , Kernel mailing list , linux-raid@vger.kernel.org References: <200210021516.46668.roy@karlsbakk.net> <200210031225.11283.roy@karlsbakk.net> <20021003114020.GD7350@unthought.net> <200210031513.28459.roy@karlsbakk.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200210031513.28459.roy@karlsbakk.net> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2815 Lines: 76 On Thu, Oct 03, 2002 at 03:13:28PM +0200, Roy Sigurd Karlsbakk wrote: > > > I have used presistent superblocks, but md0,1,2,3 will be differently > > > ordered if I change the disk order... At least I think so. It surely > > > didn't work. > > > > No. md0 would stay md0. This is another effect of using superblocks, > > and in fact this is also (ironically) more or less the only argument > > *against* using them :) > > > > (Imagine inserting a disk which knows that it is disk 0 of md0 into some > > machine that already has a perfectly fine md0 running) > > ok. so. theoretically - as long as the system finds all 16 drives, I should be > able to shuffle them around and attach them to whichever controller there is? > right? It will not reattach your disks (you need to move cables to do that), but it will know "First disk of md0" from "Second disk of md0" regardless of whether those disks are /dev/hda or /dev/sdg. You can shuffle your disks around as much as you please. When the RAID code looks at your disks, it will read their superblocks and correctly make the first disk of md0 the first disk of md0, and so forth, regardless of the actual device name of the disk. > > ok. > > now, I've replaced the faulty controller, and booting up. the new controller > is also (like the old one) a CMD649... > RAID doesn't care about controllers. RAID without persistent superblocks cares about disk device names. RAID with persistent superblocks don't care about disk device names. > h?? ?h? > > it works. but it surely didn't work last time... > Good for you :) > thanks > > > > But ... with persistent superblock - is it possible to fsckup the raid? > > > > You're root, it is indeed possible :) > > er - yes. I more meant like 'automagically' It will only automagically screw up your arrays if you shuffle disks between machines (mix several RAID arrays from other systems in one system) (you can of course move all your disks to one new machine, if it has none of it's original RAIDed disks left). Just don't mix disks with persistent superblocks from multiple machines into one single machine. Unless you know exactly what you're doing. -- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob ?stergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............: - 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/