From: Chandra Seetharaman <sekharan@us.ibm.com>
To: Christophe Varoqui <christophe.varoqui@free.fr>
Cc: Mike Anderson <andmike@us.ibm.com>,
dm-devel@redhat.com, michaelc@cs.wisc.edu, agk@redhat.com
Subject: Re: [PATCH 0/3] Changes to Userspace multipath code to support lsi-rdac
Date: Thu, 22 Mar 2007 15:45:41 -0800 [thread overview]
Message-ID: <1174607141.14100.9.camel@linuxchandra> (raw)
In-Reply-To: <1174518416.6218.35.camel@localhost.localdomain>
Cool,
Thanks.
chandra
On Thu, 2007-03-22 at 00:06 +0100, Christophe Varoqui wrote:
> Le mercredi 21 mars 2007 à 11:38 -0800, Chandra Seetharaman a écrit :
> > Hi All,
> >
> > While working on lsi-rdac hardware handler, I found that the checkers "tur"
> > and "readsector0" are not serving the lsi-rdac properly. Also, the storage
> > device has a active/passive state which need to be handled properly.
> >
> > So, I wrote a new path checker for lsi-rdac, to use the C4 inquiry page to get
> > the current owner of the lun and set the state as UP(active) or GHOST(passive).
> > Changes are in patch 1/3.
> >
> > After applying the above patch, I realized the priorities are not set properly.
> > Made some changes to use the GHOST state while setting priorities. Changes are
> > in patch 2/3.
> >
> > Debugging the above patches found that the wait time (5 seconds) in multipathd
> > was not sufficient for the devices to appear in /dev/ It was taking about 20
> > seconds. Changed the wait time to be 60 seconds. Change in patch 3/3.
> >
> > Please provide me with your feedback/comment on these changes regarding
> > correctness, completeness etc.,
> >
> Looks very good. I merged the 3 patches.
>
> In 1/3, I changed the DEF_TIMEOUT name to avoid surcharging the one in
> checker.h
>
> I'm having a hard time push to kernel.org, so don't expect to see the
> git tree updated soon.
>
> Thanks,
> cvaroqui
>
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------
prev parent reply other threads:[~2007-03-22 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 19:38 [PATCH 0/3] Changes to Userspace multipath code to support lsi-rdac Chandra Seetharaman
2007-03-21 19:38 ` [PATCH 1/3] C4 Inquiry based path checker Chandra Seetharaman
2007-03-21 19:38 ` [PATCH 2/3] Fix the priority calculation to use PATH_GHOST state Chandra Seetharaman
2007-03-21 19:38 ` [PATCH 3/3] Increase the wait time for device to appear in /dev Chandra Seetharaman
2007-03-21 23:06 ` [PATCH 0/3] Changes to Userspace multipath code to support lsi-rdac Christophe Varoqui
2007-03-22 22:52 ` Bernd Zeimetz
2007-03-22 23:45 ` Chandra Seetharaman [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=1174607141.14100.9.camel@linuxchandra \
--to=sekharan@us.ibm.com \
--cc=agk@redhat.com \
--cc=andmike@us.ibm.com \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=michaelc@cs.wisc.edu \
/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.