<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">Hi again,<br>
<br>
here is more information regarding issue described earlier<br>
<br>
It looks like self healing is stuck. According to "heal statistics"
crawl began at Sat Jan 20 12:56:19 2018 and it's still going on (It's
around Sun Jan 21 20:30 when writing this). However glustershd.log says
that last heal was completed at "2018-01-20 11:00:13.090697" (which is
13:00 UTC+2). Also "heal info" has been running now for over 16 hours
without any information. In statedump I can see that storage nodes have
locks on files and some of those are blocked. Ie. Here again it says
that ovirt8z2 is having active lock even ovirt8z2 crashed after the lock
was granted.:<br>
<br>
[xlator.features.locks.zone2-ssd1-vmstor1-locks.inode]<br>
path=/.shard/3d55f8cc-cda9-489a-b0a3-fd0f43d67876.27<br>
mandatory=0<br>
inodelk-count=3<br>
lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal<br>
inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid =
18446744073709551610, owner=d0c6d857a87f0000, client=0x7f885845efa0,
connection-id=sto2z2.xxx-10975-2018/01/20-10:56:14:649541-zone2-ssd1-vmstor1-client-0-0-0,
granted at 2018-01-20 10:59:52<br>
lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata<br>
lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0<br>
inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid =
3420, owner=d8b9372c397f0000, client=0x7f8858410be0,
connection-id=ovirt8z2.xxx.com-5652-2017/12/27-09:49:02:946825-zone2-ssd1-vmstor1-client-0-7-0,
granted at 2018-01-20 08:57:23<br>
inodelk.inodelk[1](BLOCKED)=type=WRITE, whence=0, start=0, len=0, pid =
18446744073709551610, owner=d0c6d857a87f0000, client=0x7f885845efa0,
connection-id=sto2z2.xxx-10975-2018/01/20-10:56:14:649541-zone2-ssd1-vmstor1-client-0-0-0,
blocked at 2018-01-20 10:59:52<br>
<br>
I'd also like to add that volume had arbiter brick before crash
happened. We decided to remove it because we thought that it was causing
issues. However now I think that this was unnecessary. After the crash
arbiter logs had lots of messages like this:<br>
[2018-01-20 10:19:36.515717] I [MSGID: 115072]
[server-rpc-fops.c:1640:server_setattr_cbk] 0-zone2-ssd1-vmstor1-server:
37374187: SETATTR <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe>
(a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not permitted)
[Operation not permitted]<br>
<br>
Is there anyways to force self heal to stop? Any help would be very much
appreciated :)<br>
<br>
Best regards,<br>
Samuli Heinonen<br>
<br>
<br>
<br>
<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:5A639F21.5010206@neutraali.net" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:samppah@neutraali.net"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Samuli Heinonen</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">20
January 2018 at 21.57</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hi all!
<br>
<br>One hypervisor on our virtualization environment crashed and now
some of
the VM images cannot be accessed. After investigation we found out that
there was lots of images that still had active lock on crashed
hypervisor. We were able to remove locks from "regular files", but it
doesn't seem possible to remove locks from shards.
<br>
<br>We are running GlusterFS 3.8.15 on all nodes.
<br>
<br>Here is part of statedump that shows shard having active lock on
crashed
node:
<br>[xlator.features.locks.zone2-ssd1-vmstor1-locks.inode]
<br>path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21
<br>mandatory=0
<br>inodelk-count=1
<br>lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata
<br>lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal
<br>lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0
<br>inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len=0, pid
=
3568, owner=14ce372c397f0000, client=0x7f3198388770, connection-id
ovirt8z2.xxx-5652-2017/12/27-09:49:02:946825-zone2-ssd1-vmstor1-client-1-7-0,
granted at 2018-01-20 08:57:24
<br>
<br>If we try to run clear-locks we get following error message:
<br># gluster volume clear-locks zone2-ssd1-vmstor1
/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 kind all inode
<br>Volume clear-locks unsuccessful
<br>clear-locks getxattr command failed. Reason: Operation not permitted
<br>
<br>Gluster vol info if needed:
<br>Volume Name: zone2-ssd1-vmstor1
<br>Type: Replicate
<br>Volume ID: b6319968-690b-4060-8fff-b212d2295208
<br>Status: Started
<br>Snapshot Count: 0
<br>Number of Bricks: 1 x 2 = 2
<br>Transport-type: rdma
<br>Bricks:
<br>Brick1: sto1z2.xxx:/ssd1/zone2-vmstor1/export
<br>Brick2: sto2z2.xxx:/ssd1/zone2-vmstor1/export
<br>Options Reconfigured:
<br>cluster.shd-wait-qlength: 10000
<br>cluster.shd-max-threads: 8
<br>cluster.locking-scheme: granular
<br>performance.low-prio-threads: 32
<br>cluster.data-self-heal-algorithm: full
<br>performance.client-io-threads: off
<br>storage.linux-aio: off
<br>performance.readdir-ahead: on
<br>client.event-threads: 16
<br>server.event-threads: 16
<br>performance.strict-write-ordering: off
<br>performance.quick-read: off
<br>performance.read-ahead: on
<br>performance.io-cache: off
<br>performance.stat-prefetch: off
<br>cluster.eager-lock: enable
<br>network.remote-dio: on
<br>cluster.quorum-type: none
<br>network.ping-timeout: 22
<br>performance.write-behind: off
<br>nfs.disable: on
<br>features.shard: on
<br>features.shard-block-size: 512MB
<br>storage.owner-uid: 36
<br>storage.owner-gid: 36
<br>performance.io-thread-count: 64
<br>performance.cache-size: 2048MB
<br>performance.write-behind-window-size: 256MB
<br>server.allow-insecure: on
<br>cluster.ensure-durability: off
<br>config.transport: rdma
<br>server.outstanding-rpc-limit: 512
<br>diagnostics.brick-log-level: INFO
<br>
<br>Any recommendations how to advance from here?
<br>
<br>Best regards,
<br>Samuli Heinonen
<br>
<br>_______________________________________________
<br>Gluster-users mailing list
<br><a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<br><a class="moz-txt-link-freetext" href="http://lists.gluster.org/mailman/listinfo/gluster-users">http://lists.gluster.org/mailman/listinfo/gluster-users</a>
<br></div>
</blockquote>
<br>
</body></html>