[LU-11648] Create white list for CONFIGS directory files processing Created: 09/Nov/18 Updated: 04/Aug/22 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Artem Blagodarenko (Inactive) | Assignee: | Artem Blagodarenko |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
Not all files that are stored in CONFIGS directory should be processed. For example there are ".bak" files which created during change_nids operation and used to store non-modified copy. Currently blacklist is used to process CONFIGS directory (".bak"s are excluded), but using whitelist looks more robust. Here is example of some MDT CONFIG directory list # ls /mnt/fs2mdt/CONFIGS/ lustre-client lustre-MDT0000 lustre-MDT0001 lustre-MDT0002 lustre-MDT0003 lustre-OST0000 lustre-OST0001 lustre-OST0002 lustre-OST0003 mountdata nodemap params params, node map, mountdata, client, *-MDT, -OST are allowed. What else? |
| Comments |
| Comment by Andreas Dilger [ 10/Nov/18 ] |
|
I would say not all *OST* and *MDT* files, only ones that end with *-OSTxxxx and *-MDTxxxx. |