You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current implementation, IDM lock manager uses ptable's UUID as its unique identifier. But it has risk for it might not the unique identifier for drives in big cluster.
This issue can be reproduced by below command:
# make check_lvmlockd_idm LVM_TEST_FAILURE_INJECTION=1 T=idm_ilm_fabric_failure.sh
To resolve this issue, some proposals for unique identifier:
WWN;
Seagate drive's model number + serial number.
Wait for Tom's suggestion for this.
The text was updated successfully, but these errors were encountered:
In current implementation, IDM lock manager uses ptable's UUID as its unique identifier. But it has risk for it might not the unique identifier for drives in big cluster.
This issue can be reproduced by below command:
To resolve this issue, some proposals for unique identifier:
Wait for Tom's suggestion for this.
The text was updated successfully, but these errors were encountered: