From: Bill Davidsen <davidsen@tmr.com>
To: Michael Schmitt <mschmitt@unixkiste.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: confusion about partitionable md arrays
Date: Thu, 28 Dec 2006 22:20:26 -0500 [thread overview]
Message-ID: <4594897A.4080903@tmr.com> (raw)
In-Reply-To: <1167161228.3918.41.camel@localhost.localdomain>
Michael Schmitt wrote:
> Hi list,
>
> since recent releases obviously it is possible to build an array and
> partition that instead of building an array out of partitions. This was
> somehow confusing but it worked in the first place. Now I moved the
> array from one machine to another and... now it gets somehow strange. I
> have nothing in /dev/md/ but /dev/md0. If I do fdisk -l it lists the
> partitions /dev/md0p1 to /dev/md0p4, set to type 83 but there are no
> devices under /dev/ or in /proc/partitions for them. I've read the
> archives and googled around but there was no real solution just
> different meanings on how it should be and how such things come. I'd
> really appreciate a definite answer how that should work with
> partitionable arrays and in best cases, what my problem may be here :)
>
> At the end of this mail are the mdstat and mdadm outputs for reference
>
>
I'm not sure you have a problem, if this whole thing works correctly.
However, there has been discussion about the implications of using whole
drives instead of partitions to build your array. Having avoided that
particular path I'm not going to rehash something I marginally
understand, but some reading of post in the last few months may shed
understanding.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-12-29 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 19:27 confusion about partitionable md arrays Michael Schmitt
2006-12-29 3:20 ` Bill Davidsen [this message]
2006-12-29 8:31 ` Michael Schmitt
2006-12-30 22:08 ` Bill Davidsen
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=4594897A.4080903@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=mschmitt@unixkiste.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).