linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Albert Pauw <albert.pauw@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Version 3.2.5 and ddf issues (bugreport)
Date: Tue, 31 Jul 2012 16:11:15 +1000	[thread overview]
Message-ID: <20120731161115.46b96f90@notabene.brown> (raw)
In-Reply-To: <5013D0FE.3020906@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]

On Sat, 28 Jul 2012 13:46:06 +0200 Albert Pauw <albert.pauw@gmail.com> wrote:

> Hi Neil,
> 
> After a hiatus of 1.5 year (busy with all sorts) I am back and tried the 
> ddf code to see how things improved.

Thanks!

> 
> I build a VM Centos 6.3 system with 6 extra 1GB disks for testing.
> I found several issues in the standard installed 3.2.3 version of mdadm 
> relating to ddf, but installed the
> 3.2.5 version in order to work with recent code.
> 
> However, while version 3.2.3 is able to create a ddf container with 
> raidsets in it, I found a problem with the 3.2.5 version.
> 
> After initially creating the container:
> 
> mdadm -C /dev/md127 -e ddf -l container /dev/sd[b-g]
> 
> which worked, I created a raid (1 or 5 it doesn't matter in this case) 
> in it:
> 
> mdadm -C /dev/md0 -l raid5 -n 3 /dev/md127
> 
> However, it stays on resync=PENDING and readonly, and doesn't get build.
> 
> So I tried to set it to readwrite:
> 
> mdadm --readwrite  /dev/md0
> 
> Unfortunately, it stays on readonly and doesn't get build.
> 
> As said before, this did work in 3.2.3.
> 
> Are you already on this problem?

It sounds like a problem with 'mdmon'.  mdmon needs to be running before the
array can become read-write.  mdadm should start mdmon automatically but
maybe it isn't.  Maybe it cannot find mdmon?

could you check if mdadm is running?  If it isn't run
   mdmon /dev/md127 &
and see if it starts working.

> 
> Kind regards,
> 
> Albert
> 
> P.S. My idea was, because the ddf code is not that much used, to create 
> a test/validate script for ddf.
> 
There is one 'ddf' test in my test suite and I think it is working.  I'm
happy to add more tests if you suggest or write some.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-07-31  6:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 19:18 More ddf container woes Albert Pauw
2011-03-23 22:08 ` NeilBrown
2012-07-28 11:46   ` Version 3.2.5 and ddf issues (bugreport) Albert Pauw
2012-07-31  6:11     ` NeilBrown [this message]
2012-07-31  8:46       ` Albert Pauw
2012-08-02  0:05         ` NeilBrown
2012-08-14 23:31         ` NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2012-07-28 11:54 Albert Pauw

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=20120731161115.46b96f90@notabene.brown \
    --to=neilb@suse.de \
    --cc=albert.pauw@gmail.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).