From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Cameron, Steve" <Steve.Cameron@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: RE: [RFC] Multi-path IO in 2.5/2.6 ?
Date: 10 Sep 2002 19:48:26 +0100 [thread overview]
Message-ID: <1031683706.1537.112.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <45B36A38D959B44CB032DA427A6E10640167D03E@cceexc18.americas.cpqcorp.net>
On Tue, 2002-09-10 at 17:34, Cameron, Steve wrote:
> 1. Install normally to disk-A, remove disk-A from the system.
> 2. Install normally to disk-B. Install disk-A into the system.
> and boot from disk-B. (now I can safely copy from disk-A, which has
> no actively mounted partitions.)
> 3. Create multipath devices on disk-C, one for each partition.
> The partitions are bigger than those on disk-A, to allow for md to
> put its data at the end.
> 4. Copy, (using dd) the partitions from disk-A to the md devices.
>
> 5. mount the md devices, and chroot to the md-root device.
> Try to figure out how to run lilo to make booting from disk-C possible
> also, initrd modifications to insmod multipath.o, mount the md devices,
> etc. This part, (making lilo work) I never was able to figure out.
>
> Would boot up and say "LI" then stop... or various other problems
> that I can't quite recall now. (this was a couple weeks ago)
Sounds like geometry mismatches. You need to be sure that the BIOS disk
mappings are constant and that the geometries match. The former can be a
big problem. If your failed drive falls off the scsi bus scan then your
BIOS disk 0x80 becomes the second disk not the first and life starts to
go down hill from that moment.
next prev parent reply other threads:[~2002-09-10 18:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 16:34 Cameron, Steve
2002-09-10 18:48 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-10 14:43 Cameron, Steve
2002-09-10 15:05 ` Alan Cox
2002-09-10 14:06 Cameron, Steve
2002-09-10 14:25 ` Alan Cox
2002-09-09 17:58 Ulrich Weigand
2002-09-09 14:57 James Bottomley
2002-09-09 16:56 ` Patrick Mansfield
2002-09-09 17:34 ` James Bottomley
2002-09-09 18:40 ` Mike Anderson
2002-09-10 13:02 ` Lars Marowsky-Bree
2002-09-10 16:03 ` Patrick Mansfield
2002-09-10 16:27 ` Mike Anderson
2002-09-10 0:08 ` Patrick Mansfield
2002-09-10 7:55 ` Jeremy Higdon
2002-09-10 13:04 ` Lars Marowsky-Bree
2002-09-10 16:20 ` Patrick Mansfield
2002-09-10 13:16 ` Lars Marowsky-Bree
2002-09-10 19:26 ` Patrick Mansfield
2002-09-11 14:20 ` James Bottomley
2002-09-11 19:17 ` Lars Marowsky-Bree
2002-09-11 19:37 ` James Bottomley
2002-09-11 19:52 ` Lars Marowsky-Bree
2002-09-12 1:15 ` Bernd Eckenfels
2002-09-11 21:38 ` Oliver Xymoron
2002-09-11 20:30 ` Doug Ledford
2002-09-11 21:17 ` Mike Anderson
2002-09-10 17:21 ` Patrick Mochel
2002-09-10 18:42 ` Patrick Mansfield
2002-09-10 19:00 ` Patrick Mochel
2002-09-10 19:37 ` Patrick Mansfield
2002-09-11 0:21 ` Neil Brown
2002-09-09 10:49 Lars Marowsky-Bree
2002-09-09 12:23 ` Alan Cox
2002-09-10 10:30 ` Heinz J . Mauelshagen
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=1031683706.1537.112.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Steve.Cameron@hp.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®