public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: Neil Brown <neilb@suse.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	hank peng <pengxihan@gmail.com>,
	Tim Connors <tconnors@rather.puzzling.org>,
	linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: raid failure and LVM volume group availability
Date: Thu, 28 May 2009 20:48:10 +0200	[thread overview]
Message-ID: <87skipysgl.fsf@frosties.localdomain> (raw)
In-Reply-To: <18971.55554.63887.457689@notabene.brown> (Neil Brown's message of "Tue, 26 May 2009 21:56:50 +1000")

Neil Brown <neilb@suse.de> writes:

> On Tuesday May 26, goswin-v-b@web.de wrote:
>> hank peng <pengxihan@gmail.com> writes:
>> 
>> > Only one of disks in this RAID1failed, it should continue to work with
>> > degraded state.
>> > Why LVM complained with I/O errors??
>> 
>> That is because the last drive in a raid1 can not fail:
>> 
>> md9 : active raid1 ram1[1] ram0[2](F)
>>       65472 blocks [2/1] [_U]
>> 
>> # mdadm --fail /dev/md9 /dev/ram1
>> mdadm: set /dev/ram1 faulty in /dev/md9
>> 
>> md9 : active raid1 ram1[1] ram0[2](F)
>>       65472 blocks [2/1] [_U]
>> 
>> See, still marked working.
>> 
>> MfG
>>         Goswin
>> 
>> PS: Why doesn't mdadm or kernel give a message about not failing?
>
> -ENOPATCH :-)
>
> You would want to rate limit any such message from the kernel, but it
> might make sense to have it.
>
> NeilBrown

No rate risk in mdadm --fail reporting a failure to fail the device.

MfG
        Goswin

      reply	other threads:[~2009-05-28 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  3:07 raid failure and LVM volume group availability Tim Connors
2009-05-21  3:55 ` NeilBrown
2009-05-25 12:15   ` Goswin von Brederlow
2009-05-25 16:09 ` hank peng
2009-05-26 11:05   ` Goswin von Brederlow
2009-05-26 11:56     ` Neil Brown
2009-05-28 18:48       ` Goswin von Brederlow [this message]

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=87skipysgl.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=pengxihan@gmail.com \
    --cc=tconnors@rather.puzzling.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