* mdadm 3.0.3 bug report
@ 2009-11-09 15:43 Jon Nelson
2009-11-10 0:24 ` Michael Evans
2009-11-10 0:47 ` Dan Williams
0 siblings, 2 replies; 5+ messages in thread
From: Jon Nelson @ 2009-11-09 15:43 UTC (permalink / raw)
To: LinuxRaid
I tried to create a raid thusly:
mdadm --create /dev/md3 --level=10 --layout=f2 --metadata=ddf
--raid-devices=2 --assume-clean /dev/sdc1 missing
and while I got a non-zero exit code (1), I did not get an error
message or any other indication of failure.
The misfeature is that I expected some sort of message.
--
Jon
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: mdadm 3.0.3 bug report
2009-11-09 15:43 mdadm 3.0.3 bug report Jon Nelson
@ 2009-11-10 0:24 ` Michael Evans
2009-11-10 0:30 ` Jon Nelson
2009-11-10 0:47 ` Dan Williams
1 sibling, 1 reply; 5+ messages in thread
From: Michael Evans @ 2009-11-10 0:24 UTC (permalink / raw)
To: Jon Nelson; +Cc: LinuxRaid
$ perror 1
OS error code 1: Operation not permitted
Will it let you create that with another layout type? (such as near or
offset) or with another metadata container format (such as 1.1)?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: mdadm 3.0.3 bug report
2009-11-10 0:24 ` Michael Evans
@ 2009-11-10 0:30 ` Jon Nelson
0 siblings, 0 replies; 5+ messages in thread
From: Jon Nelson @ 2009-11-10 0:30 UTC (permalink / raw)
Cc: LinuxRaid
On Mon, Nov 9, 2009 at 6:24 PM, Michael Evans <mjevans1983@gmail.com> wrote:
> $ perror 1
> OS error code 1: Operation not permitted
>
> Will it let you create that with another layout type? (such as near or
> offset) or with another metadata container format (such as 1.1)?
Yes, I understand error codes.
However, I was still expecting an error *message*.
With metadata=1.1, I get:
mdadm: array /dev/md/3 started.
(and exit code 0, of course)
--
Jon
--
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: mdadm 3.0.3 bug report
2009-11-09 15:43 mdadm 3.0.3 bug report Jon Nelson
2009-11-10 0:24 ` Michael Evans
@ 2009-11-10 0:47 ` Dan Williams
2009-11-16 2:39 ` Neil Brown
1 sibling, 1 reply; 5+ messages in thread
From: Dan Williams @ 2009-11-10 0:47 UTC (permalink / raw)
To: Jon Nelson; +Cc: LinuxRaid
On Mon, Nov 9, 2009 at 8:43 AM, Jon Nelson
<jnelson-linux-raid@jamponi.net> wrote:
> I tried to create a raid thusly:
> mdadm --create /dev/md3 --level=10 --layout=f2 --metadata=ddf
> --raid-devices=2 --assume-clean /dev/sdc1 missing
> and while I got a non-zero exit code (1), I did not get an error
> message or any other indication of failure.
>
> The misfeature is that I expected some sort of message.
Yes, there should be a message that points out that the external
metadata formats ('ddf' and 'imsm') require a container to be created
first and then raid volumes are carved out of that container. The
mdmon man page has a little blurb on containers. The 'missing' option
is currently not supported for creating containers so you would need
to modify this to something like:
mdadm --create /dev/md/ddf -e ddf /dev/sdc /dev/sdX -n 2
mdadm --create /dev/md/volume0 /dev/md/ddf --level=10 --layout=f2
--
Dan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: mdadm 3.0.3 bug report
2009-11-10 0:47 ` Dan Williams
@ 2009-11-16 2:39 ` Neil Brown
0 siblings, 0 replies; 5+ messages in thread
From: Neil Brown @ 2009-11-16 2:39 UTC (permalink / raw)
To: Dan Williams; +Cc: Jon Nelson, LinuxRaid
On Monday November 9, dan.j.williams@intel.com wrote:
> On Mon, Nov 9, 2009 at 8:43 AM, Jon Nelson
> <jnelson-linux-raid@jamponi.net> wrote:
> > I tried to create a raid thusly:
> > mdadm --create /dev/md3 --level=10 --layout=f2 --metadata=ddf
> > --raid-devices=2 --assume-clean /dev/sdc1 missing
> > and while I got a non-zero exit code (1), I did not get an error
> > message or any other indication of failure.
> >
> > The misfeature is that I expected some sort of message.
Thanks for the report. mdadm-3.1.1 will be more verbose.
In that particular case:
mdadm: DDF does not support level 10 arrays
If you try the same with --level=5
mdadm: ddf: Cannot create this array on device /dev/sdc1 - a container is required.
>
> Yes, there should be a message that points out that the external
> metadata formats ('ddf' and 'imsm') require a container to be created
> first and then raid volumes are carved out of that container. The
> mdmon man page has a little blurb on containers. The 'missing' option
> is currently not supported for creating containers so you would need
> to modify this to something like:
I really should do something about supporting the 'missing' option,
and in general being able to specify which devices in the container
should be used....
>
> mdadm --create /dev/md/ddf -e ddf /dev/sdc /dev/sdX -n 2
> mdadm --create /dev/md/volume0 /dev/md/ddf --level=10 --layout=f2
Except that ddf doesn't know "RAID10", it knows "RAID1E" with layouts
of "ADJACENT" (like n2) or OFFSET (like o20).
But mdadm/ddf doesn't handle RAID1E yet - I guess it should.
NeilBrown
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2009-11-16 2:39 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-09 15:43 mdadm 3.0.3 bug report Jon Nelson
2009-11-10 0:24 ` Michael Evans
2009-11-10 0:30 ` Jon Nelson
2009-11-10 0:47 ` Dan Williams
2009-11-16 2:39 ` Neil Brown
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.