Bug 1091553
Summary: | "Internal error: Performing unsafe table load" error during snapshot of cache origin volume removal | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> | ||||
Component: | lvm2 | Assignee: | Jonathan Earl Brassow <jbrassow> | ||||
lvm2 sub component: | Cache Logical Volumes | QA Contact: | Cluster QE <mspqa-list> | ||||
Status: | CLOSED ERRATA | Docs Contact: | |||||
Severity: | medium | ||||||
Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, zkabelac | ||||
Version: | 7.0 | ||||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | lvm2-2.02.111-1.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
No Documentation Needed. Snapshots of cache logical volumes will happen in a future release.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1114068 (view as bug list) | Environment: | |||||
Last Closed: | 2015-03-05 13:08:31 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: | 1075262, 1114068, 1119326, 1185916 | ||||||
Attachments: |
|
Description
Corey Marthaler
2014-04-25 21:00:14 UTC
Created attachment 889912 [details]
-vvvv of the snap lvremove
Here's the attempted removal of a snap of a raid cache pool. Test Output: lvremove -f /dev/cache_sanity/snap1 couldn't remove volume snap1 Internal error: Performing unsafe table load while 4 device(s) are known to be suspended: (253:24) device-mapper: resume ioctl on failed: Invalid argument Unable to resume cache_sanity-rename_orig_A-real (253:24) Failed to resume rename_orig_A. libdevmapper exiting with 4 device(s) still suspended. Jun 4 17:46:10 host-073 qarshd[25149]: Running cmdline: lvremove -f /dev/cache_sanity/snap1 Jun 4 17:46:10 host-073 lvm[3121]: No longer monitoring snapshot cache_sanity-snap1 Jun 4 17:46:10 host-073 lvm[3121]: No longer monitoring snapshot cache_sanity-snap2 Jun 4 17:46:10 host-073 lvm[3121]: No longer monitoring RAID device cache_sanity-rename_pool_A_cdata for events. Jun 4 17:46:10 host-073 lvm[3121]: No longer monitoring RAID device cache_sanity-rename_pool_A_cmeta for events. Jun 4 17:46:10 host-073 systemd-udevd: inotify_add_watch(7, /dev/dm-25, 10) failed: No such file or directory Jun 4 17:46:11 host-073 kernel: device-mapper: block manager: validator mismatch (old=array vs new=btree_node) for block 140 Jun 4 17:46:11 host-073 kernel: device-mapper: cache: could not load origin discards Jun 4 17:46:11 host-073 kernel: device-mapper: table: 253:24: cache: preresume failed, error = -22 Support for snapshot of cached volume is for now disabled as unsupported. Please retest. This "works" now. We will need to add a new feature bug to allow snapshots of cache LVs. [root@bp-01 ~]# lvcreate -s -L 500M -n snap vg/lv Snapshot of cache LV is not yet supported. *** Bug 1105732 has been marked as a duplicate of this bug. *** Marking "Verified" in the latest rpms. Snaps of cache volumes are no longer allowed. 3.10.0-215.el7.x86_64 lvm2-2.02.114-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 lvm2-libs-2.02.114-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 lvm2-cluster-2.02.114-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 device-mapper-1.02.92-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 device-mapper-libs-1.02.92-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 device-mapper-event-1.02.92-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 device-mapper-event-libs-1.02.92-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 device-mapper-persistent-data-0.4.1-2.el7 BUILT: Wed Nov 12 12:39:46 CST 2014 cmirror-2.02.114-2.el7 BUILT: Mon Dec 1 10:57:14 CST 2014 [root@host-115 ~]# lvcreate -s /dev/cache_sanity/corigin -c 64 -n merge -L 500M Snapshots of cache type volume cache_sanity/corigin is not supported. *** Bug 1105732 has been marked as a duplicate of this bug. *** 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/RHBA-2015-0513.html |