From: NeilBrown <neilb@suse.de>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Can't add drive to array 3.3 & 3.2.3
Date: Fri, 6 Apr 2012 20:27:13 +1000 [thread overview]
Message-ID: <20120406202713.30ac90a3@notabene.brown> (raw)
In-Reply-To: <4F7E5309.7080302@fnarfbargle.com>
[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]
On Fri, 06 Apr 2012 10:20:57 +0800 Brad Campbell <lists2009@fnarfbargle.com>
wrote:
> G'day Neil,
>
> I've got a vanilla 3.3 kernel, and mdadm v3.2.3.
Having now seen the real strace:
Yeah, that's a bad combination when bitmaps are involved.
mdadm v.3.2.3 has a bug with adding bitmaps. It uses O_DIRECT writes from a
non-aligned buffer.
You could use the mdadm from my .git, and it would fix that problem, but then
there is a kernel bug (fixed in 3.3.2 I think) which causes an oops.
Probably safest to go back to mdadm-3.2.2, but going forward to
linux.3.3.2 and mdadm-.git would work too.
NeilBrown
>
> I have a 10 drive raid 6 :
> root@srv:~# mdadm --detail /dev/md0
> /dev/md0:
> Version : 1.2
> Creation Time : Tue Apr 5 18:14:42 2011
> Raid Level : raid6
> Array Size : 15628106752 (14904.12 GiB 16003.18 GB)
> Used Dev Size : 1953513344 (1863.02 GiB 2000.40 GB)
> Raid Devices : 10
> Total Devices : 9
> Persistence : Superblock is persistent
>
> Intent Bitmap : Internal
>
> Update Time : Fri Apr 6 10:11:46 2012
> State : active, degraded
> Active Devices : 9
> Working Devices : 9
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 128K
>
> Name : storage1:0_0
> UUID : 0f24724f:8e39ff45:4ed83efe:cad4dd84
> Events : 74069
>
> Number Major Minor RaidDevice State
> 0 8 48 0 active sync /dev/sdd
> 1 0 0 1 removed
> 4 8 144 2 active sync /dev/sdj
> 11 8 80 3 active sync /dev/sdf
> 10 8 16 4 active sync /dev/sdb
> 9 8 0 5 active sync /dev/sda
> 8 8 32 6 active sync /dev/sdc
> 7 8 64 7 active sync /dev/sde
> 6 8 96 8 active sync /dev/sdg
> 5 8 128 9 active sync /dev/sdi
>
> When I go to add a disk to it :
> mdadm --add /dev/md0 /dev/sdh
>
> mdadm creates a superblock on the disk, but there is nothing in dmesg, nor /proc/mdstat.
>
> I've attached an strace of the mdadm --add /dev/md0 /dev/sdh for information.
>
> Not an urgent query, but I thought it odd enough to bring up.
>
> Regards,
> Brad
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-04-06 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 2:20 Can't add drive to array 3.3 & 3.2.3 Brad Campbell
2012-04-06 2:54 ` NeilBrown
2012-04-06 10:14 ` Brad Campbell
2012-04-06 10:27 ` NeilBrown [this message]
2012-04-07 3:26 ` Brad Campbell
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=20120406202713.30ac90a3@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
/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).