From: Tim Burgess <tim.burgess@anu.edu.au>
To: dm-devel@redhat.com
Subject: Multipath target does not shift block offset?
Date: Thu, 10 Feb 2005 16:02:28 +1100 [thread overview]
Message-ID: <420AEAE4.8090506@anu.edu.au> (raw)
Hi,
I've just been playing with the multipath dm target, and would like to
create a single device mapper device consisting of several,
concatenated, multipathed devices. The intuitive way to do this would be:
# HBA 2 failing to 3
0 286749488 multipath 2 round-robin 1 0 /dev/sdd round-robin 1 0 /dev/sdl
286749488 286749488 multipath 2 round-robin 1 0 /dev/sde round-robin 1 0
/dev/sdm
573498976 286749488 multipath 2 round-robin 1 0 /dev/sdf round-robin 1 0
/dev/sdn
<snip>
However, when one tries to set up such a device, we get the error message:
kernel: device-mapper: device /dev/sde too small for target
I would have assumed that the mapping specified above would map the
whole (sector range 0-286749487) of the sde/sdm device into the range
286749488-573498975 of the dm device. However, dm appears to be trying
to map the range 286749488-573498975 of the dm device to the same
offsets in the sde/sdm device.
Is this what was intended?
Cheers,
Tim
--------------------------------------------------------------------------
ANU Supercomputer Facility
tim.burgess@anu.edu.au and APAC National Facility
Phone: +61 2 6125 1431 Leonard Huxley Bldg (No. 56)
Fax: +61 2 6125 8199 Australian National University
Canberra, ACT, 0200, Australia
--------------------------------------------------------------------------
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2005-02-10 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 5:02 Tim Burgess [this message]
2005-02-10 17:18 ` Multipath target does not shift block offset? Alasdair G Kergon
2005-02-10 19:23 ` Kevin Corry
2005-02-11 18:29 ` Alasdair G Kergon
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 4:45 Tim Burgess
2005-02-16 16:02 ` Kevin Corry
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=420AEAE4.8090506@anu.edu.au \
--to=tim.burgess@anu.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox