linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: adfas asd <chimera_god@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: RE: A few remaining questions about installing to RAID-10
Date: Mon, 5 Oct 2009 08:30:48 -0700 (PDT)	[thread overview]
Message-ID: <556491.46402.qm@web38805.mail.mud.yahoo.com> (raw)
In-Reply-To: <20091005145711322.FNMG18886@cdptpa-omta02.mail.rr.com>

WAT?!  How can I mount an unpartitioned/unformatted array?  This is more direct than using a filesystem, although there would be no journalling, right?  If I were to mount my small disk for / and the unpartitioned array as /home for example. 

Seems like journalling/crash recovery is pretty vital.  Could not partitioning be recommendable?


--- On Mon, 10/5/09, Leslie Rhorer <lrhorer@satx.rr.com> wrote:
> Partitions are not needed at all unless your underlying
> topology requires
> it:
> 
> `mdadm --create --raid-devices=2 --metadata=1.0 --chunk=128
> --level=1
> /dev/md0 /dev/sda /dev/sdb`
> 
>     Will work just fine.  You can also
> use LVM with raw disks.  Both
> systems simply stitch together storage units provided by
> the drive
> subsystem, so any block device found in /dev can be
> used.  Once the array is
> assembled, it is not necessary to partition it, either,
> again unless your
> overlaying topology requires it.  On my systems, the
> boot drives are
> partitioned to allow booting into Windows if necessary, and
> usually the swap
> is also in a partition on the boot drive, but my arrays are
> completely
> un-partitioned.
> 
> 


      

       reply	other threads:[~2009-10-05 15:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091005145711322.FNMG18886@cdptpa-omta02.mail.rr.com>
2009-10-05 15:30 ` adfas asd [this message]
2009-10-05 15:49   ` A few remaining questions about installing to RAID-10 Drew
2009-10-05 15:55     ` adfas asd
2009-10-05 16:19       ` Drew
2009-10-05 18:13     ` Leslie Rhorer
2009-10-05 18:41       ` Drew
2009-10-06  0:50         ` Leslie Rhorer
2009-10-06  3:42           ` Drew
2009-10-06  9:11             ` Keld Jørn Simonsen
2009-10-06 13:24             ` adfas asd
2009-10-06 22:57               ` Ben DJ
2009-10-07 17:58           ` adfas asd
2009-10-25  5:20             ` Leslie Rhorer
2009-10-05 18:03   ` Leslie Rhorer
2009-10-02  1:27 Ben DJ
2009-10-02  2:31 ` Ben DJ
2009-10-02  3:16 ` Neil Brown
2009-10-02  3:46   ` Ben DJ
2009-10-02 12:30     ` adfas asd
2009-10-02 14:54       ` Ben DJ
2009-10-02 15:06         ` Keld Jørn Simonsen
2009-10-02 15:15         ` Robin Hill
2009-10-02 15:46           ` Ben DJ
2009-10-02 15:59             ` Robin Hill
2009-10-02 16:31               ` Ben DJ
2009-10-02 17:01                 ` Robin Hill
2009-10-02 17:24                   ` Ben DJ
2009-10-03 14:12         ` adfas asd
2009-10-03 16:55           ` Keld Jørn Simonsen
2009-10-03 17:02           ` Thomas Fjellstrom
2009-10-03 19:05           ` Drew
2009-10-03 21:09             ` adfas asd
2009-10-04  5:59               ` Thomas Fjellstrom
2009-10-05  4:59           ` Leslie Rhorer
2009-10-05 13:58             ` adfas asd
2009-10-02  7:51 ` Keld Jørn Simonsen
2009-10-02  7:54 ` Robin Hill

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=556491.46402.qm@web38805.mail.mud.yahoo.com \
    --to=chimera_god@yahoo.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).