linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Sawicz" <michal@sawicz.net>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Failed, but "md: cannot remove active disk..."
Date: Sun, 13 May 2012 20:21:48 +0200	[thread overview]
Message-ID: <1336933308.2831.4.camel@localhost> (raw)

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

Hey,

I've a weird issue with a RAID6 setup, /proc/mdstat says:

> md126 : active raid6 sda1[3] sdh1[6] sdg1[0](F) sdf1[5] sdi1[1] sdc[8] sdb[7]
>       9767559680 blocks super 1.2 level 6, 512k chunk, algorithm 2 [7/6] [_UUUUUU]

So sdg1 is (F)ailed, yet `mdadm --remove` yields:

> md: cannot remove active disk sdg1 from md126 ...

in dmesg...

`mdadm --examine` shows:

> /dev/sdg1:
>           Magic : a92b4efc
>         Version : 1.2
>     Feature Map : 0x0
>      Array UUID : ff9e032c:446ed0bd:fc9473f3:f8e090ed
>            Name : media:store  (local to host media)
>   Creation Time : Tue Sep 13 21:36:43 2011
>      Raid Level : raid6
>    Raid Devices : 7
> 
> Avail Dev Size : 3907024896 (1863.01 GiB 2000.40 GB)
>      Array Size : 19535119360 (9315.07 GiB 10001.98 GB)
>   Used Dev Size : 3907023872 (1863.01 GiB 2000.40 GB)
>     Data Offset : 2048 sectors
>    Super Offset : 8 sectors
>           State : clean
>     Device UUID : 4bcee8e2:709419b6:fbeb3a8e:5c9bb68a
> 
>     Update Time : Sat May 12 21:57:27 2012
>        Checksum : ffb03189 - correct
>          Events : 304564
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 0
>    Array State : AAAAAAA ('A' == active, '.' == missing)

So that superblock thinks it's active, but that's normal, right? It
wasn't updated due to fail? Others correctly show:

> dev/sdc:
>           Magic : a92b4efc
>         Version : 1.2
>     Feature Map : 0x0
>      Array UUID : ff9e032c:446ed0bd:fc9473f3:f8e090ed
>            Name : media:store  (local to host media)
>   Creation Time : Tue Sep 13 21:36:43 2011
>      Raid Level : raid6
>    Raid Devices : 7
> 
>  Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
>      Array Size : 19535119360 (9315.07 GiB 10001.98 GB)
>   Used Dev Size : 3907023872 (1863.01 GiB 2000.40 GB)
>     Data Offset : 2048 sectors
>    Super Offset : 8 sectors
>           State : clean
>     Device UUID : b713fd2b:eef145b0:ce91de0a:9077554b
> 
>     Update Time : Sat May 12 21:57:57 2012
>        Checksum : 80345876 - correct
>          Events : 304581
> 
>          Layout : left-symmetric
>      Chunk Size : 512K
> 
>    Device Role : Active device 2
>    Array State : .AAAAAA ('A' == active, '.' == missing)

Any ideas?

Cheers,
-- 
Michał Sawicz <michal@sawicz.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-05-13 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 18:21 Michał Sawicz [this message]
2012-05-14 10:22 ` Failed, but "md: cannot remove active disk..." NeilBrown
2012-05-14 10:53   ` Michał Sawicz
2012-05-14 11:36     ` NeilBrown
2012-05-14 11:44       ` Michał Sawicz
2012-05-15  3:38         ` NeilBrown
2012-05-15  7:56           ` Michał Sawicz

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=1336933308.2831.4.camel@localhost \
    --to=michal@sawicz.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).