[LU-10838] replay-single/89 fails with a single client Created: 22/Mar/18  Updated: 06/May/18  Resolved: 06/May/18

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Upstream
Fix Version/s: Lustre 2.12.0

Type: Bug Priority: Minor
Reporter: Alex Zhuravlev Assignee: Alex Zhuravlev
Resolution: Fixed Votes: 0
Labels: None
Environment:

single client setup


Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

when a single client is used, lfs df in client_up() doesn't really wait for recovery completion: ost1 is still waiting for missing client (just remoounted) and doesn't let new client to connection leaving corresponding OSC connection inactive. then check for ltd_active in lov_iocontrol() skips that inactive connection and lfs df finishes. in presence of another client similar ltd_active is set, so lfs df blocks on OSC connection to restarted ost1.

 



 Comments   
Comment by Gerrit Updater [ 22/Mar/18 ]

Alex Zhuravlev (alexey.zhuravlev@intel.com) uploaded a new patch: https://review.whamcloud.com/31729
Subject: LU-10838 tests: replay-single/89 to wait for recovery
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 301ba1f8b193e16b57ded2ee61f3f643d6305ed2

Comment by Gerrit Updater [ 06/May/18 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/31729/
Subject: LU-10838 tests: replay-single/89 to wait for recovery
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 8020bf0cc8a055a9b5ae347b8b1ac582113686bc

Comment by Peter Jones [ 06/May/18 ]

Landed for 2.12

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