[LU-3272] block rename for FID_SEQ_DOT_LUSTRE, unify weird FID handling Created: 04/May/13  Updated: 27/Aug/13

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

Type: Improvement Priority: Minor
Reporter: John Hammond Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: fid, mdt

Issue Links:
Related
is related to LU-3245 FS root OBF regression Resolved
is related to LU-3181 open by FID for write with O_LOV_DELA... Resolved
Rank (Obsolete): 8109

 Description   

On LU-3245 Andreas said "Moving forward beyond the 6209 patch landing, it makes sense to explicitly block rename for the FID_SEQ_DOT_LUSTRE objects, since I don't think it ever makes sense to allow that."

We should also review the other reint handlers checking for consistency with respect to the weird FIDs and, I hope, factor the cases into one or more "client may access this FID for R/W/X/..."

 Comments   
Comment by Swapnil Pimpale (Inactive) [ 27/Aug/13 ]

Hi John,

I tried rename and mv on FIDs in .lustre/fid and it correctly gave me an "Operation not permitted" error in both the cases.
Could you please clarify as to what exactly is to be fixed here?

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