All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jose nuno neto" <jose.neto@liber4e.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Lvm hangs on San fail
Date: Thu, 15 Apr 2010 08:29:48 -0000 (GMT)	[thread overview]
Message-ID: <dfcfa84ce3699e54c9fd46ec9513ec78.squirrel@fela.liber4e.com> (raw)
In-Reply-To: <1271286129.2462.0.camel@localhost>

GoodMornings

This is what I have on multipath.conf

blacklist {
        wwid SSun_VOL0_266DCF4A
        wwid SSun_VOL0_5875CF4A
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
}
defaults {
                user_friendly_names             yes
}
devices {
       device {
                vendor                          "HITACHI"
                product                         "OPEN-V"
                path_grouping_policy            group_by_node_name
                failback                        immediate
                no_path_retry                   fail
       }
       device {
                vendor                          "IET"
                product                         "VIRTUAL-DISK"
                path_checker                    tur
                path_grouping_policy            failover
                failback                        immediate
                no_path_retry                   fail
       }
}

As an example this is one LUN. It shoes [features=0] so I'd say it should
fail right way

mpath-dc2-a (360060e8004f240000000f24000000502) dm-15 HITACHI,OPEN-V      -SU
[size=26G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=4][active]
 \_ 5:0:1:0     sdu  65:64  [active][ready]
 \_ 5:0:1:16384 sdac 65:192 [active][ready]
 \_ 5:0:1:32768 sdas 66:192 [active][ready]
 \_ 5:0:1:49152 sdba 67:64  [active][ready]
\_ round-robin 0 [prio=4][enabled]
 \_ 3:0:1:0     sdaw 67:0   [active][ready]
 \_ 3:0:1:16384 sdbe 67:128 [active][ready]
 \_ 3:0:1:32768 sdbi 67:192 [active][ready]
 \_ 3:0:1:49152 sdbm 68:0   [active][ready]

It think they fail since I see this messages from LVM:
Apr 14 16:03:05 dc1-x6250-a lvm[15622]: Device failure in
vg_syb_roger-lv_syb_roger_admin
Apr 14 16:03:14 dc1-x6250-a lvm[15622]: Failed to remove faulty devices in
vg_syb_roger-lv_syb_roger_admin

But from some reason LVM cant remove them, any option I should have on
lvm.conf?

BestRegards
Jose
> post your multipath.conf file, you may be queuing forever ?
>
>
>
> On Wed, 2010-04-14 at 15:03 +0000, jose nuno neto wrote:
>> Hi2all
>>
>> I'm on RHEL 5.4 with
>> lvm2-2.02.46-8.el5_4.1
>> 2.6.18-164.2.1.el5
>>
>> I have a multipathed SAN connection with what Im builing LVs
>> Its a Cluster system, and I want LVs to switch on failure
>>
>> If I simulate a fail through the OS via
>> /sys/bus/scsi/devices/$DEVICE/delete
>> I get a LV fail and the service switch to other node
>>
>> But if I do it "real" portdown on the SAN Switch, multipath reports path
>> down, but LVM commands hang forever and nothing gets switched
>>
>> from the logs i see multipath failing paths, and lvm Failed to remove
>> faulty
>> "devices"
>>
>> Any ideas how I should  "fix" it?
>>
>> Apr 14 16:02:45 dc1-x6250-a lvm[15622]: Log device, 253:53, has failed.
>> Apr 14 16:02:45 dc1-x6250-a lvm[15622]: Device failure in
>> vg_ora_scapa-lv_ora_scapa_redo
>> Apr 14 16:02:45 dc1-x6250-a lvm[15622]: Another thread is handling an
>> event.  Waiting...
>>
>> Apr 14 16:02:52 dc1-x6250-a multipathd: mpath-dc1-a: remaining active
>> paths: 0
>> Apr 14 16:02:52 dc1-x6250-a multipathd: mpath-dc1-a: remaining active
>> paths: 0
>> Apr 14 16:02:52 dc1-x6250-a multipathd: mpath-dc1-b: remaining active
>> paths: 0
>> Apr 14 16:02:52 dc1-x6250-a multipathd: mpath-dc1-b: remaining active
>> paths: 0
>>
>> Apr 14 16:03:05 dc1-x6250-a lvm[15622]: Device failure in
>> vg_syb_roger-lv_syb_roger_admin
>> Apr 14 16:03:14 dc1-x6250-a lvm[15622]: Failed to remove faulty devices
>> in
>> vg_syb_roger-lv_syb_roger_admin
>>
>> Much Thanks
>> Jose
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  reply	other threads:[~2010-04-15  8:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 16:14 [linux-lvm] Mirror fail/recover test jose nuno neto
2010-02-24 18:55 ` malahal
2010-02-25 10:36   ` jose nuno neto
2010-02-25 16:11     ` malahal
2010-03-02 10:31       ` [linux-lvm] Mirror fail/recover test SOLVED jose nuno neto
2010-04-14 15:03         ` [linux-lvm] Lvm hangs on San fail jose nuno neto
2010-04-14 17:38           ` Eugene Vilensky
2010-04-14 23:02           ` brem belguebli
2010-04-15  8:29             ` jose nuno neto [this message]
2010-04-15  9:32               ` Bryan Whitehead
2010-04-15 11:59               ` jose nuno neto
2010-04-15 12:41                 ` Eugene Vilensky
2010-04-16  8:55                   ` jose nuno neto
2010-04-16 20:15                     ` Bryan Whitehead
2010-04-17  9:00                     ` brem belguebli
2010-04-19  9:21                       ` jose nuno neto

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=dfcfa84ce3699e54c9fd46ec9513ec78.squirrel@fela.liber4e.com \
    --to=jose.neto@liber4e.com \
    --cc=linux-lvm@redhat.com \
    /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.