All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid device gone underneath array
Date: Fri, 19 Oct 2012 12:22:00 +0800	[thread overview]
Message-ID: <5080D568.4050201@fnarfbargle.com> (raw)
In-Reply-To: <slrnk81k84.am0.chris@chris.onthe.net.au>

On 19/10/12 12:03, Chris Dunlop wrote:
> On 2012-10-19, Adam Goryachev <mailinglists@websitemanagers.com.au> wrote:
>> On 19/10/12 11:01, Marcus Sorensen wrote:
>>> I've been using software raid to mirror two devices, and recently one
>>> of the drives went AWOL.
>>>
>>> md1 : active raid1 sdm[0] sdc[1](F)
>>>        12884900728 blocks super 1.2 [2/1] [U_]
>>>        bitmap: 1/96 pages [4KB], 65536KB chunk
>>>
>>> However, md1 froze, and in looking at the logs I saw this:
>>>
>>> Oct 18 17:47:48 sys kernel: md: cannot remove active disk sdc from md1 ...
>>> Oct 18 17:47:48 sys kernel: md: cannot remove active disk sdc from md1 ...
>>>
>>> [root(marcus)@sanmirror3-01 ~]# mdadm --manage /dev/md1 --remove /dev/sdc
>>> mdadm: cannot find /dev/sdc: No such file or directory
>>>
>>> /dev/sdc was already gone! The /sys/block was already removed, no
>>> reference to it in /proc/scsi/scsi. So md1 was destined to sit there
>>> forever. So I rebooted and started up the degraded array.
>>>
>>> Using kernel 3.6.2 from kernel.org
>>
>> I've also had this problem, I think the kernel notices the device is
>> gone, and removes it before MD notices the problem and removes it from
>> the array. I managed to resolve this without a reboot by manually
>> creating the device in /dev/sdc1 or whatever, and then doing mdadm
>> --manage /dev/md0 --remove /dev/sdc1
>
> Or you could simply do:
>
> mdadm --manage /dev/md1 -r failed

or for two less keystrokes

mdadm --remove /dev/md1 failed



  reply	other threads:[~2012-10-19  4:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19  0:01 raid device gone underneath array Marcus Sorensen
2012-10-19  0:24 ` Adam Goryachev
2012-10-19  4:03   ` Chris Dunlop
2012-10-19  4:22     ` Brad Campbell [this message]
2012-10-19  4:29     ` Chris Murphy
2012-10-19 15:45       ` Marcus Sorensen
2012-10-21 22:19 ` NeilBrown

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=5080D568.4050201@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --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.