Details
-
Improvement
-
Resolution: Unresolved
-
Critical
-
None
-
9223372036854775807
Description
For DNE filesystems where there are large numbers of remote entries, for example once LU-4684 is landed to restripe directories, or DNE2 striped directories with many renames, the size of the REMOTE_PARENT_DIR may become very large.
In order to limit contention and scaling issues in REMOTE_PARENT_DIR it makes sense to have multiple such directories. As a starting point, one REMOTE_PARENT_DIR_MDTxxxx for each remote MDT would be useful, but it may be necessary to have a tree of directories similar to the O/<seq>/dN object directories. Having a separate REMOTE_PARENT_DIR_MDTxxxx per MDT would also allow LFSCK to efficiently scan remote entries for a given MDT, if there was a problem (e.g. MDT was marked offline and returned into the namespace later).
Attachments
Issue Links
- has to be done before
-
LU-11025 DNE3: directory restripe
- Resolved
-
LU-10784 DNE3: mkdir() automatically create remote directory on MDS which has more space
- Resolved
- is related to
-
LU-15383 DNE directories not connected to REMOTE_PARENT_DIR
- Open
-
LU-4876 LFSCK remove entry from /REMOTE_PARENT_DIR if MDT-object name reside on the same MDT after migration
- Open
-
LU-11446 ldiskfs inodes nlink mismatch with DNE
- Open
-
LU-11502 add striped directory migration support in racer test
- Open
-
LU-15330 ext2fs_get_pathname() very slow for large directory
- Open
-
LU-17818 LMR: Lustre Metadata Redundancy
- Open
-
LU-12310 MDT Device-level Replication/Mirroring
- Open
-
LU-15307 Option to set max directory stripe count per filesystem
- Resolved
-
LU-13440 DNE3: limit directory default layout inheritance
- Resolved
- is related to
-
LU-12892 Large directory feature is not enabled (REMOTE_PARENT_DIR)
- Resolved
-
LU-11546 enable large_dir support for MDTs
- Resolved
-
LU-10192 Agent entry for cross-MDTs reference
- Resolved
-
LU-4684 DNE3: allow migrating DNE striped directory
- Resolved