Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Ethan Wilson <ethan.wilson@shiftmail.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Very small bug on assemble --force
Date: Wed, 29 Oct 2014 07:50:50 +1100	[thread overview]
Message-ID: <20141029075050.605a11a9@notabene.brown> (raw)
In-Reply-To: <544FA7B6.7030100@shiftmail.org>

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

On Tue, 28 Oct 2014 15:27:02 +0100 Ethan Wilson <ethan.wilson@shiftmail.org>
wrote:

> Very small bug report:

Thanks for the bug report.
However, please always quote version of mdadm and version of Linux.

I think this might have been fixed already, in mdadm 3.3.1.

NeilBrown


> mdadm assemble --force fails to assemble at the very last step after 
> having adjusted the event count:
> 
> 
> root@storage1:/root# mdadm --assemble /dev/md106 --config 
> /etc/mdadm/mdadm.secondary.conf --force
> mdadm: forcing event count in 
> /dev/mapper/mpathid-350014ee0ac5a112e-part1(3) from 1058 upto 1061
> mdadm: forcing event count in 
> /dev/mapper/mpathid-350014ee056feaaf4-part1(4) from 1058 upto 1061
> mdadm: forcing event count in 
> /dev/mapper/mpathid-350014ee001a93ede-part1(6) from 1058 upto 1061
> mdadm: clearing FAULTY flag for device 1 in /dev/md106 for 
> /dev/mapper/mpathid-350014ee0ac5a112e-part1
> mdadm: clearing FAULTY flag for device 5 in /dev/md106 for 
> /dev/mapper/mpathid-350014ee056feaaf4-part1
> mdadm: clearing FAULTY flag for device 8 in /dev/md106 for 
> /dev/mapper/mpathid-350014ee001a93ede-part1
> mdadm: Marking array /dev/md106 as 'clean'
> mdadm: /dev/md106 assembled from 8 drives - not enough to start the array.
> 
> mdadm is wrong here: 8 devices is indeed the total number of devices for 
> this array.
> the last command started it inactive like this:
> 
> md106 : inactive dm-101[0](S) dm-24[9](S) dm-107[6](S) dm-103[5](S) 
> dm-123[4](S) dm-95[3](S) dm-105[2](S) dm-106[1](S)
>        4193255424 blocks super 1.2
> (maybe the blocks count is also wrong? Not adjusted for parity maybe? 
> 4193255424  / 8.0 * 6.0 == 3144941568.0 almost correct)
> 
> it can be fixed simply by doing:
> 
> root@storage1:/root# mdadm --stop /dev/md106
> mdadm: stopped /dev/md106
> 
> root@storage1:/root# mdadm --assemble /dev/md106 --config 
> /etc/mdadm/secondary.conf --no-degraded
> mdadm: /dev/md106 has been started with 8 drives.
> 
> now it works:
> 
> md106 : active raid6 dm-101[0] dm-24[9] dm-107[6] dm-103[5] dm-123[4] 
> dm-95[3] dm-105[2] dm-106[1]
>        3144938496 blocks super 1.2 level 6, 512k chunk, algorithm 2 
> [8/8] [UUUUUUUU]
>        bitmap: 0/1 pages [0KB], 1048576KB chunk
> 
> Regards
> EW
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  reply	other threads:[~2014-10-28 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 14:27 Very small bug on assemble --force Ethan Wilson
2014-10-28 20:50 ` NeilBrown [this message]
2014-10-28 22:40   ` Ethan Wilson

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=20141029075050.605a11a9@notabene.brown \
    --to=neilb@suse.de \
    --cc=ethan.wilson@shiftmail.org \
    --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