linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Michal Soltys <soltys@ziu.info>,
	linux-raid@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: How do I tell if my partition is aligned for a 64k/RAID-6?
Date: Sat, 27 Dec 2008 08:58:22 -0500	[thread overview]
Message-ID: <20081227135822.GI6284@josefsipek.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0812270850490.15403@p34.internal.lan>

On Sat, Dec 27, 2008 at 08:53:21AM -0500, Justin Piszcz wrote:
> Why bother partitioning?  I also run a Linux SW RAID1 on the host, as you 
> know the drive letters can change when working on a server.
>
> Example: Before I created the array (RAID-6), my disks were /dev/sda,  
> /dev/sdb and /dev/sdc (spare), the RAID-6 was /dev/sdd.  After reboot,  
> /dev/sdd became /dev/sda and /dev/sd[a-c] became /dev/sd[b-d].
>
> In lilo.conf I had:
> raid-extra-boot="/dev/sda,/dev/sdb"
>
> If I ran LILO and forgot to fix the lilo.conf to reflect the new drive  
> mappings:
> raid-extra-boot="/dev/sdb,/dev/sdc"
>
> I could be at risk of ruining the partition?

Hrm...interesting point. LILO could mess up the superblock in sector 0.

> I try to avoid such situations when possible, to be safe.

:)

I don't know how LILO would handle it, but I would try to use
/dev/disk/by-*/* instead of the rather unstable /dev/sd* names.

Just my 0.02 cents.

Jeff.

-- 
Keyboard not found!
Press F1 to enter Setup

  reply	other threads:[~2008-12-27 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-25 13:31 How do I tell if my partition is aligned for a 64k/RAID-6? Justin Piszcz
2008-12-25 22:53 ` Justin Piszcz
2008-12-25 23:02 ` Michal Soltys
2008-12-25 23:46   ` Justin Piszcz
2008-12-27 13:38     ` Josef 'Jeff' Sipek
2008-12-27 13:53       ` Justin Piszcz
2008-12-27 13:58         ` Josef 'Jeff' Sipek [this message]
2008-12-27 14:05           ` Justin Piszcz
2008-12-27 14:20           ` John Robinson

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=20081227135822.GI6284@josefsipek.net \
    --to=jeffpc@josefsipek.net \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=soltys@ziu.info \
    --cc=xfs@oss.sgi.com \
    /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).