linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 reshape problems
Date: Thu, 26 Mar 2009 07:58:33 +0100	[thread overview]
Message-ID: <49CB2799.7000305@xunil.at> (raw)
In-Reply-To: <49CAB3A3.7020807@xunil.at>

Stefan G. Weichinger schrieb:

> Might take till tomorrow when the owner comes to office again that he
> will be able to reboot the box via console.
> 
> At least I am somehow more confident now that we won't lose data.

Update: a hard reboot worked, the raid was visible but inactive.
We re-added the now checked sdf (in a completely cleaned server) and the
raid was still inactive. In the end I had to re-assemble the md-device
with 5 out of 6 devices, right now it rebuilds:

# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sde3[3](S) sdd3[2] sdb3[1] sda3[0]
      17591040 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]

md2 : active raid5 sde4[3] sdd4[2] sdc4[5] sdb4[1] sda4[0]
      2903386944 blocks super 0.91 level 5, 64k chunk, algorithm 2 [6/5]
[UUUU_U]
      [>....................]  reshape =  1.9% (18408064/967795648)
finish=1479.2min speed=10696K/sec


# mdadm -D /dev/md2
/dev/md2:
        Version : 00.91.03
  Creation Time : Wed Oct 22 19:43:13 2008
     Raid Level : raid5
     Array Size : 2903386944 (2768.89 GiB 2973.07 GB)
  Used Dev Size : 967795648 (922.96 GiB 991.02 GB)
   Raid Devices : 6
  Total Devices : 5
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Thu Mar 26 07:56:33 2009
          State : clean, degraded, recovering
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

 Reshape Status : 1% complete
  Delta Devices : 2, (4->6)

           UUID : 2e27c42d:40936d45:53eb5abe:265a9668
         Events : 0.12576

    Number   Major   Minor   RaidDevice State
       0       8        4        0      active sync   /dev/sda4
       1       8       20        1      active sync   /dev/sdb4
       2       8       52        2      active sync   /dev/sdd4
       3       8       68        3      active sync   /dev/sde4
       4       0        0        4      removed
       5       8       36        5      active sync   /dev/sdc4


---

I assume that I will simply have to add /dev/sdf4 then ??
Or again "add" and then "grow" ?

The PV/VG/LVs all are valid, time to try to relax a bit now.

Thanks, Neil,

Stefan

  reply	other threads:[~2009-03-26  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger
2009-03-25 22:13 ` Neil Brown
2009-03-25 22:43   ` Stefan G. Weichinger
2009-03-26  6:58     ` Stefan G. Weichinger [this message]
2009-03-26 10:20       ` Stefan G. Weichinger
2009-03-27 18:11         ` RAID5 reshape problems : SOLVED Stefan G. Weichinger

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=49CB2799.7000305@xunil.at \
    --to=lists@xunil.at \
    --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).