[Gluster-users] Gluster snapshot fails
Rafi Kavungal Chundattu Parambil
rkavunga at redhat.com
Wed Apr 10 13:05:01 UTC 2019
The name of device is not at all a problem here. Can you please check the log of glusterd, and see if there is any useful information about the failure. Also please provide the output of `lvscan` and `lvs --noheadings -o pool_lv` from all nodes
----- Original Message -----
From: "Strahil Nikolov" <hunter86_bg at yahoo.com>
To: gluster-users at gluster.org
Sent: Wednesday, April 10, 2019 2:36:39 AM
Subject: [Gluster-users] Gluster snapshot fails
I have a problem running a snapshot of a replica 3 arbiter 1 volume.
[root at ovirt2 ~]# gluster snapshot create before-423 engine description "Before upgrade of engine from 4.2.2 to 4.2.3"
snapshot create: failed: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of engine are thinly provisioned LV.
Snapshot command failed
Volume Name: engine
Volume ID: 30ca1cc2-f2f7-4749-9e2e-cee9d7099ded
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Brick3: ovirt3:/gluster_bricks/engine/engine (arbiter)
All bricks are on thin lvm with plenty of space, the only thing that could be causing it is that ovirt1 & ovirt2 are on /dev/gluster_vg_ssd/gluster_lv_engine , while arbiter is on /dev/gluster_vg_sda3/gluster_lv_engine.
Is that the issue ? Should I rename my brick's VG ?
If so, why there is no mentioning in the documentation ?
Gluster-users mailing list
Gluster-users at gluster.org
More information about the Gluster-users