From: Jakob Oestergaard <jakob@unthought.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-raid@vger.kernel.org
Subject: Re: AARGH! Please help. IDE controller fsckup
Date: Thu, 3 Oct 2002 15:23:50 +0200 [thread overview]
Message-ID: <20021003132349.GE7350@unthought.net> (raw)
In-Reply-To: <200210031513.28459.roy@karlsbakk.net>
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-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-10-03 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200210021516.46668.roy@karlsbakk.net>
[not found] ` <200210031225.11283.roy@karlsbakk.net>
[not found] ` <20021003114020.GD7350@unthought.net>
2002-10-03 13:13 ` AARGH! Please help. IDE controller fsckup Roy Sigurd Karlsbakk
2002-10-03 13:23 ` Jakob Oestergaard [this message]
2002-10-03 20:05 ` Andre Hedrick
2002-10-03 20:52 ` Jakob Oestergaard
2002-10-05 15:42 ` Roy Sigurd Karlsbakk
2002-10-05 16:51 ` Adam Luter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021003132349.GE7350@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=roy@karlsbakk.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).