All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Avuton Olrich <avuton@gmail.com>
Cc: Jonathan Briggs <jbriggs@esoft.com>,
	Christian Iversen <chrivers@iversen-net.dk>,
	Alexander Zarochentsev <zam@namesys.com>,
	reiserfs-list@namesys.com, Mark F <mfaine@knology.net>,
	Ext3-users@redhat.com
Subject: Re: create very large file system
Date: Thu, 20 Jul 2006 12:32:36 -0500	[thread overview]
Message-ID: <44BFBE34.80001@slaphack.com> (raw)
In-Reply-To: <3aa654a40607200956j37aeed0o66218c7ff94d815a@mail.gmail.com>

Avuton Olrich wrote:
> On 7/20/06, Jonathan Briggs <jbriggs@esoft.com> wrote:
>> You're not supposed to be doing it that way these days.  RAID autodetect
>> is getting tossed out of the kernel in the future (probably still many
> 
> Bit OT, but is there something that is supposed to replace RAID
> autodetect, or we're just supposed to make initscripts to run mdadm?

I'm not sure, but I suspect it may have something to do with the 
device-mapper.  I know that's what I use for a striped array -- and yes, 
I have to make an initscript -- initrd, because I boot off the thing -- 
to set them up.  The good news is, the detection can be done in userland 
now -- since mine is nvidia raid, I can use dmraid, which runs entirely 
in userland, autodetects from BIOS settings, then sets up a proper 
device-mapper table in the kernel.

Device-mapper doesn't support everything yet (as far as I know), but the 
principle should be about the same for more complex RAID -- some 
userland tool.  There really is no reason for this autodetection to be 
in the kernel.

In the meantime, there may be rough edges...

  reply	other threads:[~2006-07-20 17:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 12:10 create very large file system Mark F
2006-07-19 12:57 ` Alexander Zarochentsev
2006-07-19 13:24   ` Mark F
2006-07-20  6:26   ` Andreas Dilger
2006-07-20  7:11     ` Clay Barnes
2006-07-20 16:46       ` David Masover
2006-07-20 11:17     ` Christian Iversen
2006-07-20 15:02       ` Andreas Dilger
2006-07-20 16:22       ` Jonathan Briggs
2006-07-20 16:56         ` Avuton Olrich
2006-07-20 17:32           ` David Masover [this message]
2006-07-21 15:37 ` Stephen Tweedie
2006-07-21 15:58   ` Mark F

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=44BFBE34.80001@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=Ext3-users@redhat.com \
    --cc=avuton@gmail.com \
    --cc=chrivers@iversen-net.dk \
    --cc=jbriggs@esoft.com \
    --cc=mfaine@knology.net \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.