From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: path checker open() flags, devmapper ioctl()
Date: Fri, 18 Apr 2008 21:43:01 +0200 [thread overview]
Message-ID: <1208547781.11770.117.camel@plop> (raw)
Here is an update with my findings of today.
Paths to R2 LU are flaged read-only upon detection, as can be seen with
"hdparm -r". hdparm is able to flag them rw (hdparm -r0). Once paths are
switched to rw, I still can't use multipath to load maps upon them.
But, issuing "blockdev --rereadpt" on the paths finally resolves this
issue.
I'm confused. What is expected from the multipath tools there ? I'd like
to have the multipath maps up and running for R2 LU, for them to be
ready the moment they get activated by the R1/R2 split. But I'm not sure
how to do that in the described context. Input welcome.
Regards,
cvaroqui
next reply other threads:[~2008-04-18 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 19:43 Christophe Varoqui [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-17 20:55 path checker open() flags, devmapper ioctl() Christophe Varoqui
2008-04-17 21:21 ` Christophe Varoqui
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=1208547781.11770.117.camel@plop \
--to=christophe.varoqui@free.fr \
--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.