[LU-13560] 'lfs mkdir -i N' should be 'sticky' on a particular MDT Created: 15/May/20  Updated: 13/May/22  Resolved: 06/Jan/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.14.0, Lustre 2.12.4
Fix Version/s: Lustre 2.15.0

Type: Improvement Priority: Minor
Reporter: Andreas Dilger Assignee: Lai Siyao
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Cloners
is cloned by LU-15856 "lfs setdirstripe -D ... <dir>" shoul... Open
Related
is related to LU-13417 DNE3: mkdir() automatically create re... Resolved
is related to LU-10784 DNE3: mkdir() automatically create re... Resolved
Rank (Obsolete): 9223372036854775807

 Description   

In discussion with Lai and Jian, it makes sense that "lfs mkdir -i N" be "sticky" on a particular MDT, in the same way that it was before 2.15 introduced MDT space balance, since that is what users expect (the few that actually use "lfs mkdir -i" in the first place) and is the "more obvious" behavior. If a user is running "lfs mkdir -i N" then they want the directory to be on a specific MDT, and that matches the existing behavior better. The majority of users that don't know/use "lfs mkdir" will probably want (and get) the MDTs to be balanced automatically.

That means by default that the 2.15+ "lfs mkdir -i N" should also include a default directory layout for the same MDT. It would be possible to override this with "--max-inherit=0|-X 0".



 Comments   
Comment by Gerrit Updater [ 19/Oct/21 ]

"Lai Siyao <lai.siyao@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45290
Subject: LU-13560 lod: set default LMV for "lfs mkdir -c 1"
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 959a271ad88e1a7437ee4e263d4cd0609d759c7e

Comment by Gerrit Updater [ 06/Jan/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45290/
Subject: LU-13560 lod: set default LMV for "lfs mkdir -c 1"
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: bc2d7f065af6b4f9a69bc7d3d250b948b33a1018

Comment by Peter Jones [ 06/Jan/22 ]

Landed for 2.15

Comment by Andreas Dilger [ 13/May/22 ]

I updated the summary and description of this ticket to match the actual patch that was landed, and moved the original summary/description to a separate ticket LU-15856.

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