In the file .vh.sf you should find 1024 entries for "abcdef0"
[root@localhost:/vmfs/volumes/5d94db91-49223634-6ebf-000c294514fd] od -t x4 .vh.sf | grep -c "abcdef0"
1024
The vast majority should have abcdef01 while a small number can have abcdef02.
Do you see entries with abcdef03 or abcdef04 ?
I am trying to figure out if the entries abcdef03 and abcdef04 are the result of corruption or wether they are the result of a new unknown feature.
If you see those entries - do you have problems with locked files ?
Ulli
>> od -t x4 .vh.sf | grep -c "abcdef04"
This is a valid type of lock - so not alarming in itself ....
Just in case someone reads this post ...
Ullio
It is very easy to find out if you are affected - the commands are harmless and will be done in seconds
od -t x4 .vh.sf | grep -c "abcdef01"
od -t x4 .vh.sf | grep -c "abcdef02"
od -t x4 .vh.sf | grep -c "abcdef03"
od -t x4 .vh.sf | grep -c "abcdef04"
Please post the numbers you get ...
od -t x4 .vh.sf | grep -c "abcdef0"
1024
od -t x4 .vh.sf | grep -c "abcdef01"
1019
od -t x4 .vh.sf | grep -c "abcdef02"
5
od -t x4 .vh.sf | grep -c "abcdef03"
0
od -t x4 .vh.sf | grep -c "abcdef04"
0
Here is one example
4 .vh.sf | grep -c "abcdef01"
1017
[root@:/vmfs/volumes/5d150907-61796d8f-e46a-40f2e94eaed0] od -t x
4 .vh.sf | grep -c "abcdef02"
7
[root@:/vmfs/volumes/5d150907-61796d8f-e46a-40f2e94eaed0] od -t x
4 .vh.sf | grep -c "abcdef03"
0
[root@:/vmfs/volumes/5d150907-61796d8f-e46a-40f2e94eaed0] od -t x
4 .vh.sf | grep -c "abcdef04"
0
and here is another
[root@:/vmfs/volumes/5d02705f-34bfa70d-8e66-3440b5e214f8] od -t x
4 .vh.sf | grep -c "abcdef01"
1018
[root@:/vmfs/volumes/5d02705f-34bfa70d-8e66-3440b5e214f8] od -t x
4 .vh.sf | grep -c "abcdef02"
6
[root@:/vmfs/volumes/5d02705f-34bfa70d-8e66-3440b5e214f8] od -t x
4 .vh.sf | grep -c "abcdef03"
0
[root@:/vmfs/volumes/5d02705f-34bfa70d-8e66-3440b5e214f8] od -t x
4 .vh.sf | grep -c "abcdef04"
0
Thanks - those numbers show a healthy datastore
Hi,
[root@esxi02:/vmfs/volumes/5ba6e07e-9a0d2779-98b5-0050568ce6af] od -t x4 .vh.sf | grep -c "abcdef01"
1023
[root@esxi02:/vmfs/volumes/5ba6e07e-9a0d2779-98b5-0050568ce6af] od -t x4 .vh.sf | grep -c "abcdef02"
1
[root@esxi02:/vmfs/volumes/5ba6e07e-9a0d2779-98b5-0050568ce6af] od -t x4 .vh.sf | grep -c "abcdef03"
0
[root@esxi02:/vmfs/volumes/5ba6e07e-9a0d2779-98b5-0050568ce6af] od -t x4 .vh.sf | grep -c "abcdef04"
0
no problems here
Please help me ....
at the moment I think that a lock with abcdef03 is an indication of a corrupt heartbeat.
I am not sure about abcdef04 ....
If I have more numbers I can create a patch to fix the problem ...
Thanks
New locktype abcdef04 confirmed.
Still not sure if it is a bug or a feature.
Please report if you see it - it would help to find out in which conditions it is used.
At the moment I dont know how to fix it with minimal invasive operations ...
Ulli
I just asked the same question in a professional forum ...
New locktype for VMFS heartbeat entries ? - Veeam Community Forums
>> od -t x4 .vh.sf | grep -c "abcdef04"
This is a valid type of lock - so not alarming in itself ....
Just in case someone reads this post ...
Ullio