From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Jakob Oestergaard <jakob@unthought.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:13:28 +0200 [thread overview]
Message-ID: <200210031513.28459.roy@karlsbakk.net> (raw)
In-Reply-To: <20021003114020.GD7350@unthought.net>
> > 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?
ok.
now, I've replaced the faulty controller, and booting up. the new controller
is also (like the old one) a CMD649...
hæ?
it works. but it surely didn't work last time...
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'
> But you would not need to perform any of the special operations that you
> need to now.
>
> Persistent superblocks saves you from a number of "bad" situations you
> can encounter with normal production systems (such as replacing a
> controller or moving disks around).
>
> One should be careful when moving disks with persistent superblocks
> between systems though. You don't want the kernel to autodetect the
> "wrong" md0 on boot :) I consider this problem nonexistent in the
> production environment that I administer, but I know that some people
> feel differently about it. You should consider these pros and cons in
> relation to your environment and make a decision based on that.
--
Roy Sigurd Karlsbakk, Datavaktmester
ProntoTV AS - http://www.pronto.tv/
Tel: +47 9801 3356
Computers are like air conditioners.
They stop working when you open Windows.
-
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 parent reply other threads:[~2002-10-03 13:13 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 ` Roy Sigurd Karlsbakk [this message]
2002-10-03 13:23 ` AARGH! Please help. IDE controller fsckup Jakob Oestergaard
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=200210031513.28459.roy@karlsbakk.net \
--to=roy@karlsbakk.net \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/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).