All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Beck <mail@pierre-beck.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 crashed, need comments on possible repair solution
Date: Sat, 12 May 2012 19:19:32 +0200	[thread overview]
Message-ID: <4FAE9BA3.4000407@pierre-beck.de> (raw)
In-Reply-To: <20120424090122.3d90b4a6@notabene.brown>

Hi,

got an all-spares auto-assembly on IRC with "Raid level: -unknown-". We 
recovered by re-creating the array. Since more data is always good, I 
add this to the thread and hope it helps confirm the bug is fixed by the 
patch.

RAID-5, 3 members with 1 missing on creation and ever since.

Members on partitions with partition type set for auto-assembly.

Array was transported to a new machine.

Drive order got mixed up on transport: AB_ BA_
(figured that out on recovery)

On target machine boot-up (array not yet configured in mdadm.conf) 
Archlinux auto-assembled array with both drives as spares:

/dev/sda1:
           Magic : a92b4efc
         Version : 1.2
     Feature Map : 0x0
      Array UUID : c051172d:52ed3e47:e8dc6dc8:8798f4c9
            Name : OncleGeorges:0
   Creation Time : Fri Aug  5 18:00:19 2011
      Raid Level : -unknown-
    Raid Devices : 0

  Avail Dev Size : 1953515969 (931.51 GiB 1000.20 GB)
     Data Offset : 2048 sectors
    Super Offset : 8 sectors
           State : active
     Device UUID : a8b44e10:ff04d973:c5f92933:3c9e124f

     Update Time : Sat Apr 21 19:14:34 2012
        Checksum : 8b57fb27 - correct
          Events : 1


    Device Role : spare
    Array State :  ('A' == active, '.' == missing)

/dev/sdb1:
           Magic : a92b4efc
         Version : 1.2
     Feature Map : 0x0
      Array UUID : c051172d:52ed3e47:e8dc6dc8:8798f4c9
            Name : OncleGeorges:0
   Creation Time : Fri Aug  5 18:00:19 2011
      Raid Level : -unknown-
    Raid Devices : 0

  Avail Dev Size : 2046769231 (975.98 GiB 1047.95 GB)
   Used Dev Size : 1953515969 (931.51 GiB 1000.20 GB)
     Data Offset : 2048 sectors
    Super Offset : 8 sectors
           State : active
     Device UUID : d2594375:c8adc5a0:53938a24:9bd5c6be

     Update Time : Sat Apr 21 19:14:34 2012
        Checksum : 83dd0895 - correct
          Events : 1


    Device Role : spare
    Array State :  ('A' == active, '.' == missing)


Versions:

Linux HostName 3.3.4-2-ARCH #1 SMP PREEMPT Wed May 2 15:39:58 UTC 2012 
i686 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux

mdadm - v3.2.3 - 23rd December 2011

Greetings,

Pierre Beck

  reply	other threads:[~2012-05-12 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 13:56 Raid5 crashed, need comments on possible repair solution Christoph Nelles
2012-04-23 21:00 ` NeilBrown
2012-04-23 21:47   ` Christoph Nelles
2012-04-23 23:01     ` NeilBrown
2012-05-12 17:19       ` Pierre Beck [this message]
2012-05-14 21:00         ` C.J. Adams-Collier KF7BMP

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=4FAE9BA3.4000407@pierre-beck.de \
    --to=mail@pierre-beck.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 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.