linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher White <linux@pulseforce.com>
To: linux-raid@vger.kernel.org
Subject: mdadm does not create partition devices whatsoever, "partitionable" functionality broken
Date: Fri, 13 May 2011 17:13:07 +0200	[thread overview]
Message-ID: <4DCD4A83.8060202@pulseforce.com> (raw)

Greetings.

I have spent TEN hours trying everything other than regressing to a 
REALLY old version. I started out on 3.1.4 and have also tried manually 
upgrading to 3.2.1, but the bug still exists.

Somewhere along the way, the "auto" partitionable flag has broken.

sudo mdadm --create --level=raid5 --auto=part2 /dev/md1 --metadata=1.2 
--raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2

This only creates /dev/md1. It is of course possible to create one big 
partition as /dev/md1p1 with any partitioning program, but FORGET about 
trying to create /dev/md1p2.

The problem is that the RAID array is NOT created in partitionable mode, 
and only supports one large partition, despite ALL attempts at EVERY 
format of the --auto option, you name it, -a part2, --auto=mdp2, 
--auto=part2, --auto=p2, --auto=mdp, --auto=part, --auto=p, --auto=p4, 
you name it and I've tried it!

My guess is the functionality of creating partitionable arrays literally 
DID break somewhere prior to/at version 3.1.4 which is the earliest 
version I tried.

I'm giving up and creating physical n-1 sized partitions on the source 
disks and creating two RAID 5 arrays from those partitions instead, but 
decided I really MUST report this bug so that other people don't bang 
their head against the wall for ten hours of their life as well. ;-)


Christopher


             reply	other threads:[~2011-05-13 15:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 15:13 Christopher White [this message]
2011-05-13 16:49 ` mdadm does not create partition devices whatsoever, "partitionable" functionality broken Phil Turmel
2011-05-13 17:18   ` Christopher White
2011-05-13 17:32     ` Christopher White
2011-05-13 17:40       ` Roman Mamedov
2011-05-13 18:04         ` Christopher White
2011-05-13 18:18           ` Phil Turmel
2011-05-13 18:54             ` Christopher White
2011-05-13 19:01               ` Rudy Zijlstra
2011-05-13 19:49                 ` Christopher White
2011-05-13 20:00                   ` Rudy Zijlstra
2011-05-13 19:49                 ` Christopher White
2011-05-13 19:22               ` Phil Turmel
2011-05-13 19:32                 ` Roman Mamedov
2011-05-13 19:39                   ` Phil Turmel
2011-05-14 10:10                   ` David Brown
2011-05-14 10:24                     ` Roman Mamedov
2011-05-14 12:56                       ` David Brown
2011-05-14 13:27                         ` Drew
2011-05-14 18:21                           ` David Brown
2011-05-13 17:43       ` Phil Turmel

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=4DCD4A83.8060202@pulseforce.com \
    --to=linux@pulseforce.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).