[LU-3531] DNE2: striped directory

• Type: Improvement
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.6.0
• Severity: 3
• Assignee: Di Wang
• Reporter: Di Wang

Description

This ticket is for tracking striped directory in DNE phase II.

Issue Links

• is duplicated by: LU-4559 Failure on test suite ost-pools test_23b: client oom
• is related to: LU-4603 NFS reexport leads to problems of "ls"
• is related to: LU-4573 sanityn test_76 fails on DNE (512 != 2048 open files)
• is related to: LU-4571 sanity test_17n: create remote dir error 0
• is related to: LU-4401 sanityn test_13 : f13 shouldn't return an error (1)
• is related to: LUDOC-198 Complete Lustre Manual updates for DNE Phase II
• is related to: LU-6660 interop DNE2 test between 2.5/2.7 clients and DNE2 servers
• is related to: LU-6661 Interop DNE2 test between DNE2 clients and 2.5/2.7 servers
• is related to: LU-4562 parallel-scale test_connectathon: didn't read '.' dir entry, pass 0
• is related to: LU-4850 DNE Striped Directory - Changing default striping only works on MDT0
• is related to: LU-4883 mdc_set_lock_data()) ASSERTION( old_inode->i _state & I_FREEING ) failed: ...
• is related to: LU-4897 dt_declare_delete()) ASSERTION( dt->do_index_ops ) failed (in orphan cleanup)
• is related to: LU-4925 bad negative dentry caching in striped directory
• is related to: LU-4420 sanity test_161a: cannot create regular file '...f.sanity.161a': Input/output error
• is related to: LU-4657 add [--delete|-d] option for lfs setdirstripe to delete the default striping from the directory.
• is related to: LU-4715 creating enough files in a directory causes '.' to disappear
• is related to: LU-4929 create remote directory does not accept mode or handle umask properly
• is related to: LU-4930 osd_object_destroy()) ASSERTION( osd_inode_unlinked(inode) || inode->i_nlink == 1 || inode->i_nlink == 2 ) failed
• is related to: LU-4521 mdc_read_entry() leaks pages
• is related to: LU-4945 req_capsule_get: Wrong buffer for field `name' (5 of 6) in format `LDLM_INTENT_GETATTR': 3 vs. 0 (client)
• is related to: LU-4921 DNE clients should fall back to "try all stripes" for lookups in directories with unknown hash functions
• is related to: LU-4684 DNE3: allow migrating DNE striped directory

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch http://review.whamcloud.com/17392/
Subject: LU-3531 doc: update lfs migrate and mkdir documentation.
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: af4dfdeb689a5c8b86184480525fec9a6d36699a

[Gerrit Updater]

Richard Henwood ([e-mail]) uploaded a new patch: http://review.whamcloud.com/17392
Subject: LU-3531 doc: remove redundant documentation.
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 7967e9239f554179a7df6721509238fb0a40ef72

[Patrick Farrell (Inactive)]

I learned from reading remote_dir.sh that in addition to lfs setdirstripe, there is a -c option to lfs mkdir that creates striped directories. Is this documented anywhere? It is not in the usage message for lfs mkdir or in the man page.

There also appears to be a -D option to set default striping on a new directory, which acts the same way as lfs setdirstripe.

Updating the usage messages (and the man page) should be part of adding these new options if we want users to be able to use them.
[lfs setdirstripe is also absent from the lfs man page]

Should -D work when creating a new directory? It does not currently. If it's not supposed to work, that should be reflected in the usage message for lfs setdirstripe and lfs mkdir [since all of the other options work when making a new directory]...

It also seems like it should have a helpful error message, rather than "unable to open":
lfs setdirstripe -i 3 -c 3 -D test_dir5
unable to open 'test_dir5': No such file or directory (2)
error: setdirstripe: create stripe dir 'test_dir5' failed