mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Raid auto-assembly on LDM?
Date: Thu, 19 Jun 2008 14:29:03 +1000	[thread overview]
Message-ID: <18521.57487.410817.953075@notabene.brown> (raw)
In-Reply-To: message from Jan De Luyck on Sunday June 15

On Sunday June 15, ml_linuxkernel_20060528@kcore.org wrote:
> Hello folks,
> 
> I'm trying something which is probably slightly crazy, but I can't get it to work.
> 
> What I'm trying is to get the linux kernel to auto-assembly my raid-1 sets, 
> which are based on volumes on two LDM disks.
> 
> The problem is that the kernel looks for partitiontypes of 0xfd, which I can't 
> set (or haven't found yet how to set) for LDM volumes. The assembly fails, and 
> the kernel panics.

Sorry, acronym failure:  What is LDM??

> 
> Another possibility would be to use an initrd/initramfs, but then I'm once again 
> stuck with a disk that is not in raid, and ergo a point of failure when the disk 
> might crash.

I don't understand your conclusion.
The initrd/initramfs is stored where ever your kernel is stored.  If
storing an initrd introduces a single point of failure, then storing
your Linux kernel will too.


Confused.

NeilBrown 


> 
> (The reason to use LDM is that this way I also can put the other OS on the disk 
> in mirror.)
> 
> Does anyone have any other ideas? I've searched the web, but noone really seems 
> inclined to do it this way...
> 
> Kind regards,
> 
> Jan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2008-06-19  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 20:13 Jan De Luyck
2008-06-19  4:29 ` Neil Brown [this message]
2008-06-19  6:27   ` Jan Engelhardt

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=18521.57487.410817.953075@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ml_linuxkernel_20060528@kcore.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®