[LU-14983] actually use CONFIGS/mountdata in server code Created: 03/Sep/21 Updated: 04/Sep/21 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.15.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | James A Simmons | Assignee: | James A Simmons |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Any Lustre server backend. |
||
| Issue Links: |
|
||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
With the separation of the of the user land code and server code struct lustre_disk_data was moved to the user land mount utility. This data is stored on the ldiskfs server backend but is never used by the server code which really doesn't make sense. We should make this a standard feature for both ldiskfs and ZFS and take advantage of this data. I could see this being used by the MGS to automount all the other servers with the proper mount options. |
| Comments |
| Comment by Peter Jones [ 04/Sep/21 ] |
|
I take it that you plan to work on this James |