Create a troubleshooting entry for the lock error message

[shcheklein]

From time to time users are getting a message like this:

ERROR: cannot perform the command because another DVC process seems to be running on this project. If that is not the case, manually remove .dvc/tmp/lock and try again.

(and even removing .dvc/tmp/lock doesn't help in this case)

when they run DVC on some Network fs (NFS, Lustre, etc).

Example: https://discordapp.com/channels/485586884165107732/563406153334128681/727222314080665682

Usually solution is simple and user needs to enable the core.hardlink_lock, but it's hard to get that from the error message.

To save us and users time we should create a troubleshooting entry and include link to the error message.

[moinnadeem]

I'm getting this issue; how would I enable the core.hardlink_lock?

[efiop]

@moinnadeem

dvc config core.hardlink_lock true

https://dvc.org/doc/command-reference/config 🙂

[shcheklein]

@moinnadeem hi! just to clarify and make sure that this ticket is the right one- have you tried to remove the .dvc/tmp/lock file (first make sure that no DVC commands are running) first? Do you use NFS or Lustre or some other network/distributed file system?

[moinnadeem]

@shcheklein Yes, and yes! I'm on a networked filesystem that doesn't allow file-level locking either. Using hardlinking solved it!

I appreciate the quick response!

[shcheklein]

@moinnadeem perfect! :) thanks for clarifying.