Bug 889973

Summary:	"kernel: device-mapper: table: 253:3: snapshot-origin: unknown target type"
Product:	Red Hat Enterprise Linux 6	Reporter:	Chao Yang <chyang>
Component:	kernel	Assignee:	Mikuláš Patočka <mpatocka>
Status:	CLOSED ERRATA	QA Contact:	Petr Beňas <pbenas>
Severity:	high	Docs Contact:
Priority:	low
Version:	6.4	CC:	agk, ccui, dwysocha, heinzm, jbrassow, lnovich, msnitzer, pbenas, prajnoha, prockai, pstehlik, qcai, thornber, zkabelac
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel-2.6.32-375.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 14:27:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	961662

Description Chao Yang 2012-12-24 08:35:39 UTC

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:

Comment 1 Chao Yang 2012-12-24 08:59:15 UTC

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.

Comment 2 Alasdair Kergon 2012-12-27 13:52:01 UTC

lvm always loads a module it needs before using it, but auto-loading should work too.

More MODULE_ALIASes perhaps?

Comment 3 RHEL 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.

Comment 4 Jarod Wilson 2013-05-08 20:31:10 UTC

Patch(es) available on kernel-2.6.32-375.el6

Comment 13 Petr Beňas 2013-08-01 11:53:54 UTC

Reproduced in 2.6.32-369.el6.x86_64 and verified in 2.6.32-370.el6.x86_64.

Comment 14 errata-xmlrpc 2013-11-21 14:27:45 UTC

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