All of lore.kernel.org
 help / color / mirror / Atom feed
From: seth vidal <skvidal@linux.duke.edu>
To: dm-devel@redhat.com
Subject: failover speed
Date: Mon, 28 Aug 2006 14:53:09 -0400	[thread overview]
Message-ID: <1156791189.26413.8.camel@cutter> (raw)

Hi,
 I've gotten failover and failback working, however, I'm not sure if the
amount of wait time for the failover is reasonable. I'm using QLogic
2340 cards and an EVA8000. I'm curious if anyone else using something
similar is seeing in terms of failover times. 

When things are running as I'd expect I'm seeing just a few seconds
before the new path is up. When things seem wrong it's waiting and
queueing for as much as 1.5 minutes.

What should I be expecting?

My multipath.conf looks like this:

defaults {
        user_friendly_names             yes
        multipath_tool                  "/sbin/multipath -v0"
        udev_dir                        /dev
        polling_interval                10
        default_selector                "round-robin 0"
        default_path_grouping_policy    failover
        default_getuid_callout          "/sbin/scsi_id -g -u -s /block/%
n"
        default_prio_callout            "/bin/true"
        default_features                "0"
        rr_min_io                      100
        failback                        immediate
}

devnode_blacklist {
        devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
        devnode "^hd[a-z]"
        devnode "^cciss!c[0-9]d[0-9]*"
}



multipaths {

        multipath {
                wwid
3600508b40010764b0000b00003630000
                alias                   "lun1"
                path_grouping_policy    failover
                path_checker            readsector0
                path_selector           "round-robin 0"
                failback                20
                rr_weight               priorities
                no_path_retry           queue
        }

        multipath {
                wwid
3600508b40010764b0000b00003660000
                alias                   "lun2"
                path_grouping_policy    failover
                path_checker            readsector0
                path_selector           "round-robin 0"
                failback                20
                rr_weight               priorities
                no_path_retry           queue
        }
        multipath {
                wwid
3600508b40010764b0000b000036b0000
                alias                   "lun3"
                path_grouping_policy    failover
                path_checker            readsector0
                path_selector           "round-robin 0"
                failback                20
                rr_weight               priorities
                no_path_retry           queue
        }

        multipath {
                wwid
3600508b40010764b0000b000036e0000
                alias                   "lun4"
                path_grouping_policy    failover
                path_checker            readsector0
                path_selector           "round-robin 0"
                failback                20
                rr_weight               priorities
                no_path_retry           queue
        }
}
devices {
          device {
#             vendor                 "HP      "
#             product                "HSV210          "
              vendor                 "HP*"
              product                "HSV210*"
              path_grouping_policy   group_by_prio
              getuid_callout         "/sbin/scsi_id -g -u -s /block/%n"
              path_checker           tur
              path_selector          "round-robin 0"
              prio_callout           "/sbin/mpath_prio_alua %d"
              failback               immediate
              no_path_retry          60
          }
}


Thanks,
-sv

             reply	other threads:[~2006-08-28 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 18:53 seth vidal [this message]
2006-08-29 16:57 ` failover speed seth vidal
2006-09-05 13:59 ` SCSI Sense patch bart brooks
2006-09-05 15:10   ` Alasdair G Kergon
2006-09-05 15:56     ` bart brooks
2006-09-05 17:39       ` Mike Christie
2006-09-05 21:12         ` bart brooks

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=1156791189.26413.8.camel@cutter \
    --to=skvidal@linux.duke.edu \
    --cc=dm-devel@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.