[LU-4029] DNE (distributed namespace) and legacy filesystems Created: 30/Sep/13 Updated: 16/Sep/17 Resolved: 16/Sep/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Josh Fryman (Inactive) | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Rank (Obsolete): | 10825 | ||||||||
| Description |
|
As part of the training class ongoing in HF3-TR4 with Brett Lee . . . the question came up that when DNE is fully supported, how will legacy systems take advantage of this? The crude answer is to temporarily rename all 10PB of disk files, then rename them back. This should trigger a rebalance of the metadata. Obviously that's not a very good solution, so the question is whether a tuning parameter or the like could be added - or perhaps a new tool - that would rebalance files and directories in DNE. |
| Comments |
| Comment by Keith Mannthey (Inactive) [ 02/Oct/13 ] |
|
Users will need to upgrade to the proper version of Lustre to take advantage newer features. The core DNE Phase 1 was landed in 2.4, https://jira.hpdd.intel.com/browse/LU-1187. Generally newer clients are supported with older servers but most features are in the Server. All Lustre servers should be of the same Lustre version. Am I misunderstanding your question? |