From: Francis Moreau <francis.moro@gmail.com>
To: Martin Wilck <mwilck@arcor.de>
Cc: linux-raid@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: mdadm 3.3 fails to kick out non fresh disk
Date: Sat, 14 Sep 2013 17:06:58 +0200 [thread overview]
Message-ID: <CAC9WiBja2N_Q8h6MSci+fgRWWpvvRpcMZp8FOZX3V_FK8pjhpA@mail.gmail.com> (raw)
In-Reply-To: <CAC9WiBh9EOFKx99fTH2yYN62A5CAg4_mqpNtxj6jZOZE+_Raww@mail.gmail.com>
Martin,
On Sat, Sep 14, 2013 at 4:33 PM, Francis Moreau <francis.moro@gmail.com> wrote:
> On Sat, Sep 14, 2013 at 12:38 PM, NeilBrown <neilb@suse.de> wrote:
>> On Sat, 14 Sep 2013 00:35:47 +0200 Francis Moreau <francis.moro@gmail.com>
>> wrote:
[...]
>>
>> BTW I think I've fixed the issue with mdadm -R /dev/md125 for DDF.
>> Try the latest git.
>
> It seems it fixes the issue: mdmon is now correctly started with a
> degraded DDF array.
>
> However, after using the system with only one disk (sda), sdb is now
> outdated. I rebooted the system with 2 disks but mdadm doesn't seem to
> notice that sdb is outdated:
>
> # mdadm -I /dev/sda
> mdadm: container /dev/md/ddf0 now has 1 device
> mdadm: /dev/md/array1_0 assembled with 1 device but not started
> # mdadm -I /dev/sdb
> mdadm: container /dev/md/ddf0 now has 2 devices
> mdadm: Started /dev/md/array1_0 with 2 devices (1 new)
> # cat /proc/mdstat
> Personalities : [raid1]
> md126 : active (auto-read-only) raid1 sdb[1] sda[0]
> 2064384 blocks super external:/md127/0 [2/2] [UU]
>
> md127 : inactive sdb[1](S) sda[0](S)
> 65536 blocks super external:ddf
>
> So this time mdadm fails to kick out non fresh disk (when using '-I')
> but with DDF.
>
Maybe you have an idea on why mdadm doesn't notice that sdb is
outdated in that case (DDF) ?
Thanks
--
Francis
next prev parent reply other threads:[~2013-09-14 15:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 13:22 mdadm 3.3 fails to kick out non fresh disk Francis Moreau
2013-09-13 20:43 ` NeilBrown
2013-09-13 22:35 ` Francis Moreau
2013-09-13 23:56 ` Roberto Spadim
2013-09-14 10:38 ` NeilBrown
2013-09-14 14:33 ` Francis Moreau
2013-09-14 15:06 ` Francis Moreau [this message]
2013-09-14 20:43 ` Martin Wilck
2013-09-16 13:56 ` Francis Moreau
2013-09-16 17:04 ` Martin Wilck
2013-09-20 8:56 ` Francis Moreau
2013-09-20 18:07 ` Martin Wilck
2013-09-20 21:08 ` Francis Moreau
2013-09-21 13:22 ` Francis Moreau
2013-09-23 20:02 ` Martin Wilck
2013-09-27 8:26 ` Francis Moreau
2013-09-27 15:47 ` Francis Moreau
2013-10-02 18:33 ` Martin Wilck
2013-10-16 4:57 ` NeilBrown
2013-10-16 20:10 ` Francis Moreau
2013-10-17 10:58 ` NeilBrown
2013-10-19 20:21 ` Martin Wilck
2013-10-20 23:59 ` NeilBrown
2013-09-24 17:38 ` Martin Wilck
2013-09-24 17:43 ` Martin Wilck
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=CAC9WiBja2N_Q8h6MSci+fgRWWpvvRpcMZp8FOZX3V_FK8pjhpA@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mwilck@arcor.de \
--cc=neilb@suse.de \
/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).