linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moshe Yudkowsky <moshe@pobox.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash)
Date: Mon, 04 Feb 2008 05:06:09 -0600	[thread overview]
Message-ID: <47A6F1A1.7030407@pobox.com> (raw)
In-Reply-To: <20080203220158.GC22004@cthulhu.home.robinhill.me.uk>

Robin, thanks for the explanation. I have a further question.

Robin Hill wrote:

> Once the file system is mounted then hdX,Y maps according to the
> device.map file (which may actually bear no resemblance to the drive
> order at boot - I've had issues with this before).  At boot time it maps
> to the BIOS boot order though, and (in my experience anyway) hd0 will
> always map to the drive the BIOS is booting from.

At the time that I use grub to write to the MBR, hd2,1 is /dev/sdc1. 
Therefore, I don't quite understand why this would not work:

grub <<EOF
root(hd2,1)
setup(hd2)
EOF

This would seem to be a command to have the MBR on hd2 written to use 
the boot on hd2,1. It's valid when written. Are you saying that it's a 
command for the MBR on /dev/sdc to find the data on (hd2,1), the 
location of which might change at any time? That's... a  very strange 
way to write the tool. I thought it would be a command for the MBR on 
hd2 (sdc) to look at hd2,1 (sdc1) to find its data, regardless of the 
boot order that caused sdc to be the boot disk.

-- 
Moshe Yudkowsky * moshe@pobox.com * www.pobox.com/~moshe
  "Bring me the head of Prince Charming."
    				-- Robert Sheckley & Roger Zelazny

  reply	other threads:[~2008-02-04 11:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 19:15 RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash) Moshe Yudkowsky
2008-02-03 20:01 ` Robin Hill
2008-02-03 20:46   ` Moshe Yudkowsky
2008-02-03 22:01     ` Robin Hill
2008-02-04 11:06       ` Moshe Yudkowsky [this message]
2008-02-04 11:40         ` Robin Hill
2008-02-03 20:28 ` Michael Tokarev
2008-02-03 20:54   ` Moshe Yudkowsky
2008-02-03 21:04     ` Michael Tokarev
2008-02-04  9:27     ` Michael Tokarev
2008-02-04 10:58       ` Moshe Yudkowsky
2008-02-04 13:52         ` Michael Tokarev
2008-02-04 14:09           ` Justin Piszcz
2008-02-04 14:25             ` Eric Sandeen
2008-02-04 14:42               ` Eric Sandeen
2008-02-04 15:31               ` Moshe Yudkowsky
2008-02-04 16:45                 ` Eric Sandeen
2008-02-04 17:22                   ` Michael Tokarev
2008-02-05 12:31                     ` Linda Walsh
2008-02-04 16:38               ` Michael Tokarev
2008-02-04 19:02                 ` Richard Scobie
2008-02-04 22:27                 ` Justin Piszcz
2008-02-06  1:12                 ` Linda Walsh
2008-02-06  2:12                   ` Michael Tokarev
2008-02-06  9:14                 ` Luca Berra

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=47A6F1A1.7030407@pobox.com \
    --to=moshe@pobox.com \
    --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).