From: Nicolas Jungers <nicolas@jungers.net>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: bug in kernel 3.2 (up to date Debian wheezy)
Date: Fri, 28 Jun 2013 19:35:00 +0200 [thread overview]
Message-ID: <51CDC944.1000000@jungers.net> (raw)
In-Reply-To: <51CC74C2.6010608@jungers.net>
On 06/27/2013 07:22 PM, Nicolas Jungers wrote:
> Assembling a raid 10 array on Debian Wheezy I got the following messages:
>
>
> #-----------
> uname -a
> Linux ha1 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
> mdadm --version
> mdadm - v3.2.5 - 18th May 2012
> #-----------
>
> The operation was:
>
> mdadm -C /dev/md0 -l10 -pf2 -n4 -x1 --assume-clean -b internal
> /dev/sd[abcde]1
>
>
[snip]
For info, the partition 1 is ~1 GB and the bug disappear if I suppress
the internal bitmap. It doesn't show itself on a ~900 GB partition.
regards,
N.
prev parent reply other threads:[~2013-06-28 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:22 bug in kernel 3.2 (up to date Debian wheezy) Nicolas Jungers
2013-06-28 17:35 ` Nicolas Jungers [this message]
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=51CDC944.1000000@jungers.net \
--to=nicolas@jungers.net \
--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).