All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 reshape problems
Date: Wed, 25 Mar 2009 23:43:47 +0100	[thread overview]
Message-ID: <49CAB3A3.7020807@xunil.at> (raw)
In-Reply-To: <18890.44146.95223.103114@notabene.brown>

Neil Brown schrieb:

>> "mdadm -D" doesn't give me answers.
> 
> Must be some sort of deadlock....

Yes ...

your suggested ps-command showed numerous instances of hanging
smbd-processes, cronjobs etc.

I feel a bit ashamed to not have taken more daemons offline for doing
that ... but I couldn't foresee the fact that the hotplug-tray would be
full of dust and that the owner of the box wouldn't see that ...

It is very likely that the disk is OK itself, just the connection might
have been too dirty!

>>           State : active
>>  Active Devices : 5
>> Working Devices : 5
>>  Failed Devices : 1
>>   Spare Devices : 0
>>        Checksum : 65f12171 - correct
>>          Events : 0.8247
>>
>>          Layout : left-symmetric
>>      Chunk Size : 64K
>>
>>       Number   Major   Minor   RaidDevice State
>> this     0       8        4        0      active sync   /dev/sda4
>>
>>    0     0       8        4        0      active sync   /dev/sda4
>>    1     1       8       20        1      active sync   /dev/sdb4
>>    2     2       8       36        2      active sync   /dev/sdc4
>>    3     3       8       52        3      active sync   /dev/sdd4
>>    4     4       0        0        4      faulty removed
>>    5     5       8       68        5      active sync   /dev/sde4
>>
> 
> This looks good.  The devices knows that it is in the middle of a
> reshape, and knows how far along it is.  After a reboot it should just
> pick up where it left off.

Sounds gooood ...

> The raid is OK.  It is, of course, degraded now and if another device
> fails you will lose data.  Reboot should be perfectly safe.  However
> you might need to re-assemble the array using the "--force" flag.
> This is safe.
> The reshape didn't finish.  It is only up to 
>>   Reshape pos'n : 61125760 (58.29 GiB 62.59 GB)

ok ... thanks for your feedback, thanks a lot.

Sorry that I called it a "problematic RAID5" ... your code seems not to
be the problem here :-)

I try a remote reboot, I am more than 100 kms away from that server.

It seems to take forever now to reboot, I can still ping it while ssh
doesn't work anymore.

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.

I avoid thinking of having to re-add that /dev/sdf again, and the
pvresize is also still ahead of me.

*sigh*

;-)

Thanks again, Stefan


  reply	other threads:[~2009-03-25 22:43 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 [this message]
2009-03-26  6:58     ` Stefan G. Weichinger
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=49CAB3A3.7020807@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 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.