linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Ken D'Ambrosio <ken@jots.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID MIA.  Again.  (Kinda.)
Date: Wed, 10 Mar 2010 06:49:09 +1100	[thread overview]
Message-ID: <20100310064909.4ff1fc60@notabene.brown> (raw)
In-Reply-To: <6efdda840bff85f8b8ec053808afa5dd.squirrel@webmail.jots.org>

On Tue, 9 Mar 2010 09:43:48 -0500 (EST)
"Ken D'Ambrosio" <ken@jots.org> wrote:

> On Fri, March 5, 2010 3:37 pm, Neil Brown wrote:
> > mount /dev/md0 /somewhere
> >
> > ??
> 
> Sorry this took so long; I've been busy dying from Martian Death Flu. 
> So... I tried what you suggested.
> 
> And it worked.
> 
> WTF?!
> 
> How can you mount something that doesn't show a partition in fdisk?  I'm
> -very-, -very- confused here.  Grateful, yes, but confused.  Is this
> something I'm just not "getting?"

Yes, this something you are just "not getting", but it is very simple so
won't take a moment to explain.

A partition table is simply a description of how to divide a disk drive up
into smaller units.  In stead of 1 big device, you appear to have several
small devices.
You can create a filesystem on any of these things - the big device, or any
of the smaller devices.

You can use fdisk to divide /dev/sda up into /dev/sda1, /dev/sda2, etc, but
you don't have to.  You can "mkfs /dev/sda" if you like.
Similarly, you can devide /dev/md0 up into /dev/md0p1, /dev/md0p2, with
fdisk, but you don't have to.
Commonly, people use /dev/sda1 rather than /dev/sda, and
  /dev/md0 rather than /dev/md0p1.
But this is just common practice, not enforced (that it wasn't long ago
when /dev/md0p1 could not be created, but that isn't important here).

A partition table does add one byte of extra information - a partition type.
This is a hint as to what sort of thing is stored in the partition.  However
that hint is not widely used in Linux.  I think some installers use it to
automagically find 'swap' and maybe 'root', but that is about it.  For many
purposes the partition type can be ignored.

When you created your filesystem, you must have created it on /dev/md0, not
on a partition.

Hope it is all clear now.

NeilBrown


> 
> Thanks much, regardless, for the pointer -- don't know if I would ever
> have tried mounting it without a partition showing.
> 
> *confused but happy*
> 
> -Ken
> 
> 


      parent reply	other threads:[~2010-03-09 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 16:12 RAID MIA. Again. (Kinda.) Ken D'Ambrosio
2010-03-04 20:50 ` Neil Brown
2010-03-04 22:00   ` Ken D'Ambrosio
     [not found]     ` <4877c76c1003041421s42717938he6567434b74ec125@mail.gmail.com>
2010-03-04 22:24       ` Michael Evans
2010-03-04 23:41       ` Ken D'Ambrosio
2010-03-05  1:22         ` Michael Evans
2010-03-05  1:30     ` Neil Brown
2010-03-05 15:24       ` Ken D'Ambrosio
2010-03-05 20:05         ` Michael Evans
2010-03-05 20:38           ` Neil Brown
2010-03-06  3:18             ` Michael Evans
2010-03-05 20:37         ` Neil Brown
2010-03-09 14:43           ` Ken D'Ambrosio
2010-03-09 16:29             ` John Robinson
2010-03-09 19:49             ` Neil Brown [this message]

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=20100310064909.4ff1fc60@notabene.brown \
    --to=neilb@suse.de \
    --cc=ken@jots.org \
    --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).