Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Inclusion of the device-mapper switch target
The device-mapper (DM) switch target creates a device that supports an arbitrary mapping of fixed-size regions of I/O across a fixed set of paths. The path used for any specific region can be switched dynamically by sending the target a message. This functionality provides a two-layer device hierarchy that allows for efficient load balancing across a large member group.
Comment 3RHEL Program Management
2015-02-26 20:13:18 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Test it this way:
1) Create several logical volumes with the same size, for example:
LV VG Attr LSize
switch-0 vg1 -wi-a----- 1,00g
switch-1 vg1 -wi-a----- 1,00g
switch-2 vg1 -wi-a----- 1,00g
2) Load the switch target that uses these volumes:
dmsetup create switch --table "0 2097152 switch 3 31 0 /dev/vg1/switch-0 0 /dev/vg1/switch-1 0 /dev/vg1/switch-2 0"
(3 is the number of volumes; 31 is the region size in sectors, you can put any value there)
3) Load something into the mapping table, use several commands "dmsetup message switch 0 set_region_mappings..." The syntax of the command is in the file Documentation/device-mapper/switch.txt. You can load whatever you want into the table, and remember what have you loaded.
4) Create a filesystem on the switch device /dev/mapper/switch
5) Mount the filesystem, copy some data to the filesytem, unmount it.
6) Unload the switch target: dmsetup remove switch
7) Repeat the steps 2), 3), 5) (in step 3, load the same mapping table as you did before)
8) Check the filesystem with fsck, then mount it and verify that the data is intact
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-1272.html
Created attachment 995272 [details] The patch that backports dm-switch