[LU-10597] lfs mv vs stat deadlock Created: 01/Feb/18  Updated: 20/Jan/22

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Andriy Skulysh Assignee: Andriy Skulysh
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Related
is related to LU-7383 migrate failed: Device or resource b... Resolved
is related to LU-11502 add striped directory migration suppo... Open
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Deadlock happens when migrating object has links and linked object has the same parent as migrating directory's parent.

It is a regression caused by

commit 5cb0a721aea53ffc8230190c3a0b35e71a47d35b
Author: Di Wang <di.wang@intel.com>
Date:   Tue Nov 3 07:32:13 2015 -0800

    LU-7383 mdt: retry for busy lock during migration

Unlocking linkea objects doesn't help in this case.

 Comments   
Comment by Gerrit Updater [ 01/Feb/18 ]

Andriy Skulysh (c17819@cray.com) uploaded a new patch: https://review.whamcloud.com/31130
Subject: LU-10597 test: lfs migrate vs stat deadlock
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 1ada59a8e67b473e4ecc17e9c3a6d3bdb6e47380

Comment by Andriy Skulysh [ 02/Feb/18 ]

I suppose LU-7383 should be reverted because it introduces bigger problem than fixes.
In fact I don't understand why linkea object's parents are locked at all, there are might be more links to the file than objects in linkea.

Comment by Andreas Dilger [ 20/Jan/22 ]

It looks like there is still a useful test case in https://review.whamcloud.com/31130

Generated at Sat Feb 10 02:36:30 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.