All of lore.kernel.org
 help / color / mirror / Atom feed
* 'Array state: ... 1 failed', but array clean?
@ 2010-01-28 12:09 Michał Sawicz
  2010-01-28 12:59 ` Michał Sawicz
  0 siblings, 1 reply; 3+ messages in thread
From: Michał Sawicz @ 2010-01-28 12:09 UTC (permalink / raw)
  To: linux-raid


[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]

Hi,

Can anyone please explain this to me:

> # cat /proc/mdstat
> 
> Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
> md2 : active raid5 sdf1[0] sde1[5] sdb1[6] sda1[3] sdd1[2] sdc1[4]
>       4883799040 blocks super 1.1 level 5, 256k chunk, algorithm 2
> [6/6] [UUUUUU]

Everything looks peachy, but:

> # mdadm -E /dev/sda1
> [...]
>     Array Slot : 3 (0, failed, 2, 3, 1, 5, 4)
>    Array State : uuuUuu 1 failed

Where does this 'failed' come from? Oh, and it's like that on all
members. Is my array safe as /proc/mdstat says?

See attached file for full info from mdadm -E for all the drives.

-- 
Pozdrawiam
Michał (Saviq) Sawicz

[-- Attachment #1.2: md2 --]
[-- Type: text/plain, Size: 5464 bytes --]

Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] 
md2 : active raid5 sdf1[0] sde1[5] sdb1[6] sda1[3] sdd1[2] sdc1[4]
      4883799040 blocks super 1.1 level 5, 256k chunk, algorithm 2 [6/6] [UUUUUU]
      
unused devices: <none>

root@sysresccd /mnt/big % mdadm -E /dev/sda1
/dev/sda1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : 5d5eda8d:0a511d8f:b5cbdfc1:62553e46

    Update Time : Thu Jan 28 12:02:47 2010
       Checksum : 75ee8731 - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 3 (0, failed, 2, 3, 1, 5, 4)
   Array State : uuuUuu 1 failed

root@sysresccd /mnt/big % mdadm -E /dev/sdb1
/dev/sdb1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : db2e5ae0:a98c1483:6b337782:d80712f7

    Update Time : Thu Jan 28 12:02:54 2010
       Checksum : 2dd0ad85 - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 6 (0, failed, 2, 3, 1, 5, 4)
   Array State : uuuuUu 1 failed

root@sysresccd /mnt/big % mdadm -E /dev/sdc1
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : b4cd2c65:29502d62:08a12716:e2f159a0

    Update Time : Thu Jan 28 12:02:54 2010
       Checksum : ceb46781 - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 4 (0, failed, 2, 3, 1, 5, 4)
   Array State : uUuuuu 1 failed

root@sysresccd /mnt/big % mdadm -E /dev/sdd1
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : 8e6a9f57:a33fd6eb:eb8514fc:247b362b

    Update Time : Thu Jan 28 12:02:54 2010
       Checksum : bb9961f9 - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 2 (0, failed, 2, 3, 1, 5, 4)
   Array State : uuUuuu 1 failed

root@sysresccd /mnt/big % mdadm -E /dev/sde1
/dev/sde1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : 5d5eda8d:0a511d8f:b5cbdfc1:62553e46

    Update Time : Thu Jan 28 12:02:54 2010
       Checksum : 75ee873a - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 5 (0, failed, 2, 3, 1, 5, 4)
   Array State : uuuuuU 1 failed

root@sysresccd /mnt/big % mdadm -E /dev/sdf1
/dev/sdf1:
          Magic : a92b4efc
        Version : 1.1
    Feature Map : 0x0
     Array UUID : 9ce41f94:7489a7f2:6897e4b5:269c8b3b
           Name : media:2
  Creation Time : Sun Jan 24 21:32:58 2010
     Raid Level : raid5
   Raid Devices : 6

 Avail Dev Size : 1953519738 (931.51 GiB 1000.20 GB)
     Array Size : 9767598080 (4657.55 GiB 5001.01 GB)
  Used Dev Size : 1953519616 (931.51 GiB 1000.20 GB)
    Data Offset : 264 sectors
   Super Offset : 0 sectors
          State : clean
    Device UUID : fbdd8977:5c6a0b13:f1f792cb:6039ee70

    Update Time : Thu Jan 28 12:02:54 2010
       Checksum : 17ef305f - correct
         Events : 645036

         Layout : left-symmetric
     Chunk Size : 256K

    Array Slot : 0 (0, failed, 2, 3, 1, 5, 4)
   Array State : Uuuuuu 1 failed
root@sysresccd /mnt/big % 


[-- Attachment #2: To jest część wiadomości podpisana cyfrowo --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 'Array state: ... 1 failed', but array clean?
  2010-01-28 12:09 'Array state: ... 1 failed', but array clean? Michał Sawicz
@ 2010-01-28 12:59 ` Michał Sawicz
  2010-01-29  9:44   ` Neil Brown
  0 siblings, 1 reply; 3+ messages in thread
From: Michał Sawicz @ 2010-01-28 12:59 UTC (permalink / raw)
  To: linux-raid

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

Dnia 2010-01-28, czw o godzinie 13:09 +0100, Michał Sawicz pisze:
> Where does this 'failed' come from? Oh, and it's like that on all
> members. Is my array safe as /proc/mdstat says? 

Hmm I think it might be related to this:

> # mdadm -E /dev/sdb1
> [...]
>     Array Slot : 6 (0, failed, 2, 3, 1, 5, 4)
>    Array State : uuuuUu 1 failed

One of the disks in this array was swapped, maybe this is what this info
records? How can I get rid of that?

-- 
Cheers
Michał (Saviq) Sawicz

[-- Attachment #2: To jest część wiadomości podpisana cyfrowo --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 'Array state: ... 1 failed', but array clean?
  2010-01-28 12:59 ` Michał Sawicz
@ 2010-01-29  9:44   ` Neil Brown
  0 siblings, 0 replies; 3+ messages in thread
From: Neil Brown @ 2010-01-29  9:44 UTC (permalink / raw)
  To: Michał Sawicz; +Cc: linux-raid

On Thu, 28 Jan 2010 13:59:39 +0100
Michał Sawicz <michal@sawicz.net> wrote:

> Dnia 2010-01-28, czw o godzinie 13:09 +0100, Michał Sawicz pisze:
> > Where does this 'failed' come from? Oh, and it's like that on all
> > members. Is my array safe as /proc/mdstat says? 
> 
> Hmm I think it might be related to this:
> 
> > # mdadm -E /dev/sdb1
> > [...]
> >     Array Slot : 6 (0, failed, 2, 3, 1, 5, 4)
> >    Array State : uuuuUu 1 failed
> 
> One of the disks in this array was swapped, maybe this is what this info
> records? How can I get rid of that?
> 

The device that was the second device added to the array failed (or
disappeared), and this fact is recorded in case that device ever reappears...

Yes, this is confusing.  mdadm-3.x report the array state differently.

NeilBrown
--
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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-01-29  9:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-28 12:09 'Array state: ... 1 failed', but array clean? Michał Sawicz
2010-01-28 12:59 ` Michał Sawicz
2010-01-29  9:44   ` Neil Brown

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.