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.
Description of problem:
When I create snapshot-origin mapping type target through dmsetup command, it fails.
Version-Release number of selected component (if applicable):
# rpm -q kernel
kernel-2.6.32-348.el6.x86_64
# rpm -q device-mapper
device-mapper-1.02.77-5.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Using loop device to simulate block device.
2. try to create snapshot-origin mapping target using
# dmsetup create --table "0 2097152 snapshot-origin /dev/loop5" dm-ssorigin
device-mapper: reload ioctl on dm-ssorigin failed: Invalid argument
Command failed
Actual results:
Dec 24 03:31:05 intel-s3e37-01 kernel: device-mapper: table: 253:3: snapshot-origin: unknown target type
Dec 24 03:31:05 intel-s3e37-01 kernel: device-mapper: ioctl: error adding target to table
Expected results:
The target should be created successfully.
Additional info:
Seems problem with kernel module dm_snapshot, if I load the module manually, then the snapshot-origin target will be created successfully.
# modprobe dm_snapshot
# dmsetup create --table "0 2097152 snapshot-origin /dev/loop5" dm-ssorigin
# dmsetup ls
dm-ssorigin (253:4)
dm-mirror (253:3)
vg_intels3e3701-lv_home (253:2)
vg_intels3e3701-lv_swap (253:1)
vg_intels3e3701-lv_root (253:0)
But I guess this is the wrong way. The kernel module should be automatically loaded.
lvm always loads a module it needs before using it, but auto-loading should work too.
More MODULE_ALIASes perhaps?
Comment 3RHEL Program Management
2013-04-12 02:09:49 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.
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.
http://rhn.redhat.com/errata/RHSA-2013-1645.html