[Bugs] [Bug 1178031] New: [SNAPSHOT]: fails to create on thin LV with LUKS layer in between

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 1 17:11:58 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1178031

            Bug ID: 1178031
           Summary: [SNAPSHOT]: fails to create on thin LV with LUKS layer
                    in between
           Product: GlusterFS
           Version: 3.6.1
         Component: snapshot
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: pille+redhat+bugzilla at struction.de
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:

my bricks are on XFS on LUKS on thin-LV.
creating a shapshot fails.


Steps to Reproduce:
1. create bricks on thin-LV, but with additional LUKS encryption layer
2. gluster snapshot ...

Actual results:

snapshot create: failed: Snapshot is supported only for thin provisioned LV.
Ensure that all bricks of storage_www are thinly provisioned LV.
Snapshot command failed


Expected results:

snapshot


Additional info:

[2015-01-01 16:41:35.047033] E
[glusterd-snapshot.c:1742:glusterd_is_thinp_brick] 0-management: Failed to get
pool name for device /dev/mapper/data
[2015-01-01 16:41:35.047128] E
[glusterd-snapshot.c:2081:glusterd_snapshot_create_prevalidate] 0-management:
Snapshot is supported only for thin provisioned LV. Ensure that all bricks of
storage_www are thinly provisioned LV.
[2015-01-01 16:41:35.047139] W
[glusterd-snapshot.c:7013:glusterd_snapshot_prevalidate] 0-management: Snapshot
create pre-validation failed
[2015-01-01 16:41:35.047146] W [glusterd-mgmt.c:154:gd_mgmt_v3_pre_validate_fn]
0-management: Snapshot Prevalidate Failed
[2015-01-01 16:41:35.047151] E
[glusterd-mgmt.c:675:glusterd_mgmt_v3_pre_validate] 0-management: Pre
Validation failed for operation Snapshot on local node
[2015-01-01 16:41:35.047156] E
[glusterd-mgmt.c:1850:glusterd_mgmt_v3_initiate_snap_phases] 0-management: Pre
Validation Failed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list