<html><head></head><body><div class="ydpf10cc4c6yahoo-style-wrap" style="font-family: courier new, courier, monaco, monospace, sans-serif; font-size: 16px;"><div></div>
<div>Hi Rafi,</div><div><br></div><div>thanks for your update.</div><div><br></div><div>I have tested again with another gluster volume.</div><div><span>[root@ovirt1 glusterfs]# gluster volume info isos<br><br>Volume Name: isos<br>Type: Replicate<br>Volume ID: 9b92b5bd-79f5-427b-bd8d-af28b038ed2a<br>Status: Started<br>Snapshot Count: 0<br>Number of Bricks: 1 x (2 + 1) = 3<br>Transport-type: tcp<br>Bricks:<br>Brick1: ovirt1:/gluster_bricks/isos/isos<br>Brick2: ovirt2:/gluster_bricks/isos/isos<br>Brick3: ovirt3.localdomain:/gluster_bricks/isos/isos (arbiter)<br>Options Reconfigured:<br>cluster.granular-entry-heal: enable<br>performance.strict-o-direct: on<br>network.ping-timeout: 30<br>storage.owner-gid: 36<br>storage.owner-uid: 36<br>user.cifs: off<br>features.shard: on<br>cluster.shd-wait-qlength: 10000<br>cluster.shd-max-threads: 8<br>cluster.locking-scheme: granular<br>cluster.data-self-heal-algorithm: full<br>cluster.server-quorum-type: server<br>cluster.quorum-type: auto<br>cluster.eager-lock: enable<br>network.remote-dio: off<br>performance.low-prio-threads: 32<br>performance.io-cache: off<br>performance.read-ahead: off<br>performance.quick-read: off<br>transport.address-family: inet<br>nfs.disable: on<br>performance.client-io-threads: off<br>cluster.enable-shared-storage: enable</span><br></div><div><br></div><div>Command run:<br></div><div><span>logrotate -f glusterfs ; logrotate -f glusterfs-georep; gluster snapshot create isos-snap-2019-04-11 isos description TEST<br></span><span></span><div><br></div><div>Logs:</div><div><span>[root@ovirt1 glusterfs]# cat cli.log<br>[2019-04-11 07:51:02.367453] I [cli.c:769:main] 0-cli: Started running gluster with version 5.5<br>[2019-04-11 07:51:02.486863] I [MSGID: 101190] [event-epoll.c:621:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1<br>[2019-04-11 07:51:02.556813] E [cli-rpc-ops.c:11293:gf_cli_snapshot] 0-cli: cli_to_glusterd for snapshot failed<br>[2019-04-11 07:51:02.556880] I [input.c:31:cli_batch] 0-: Exiting with: -1<br>[root@ovirt1 glusterfs]# cat glusterd.log<br>[2019-04-11 07:51:02.553357] E [MSGID: 106024] [glusterd-snapshot.c:2547:glusterd_snapshot_create_prevalidate] 0-management: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of isos are thinly provisioned LV.<br>[2019-04-11 07:51:02.553365] W [MSGID: 106029] [glusterd-snapshot.c:8613:glusterd_snapshot_prevalidate] 0-management: Snapshot create pre-validation failed<br>[2019-04-11 07:51:02.553703] W [MSGID: 106121] [glusterd-mgmt.c:147:gd_mgmt_v3_pre_validate_fn] 0-management: Snapshot Prevalidate Failed<br></span><div><span>[2019-04-11 07:51:02.553719] E [MSGID: 106121] [glusterd-mgmt.c:1015:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed for operation Snapshot on local node<br></span></div><div><br></div><div><div>My LVs hosting the bricks are:</div><div><span>[root@ovirt1 ~]# lvs gluster_vg_md0<br> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert<br> gluster_lv_data gluster_vg_md0 Vwi-aot--- 500.00g my_vdo_thinpool 35.97<br> gluster_lv_isos gluster_vg_md0 Vwi-aot--- 50.00g my_vdo_thinpool 52.11<br> my_vdo_thinpool gluster_vg_md0 twi-aot--- 9.86t 2.04 11.45<br><br></span><span>[root@ovirt1 ~]# ssh ovirt2 "lvs gluster_vg_md0"<br> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert<br> gluster_lv_data gluster_vg_md0 Vwi-aot--- 500.00g my_vdo_thinpool 35.98<br> gluster_lv_isos gluster_vg_md0 Vwi-aot--- 50.00g my_vdo_thinpool 25.94<br> my_vdo_thinpool gluster_vg_md0 twi-aot--- <9.77t 1.93 11.39<br>[root@ovirt1 ~]# ssh ovirt3 "lvs gluster_vg_sda3"<br> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert<br> gluster_lv_data gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.17<br> gluster_lv_engine gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.16<br> gluster_lv_isos gluster_vg_sda3 Vwi-aotz-- 15.00g gluster_thinpool_sda3 0.12<br> gluster_thinpool_sda3 gluster_vg_sda3 twi-aotz-- 41.00g 0.16 1.58<br><br></span><div>As you can see - all bricks are thin LV and space is not the issue.</div><div><br></div><div>Can someone hint me how to enable debug , so gluster logs can show the reason for that pre-check failure ?</div><div><br></div><div>Best Regards,</div><div>Strahil Nikolov<br></div></div><span></span></div></div><div><br></div></div><div><br></div>
</div><div id="ydp848d3c78yahoo_quoted_5091806849" class="ydp848d3c78yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
В сряда, 10 април 2019 г., 9:05:15 ч. Гринуич-4, Rafi Kavungal Chundattu Parambil <rkavunga@redhat.com> написа:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Strahil,<br clear="none"><br clear="none">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<br clear="none"><br clear="none">Regards<br clear="none">Rafi KC<br clear="none"><div class="ydp848d3c78yqt0187791214" id="ydp848d3c78yqtfd10892"><br clear="none">----- Original Message -----<br clear="none">From: "Strahil Nikolov" <<a shape="rect" href="mailto:hunter86_bg@yahoo.com" rel="nofollow" target="_blank">hunter86_bg@yahoo.com</a>><br clear="none">To: <a shape="rect" href="mailto:gluster-users@gluster.org" rel="nofollow" target="_blank">gluster-users@gluster.org</a><br clear="none">Sent: Wednesday, April 10, 2019 2:36:39 AM<br clear="none">Subject: [Gluster-users] Gluster snapshot fails<br clear="none"><br clear="none">Hello Community, <br clear="none"><br clear="none">I have a problem running a snapshot of a replica 3 arbiter 1 volume. <br clear="none"><br clear="none">Error: <br clear="none">[<a shape="rect" href="mailto:root@ovirt2" rel="nofollow" target="_blank">root@ovirt2</a> ~]# gluster snapshot create before-423 engine description "Before upgrade of engine from 4.2.2 to 4.2.3" <br clear="none">snapshot create: failed: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of engine are thinly provisioned LV. <br clear="none">Snapshot command failed <br clear="none"><br clear="none">Volume info: <br clear="none"><br clear="none">Volume Name: engine <br clear="none">Type: Replicate <br clear="none">Volume ID: 30ca1cc2-f2f7-4749-9e2e-cee9d7099ded <br clear="none">Status: Started <br clear="none">Snapshot Count: 0 <br clear="none">Number of Bricks: 1 x (2 + 1) = 3 <br clear="none">Transport-type: tcp <br clear="none">Bricks: <br clear="none">Brick1: ovirt1:/gluster_bricks/engine/engine <br clear="none">Brick2: ovirt2:/gluster_bricks/engine/engine <br clear="none">Brick3: ovirt3:/gluster_bricks/engine/engine (arbiter) <br clear="none">Options Reconfigured: <br clear="none">cluster.granular-entry-heal: enable <br clear="none">performance.strict-o-direct: on <br clear="none">network.ping-timeout: 30 <br clear="none">storage.owner-gid: 36 <br clear="none">storage.owner-uid: 36 <br clear="none">user.cifs: off <br clear="none">features.shard: on <br clear="none">cluster.shd-wait-qlength: 10000 <br clear="none">cluster.shd-max-threads: 8 <br clear="none">cluster.locking-scheme: granular <br clear="none">cluster.data-self-heal-algorithm: full <br clear="none">cluster.server-quorum-type: server <br clear="none">cluster.quorum-type: auto <br clear="none">cluster.eager-lock: enable <br clear="none">network.remote-dio: off <br clear="none">performance.low-prio-threads: 32 <br clear="none">performance.io-cache: off <br clear="none">performance.read-ahead: off <br clear="none">performance.quick-read: off <br clear="none">transport.address-family: inet <br clear="none">nfs.disable: on <br clear="none">performance.client-io-threads: off <br clear="none">cluster.enable-shared-storage: enable <br clear="none"><br clear="none"><br clear="none">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. <br clear="none"><br clear="none">Is that the issue ? Should I rename my brick's VG ? <br clear="none">If so, why there is no mentioning in the documentation ? <br clear="none"><br clear="none"><br clear="none">Best Regards, <br clear="none">Strahil Nikolov </div><br clear="none"><br clear="none"><br clear="none">_______________________________________________<br clear="none">Gluster-users mailing list<br clear="none"><a shape="rect" href="mailto:Gluster-users@gluster.org" rel="nofollow" target="_blank">Gluster-users@gluster.org</a><br clear="none"><a shape="rect" href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="nofollow" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><div class="ydp848d3c78yqt0187791214" id="ydp848d3c78yqtfd14983"><br clear="none"></div></div></div>
</div>
</div></body></html>