[LU-4847] cl_default_mds_easize might be 0 in mdc_intent_getattr_pack Created: 01/Apr/14  Updated: 29/Sep/20  Resolved: 21/Apr/14

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

Type: Bug Priority: Critical
Reporter: Di Wang Assignee: Di Wang
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
Severity: 3
Rank (Obsolete): 13358

 Description   

After http://review.whamcloud.com/6339 is landed, mdc will rely on the cl_default_mds_mdsize, which might be zero in some cases, especially for mdc, which is connected to non-zero MDT.

For example if client tries to access a remote striped directory, which is located on MDT2, and cl_default_mds_mdsize on mdc-MDT2 is still zero(because it still not get default mdsize from MDS2 yet, then MDT would not return stripe information for this striped dir at all. Then this dir will be mis-regarded as a non-striped dir.

So we may need check whether cl_default_mds_mdsize is zero in mdc_intent_getattr_pack, if it is 0, it might use cl_max_mds_mdsize instead.



 Comments   
Comment by Di Wang [ 21/Apr/14 ]

http://review.whamcloud.com/9862

Comment by Di Wang [ 21/Apr/14 ]

patches landed to 2.6

Generated at Sat Feb 10 01:46:22 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.