From: Albert Pauw <albert.pauw@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Bugreport ddf rebuild problems
Date: Thu, 01 Aug 2013 21:30:19 +0200 [thread overview]
Message-ID: <51FAB74B.4030200@gmail.com> (raw)
Now I've got it working, I checked a simple rebuild test with a ddf
container, containing two raidsets (raid 1 and raid 5).
Having 6 loopback devices of 512 MB each I opened in a separate screen
this to monitor what happens:
while true; do clear; cat /proc/mdstat ; sleep 1; done
Now are here my commands, en watch the rebuild.
[root@moonlight ~]# mdadm --zero-superblock /dev/loop[1-6]
[root@moonlight ~]# mdadm -CR /dev/md127 -e ddf -l container -n 5
/dev/loop[1-5]
mdadm: /dev/loop1 appears to contain an ext2fs file system
size=153600K mtime=Thu Jan 1 01:00:00 1970
mdadm: /dev/loop2 appears to contain an ext2fs file system
size=153600K mtime=Thu Jan 1 01:00:00 1970
mdadm: container /dev/md127 prepared.
[root@moonlight ~]# mdadm -CR /dev/md0 -l raid1 -n 2 /dev/md0
mdadm: You haven't given enough devices (real or missing) to create this
array
[root@moonlight ~]# mdadm -CR /dev/md0 -l raid1 -n 2 /dev/md127
mdadm: array /dev/md0 started.
[root@moonlight ~]# mdadm -CR /dev/md1 -l raid5 -n 3 /dev/md127
mdadm: array /dev/md1 started.
[root@moonlight ~]# man mdadm
Formatting page, please wait...
[root@moonlight ~]# mdadm -f /dev/md0 /dev/loop4
mdadm: set /dev/loop4 faulty in /dev/md0
[root@moonlight ~]# mdadm -f /dev/md1 /dev/loop2
mdadm: set /dev/loop2 faulty in /dev/md1
[root@moonlight ~]# mdadm --add /dev/md127 /dev/loop6
mdadm: added /dev/loop6
What should happen is that one of the raid sets get rebuild by the added
spare, however
the one raid set gets the spare disk (which is good) and starts
rebuilding, the second one, well have a look:
root@moonlight ~]# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 loop6[3] loop1[2] loop3[0]
958464 blocks super external:/md127/1 level 5, 512k chunk,
algorithm 2 [3/3] [UUU]
md0 : active raid1 loop3[3](S) loop2[2] loop5[0]
479232 blocks super external:/md127/0 [2/2] [UU]
md127 : inactive loop6[5](S) loop5[4](S) loop4[3](S) loop3[2](S)
loop2[1](S) loop1[0](S)
196608 blocks super external:ddf
Effectively a rebuild raid 1 set with three disks (md0) including a
spare, using a failed disk.
Looks like something is going wrong here.
Albert
next reply other threads:[~2013-08-01 19:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 19:30 Albert Pauw [this message]
2013-08-01 19:09 ` Bugreport ddf rebuild problems Martin Wilck
[not found] ` <CAGkViCFT0+qm9YAnAJM7JGgVg0RTJi8=HAYDTMs-mfhXinqdcg@mail.gmail.com>
2013-08-01 21:13 ` Martin Wilck
2013-08-01 22:09 ` Martin Wilck
2013-08-01 22:37 ` Martin Wilck
2013-08-03 9:43 ` Albert Pauw
2013-08-04 9:47 ` Albert Pauw
2013-08-05 16:55 ` Albert Pauw
2013-08-05 21:24 ` Martin Wilck
2013-08-06 0:16 ` NeilBrown
2013-08-06 21:26 ` Martin Wilck
2013-08-06 21:37 ` Patches related to current discussion mwilck
2013-08-06 21:38 ` [PATCH 6/9] tests/10ddf-fail-spare: more sophisticated result checks mwilck
2013-08-06 21:38 ` [PATCH 7/9] tests/10ddf-fail-create-race: test handling of fail/create race mwilck
2013-08-06 21:38 ` [PATCH 8/9] DDF: ddf_open_new: check device status for new subarray mwilck
2013-08-06 21:38 ` [PATCH 9/9] Create: set array status to frozen until monitoring starts mwilck
2013-08-08 0:44 ` NeilBrown
2013-08-08 7:31 ` Martin Wilck
2013-08-07 18:07 ` Bugreport ddf rebuild problems Albert Pauw
2013-08-08 0:40 ` NeilBrown
[not found] <CAGkViCHPvbmcehFvACBKVFFCw+DdnjqvK2uNGmvKrFki+n9n-Q@mail.gmail.com>
2013-08-05 6:21 ` NeilBrown
2013-08-05 7:17 ` 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=51FAB74B.4030200@gmail.com \
--to=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).