From: <me@heyjay.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: mdadm 1.6.0 - A tool for managing Soft RAID under Linux
Date: Sun, 6 Jun 2004 17:50:47 -0500 [thread overview]
Message-ID: <000701c44c18$b7cf2ab0$6705a8c0@a30> (raw)
In-Reply-To: 16577.25452.82324.146669@cse.unsw.edu.au
Sorry for the delayed response.
I think I'm confused about device files and the relationship between device
files and partitions. I'm going to have to go read some now...
Thanks
Jay
----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: <me@heyjay.com>
Cc: "Guy" <bugzilla@watkins-home.com>; <linux-raid@vger.kernel.org>
Sent: Saturday, June 05, 2004 1:08 AM
Subject: Re: ANNOUNCE: mdadm 1.6.0 - A tool for managing Soft RAID under
Linux
> On Friday June 4, me@heyjay.com wrote:
> > I did finish, but the example seemed to show that the --auto would build
the
> > partitions. I know at the end of the message Neil said then you use
cfdisk
> > but it seemed unnecessary at that point
>
> Hmmm....
> I said:
>
> : If you do this, it will create device files:
> :
> : /dev/md/XX the whole array
> : /dev/md/XX1 the first partition
> : /dev/md/XX2 the second partition
> : /dev/md/XX3 the third partition
> : /dev/md/XX4 the fourth partition
>
> Meaning that it will create "device files" for the partitions, which
> is what I said.
> However I then said:
>
> : More (or less) partitions can be created using e.g. --auto=partition8
> : to create 8 partition device files.
>
> Which first says that "partitions" can be created, and then that
> "partition device files" will be created.
>
> So I clearly wasn't being precise as would be good, though I was
> trying :-)
>
> mdadm created device files (just like mknod does). It does not create
> partitions - that is a job for *fdisk.
>
> NeilBrown
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2004-06-06 22:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 6:29 ANNOUNCE: mdadm 1.6.0 - A tool for managing Soft RAID under Linux Neil Brown
2004-06-04 10:12 ` Robin Bowes
2004-06-04 12:13 ` Neil Brown
2004-06-04 13:31 ` me
2004-06-04 14:21 ` Guy
2004-06-05 2:51 ` me
2004-06-05 6:08 ` Neil Brown
2004-06-06 22:50 ` me [this message]
2004-06-05 6:36 ` David Greaves
2004-06-06 22:52 ` me
2004-06-04 15:00 ` Robin Bowes
2004-06-04 15:22 ` David Greaves
2004-06-04 15:27 ` Robin Bowes
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 10:12 Robin Bowes
2004-06-06 16:30 ` Andreas Haumer
2004-06-06 21:46 ` Neil Brown
2004-06-07 7:50 ` Mario 'BitKoenig' Holbe
2004-06-07 15:54 ` Joe Pruett
2004-06-08 14:11 ` Mario 'BitKoenig' Holbe
2004-06-09 7:01 ` Clemens Schwaighofer
2004-06-06 22:58 Norman Schmidt
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='000701c44c18$b7cf2ab0$6705a8c0@a30' \
--to=me@heyjay.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).