[LU-13499] client UUID is truncated Created: 01/May/20 Updated: 10/Jun/20 Resolved: 14/May/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.14.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Andreas Dilger | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | LTS12 | ||
| Issue Links: |
|
||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
I've noticed in various places in debug logs that the client UUID is being truncated. [ 5934.778609] Lustre: MGS: Connection restored to aafbfe59-7811-4 (at 10.9.6.193@tcp) This turns out to be a problem wherever the UUID is shown: # lctl get_param -n llite.*.uuid 595f3c6a-20ae-4 # lctl get_param -n mdc.*.uuid 595f3c6a-20ae-4 Initially I thought something was wrong with the "safe" string handling in obd_uuid2str(), but it turns out that there is a bug when the client UUID is originally generated in ll_fill_super() because of the use of UUID_SIZE, which is actually the size of the binary uuid_t instead of the ASCII UUID (stored in struct obd_uuid) that is passed between nodes and printed to the logs. |
| Comments |
| Comment by Gerrit Updater [ 01/May/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/38443 |
| Comment by Gerrit Updater [ 14/May/20 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/38443/ |
| Comment by Peter Jones [ 14/May/20 ] |
|
Landed for 2.14 |