Description of problem: With https://review.gluster.org/#/q/status:merged+project:glusterfs+branch:master+topic:ref-1568521 in, where fops that might decrement link count - such as UNLINK and RENAME - rely on file link count before cleaning up shards, which is determined under locks, it is important for LINK also to acquire locks to prevent inconsistencies stemming from premature deletion of shards while the inode continues to exist. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Status?
I don't plan to fix this anytime soon. It's a good bug to fix for beginners as it provides some amount of exposure to the way shard and locks translators work. I'll keep this and any other not-so-urgent bzs raised in future reserved for using to mentor someone.
As per Comment#2