Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Known issue: unique identifier for drive #98

Open
Leo-Yan opened this issue Jul 10, 2020 · 1 comment
Open

Known issue: unique identifier for drive #98

Leo-Yan opened this issue Jul 10, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Leo-Yan
Copy link
Contributor

Leo-Yan commented Jul 10, 2020

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.

@Leo-Yan Leo-Yan added the enhancement New feature or request label Jul 10, 2020
@TProhofsky
Copy link
Collaborator

I know of two ways to get WWN:

  1. udevadm info /dev/sdc |grep "ID_WWN="
  2. ls -lta /dev/disk/by-id/wwn* |grep -v "-part"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants