[LU-4522] ldlm_cli_enqueue and ll_inode_revalidate_fini LustreError messages on 2.4.1 clients Created: 21/Jan/14 Updated: 13/Sep/17 Resolved: 11/Mar/14 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.1 |
| Fix Version/s: | Lustre 2.6.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Oz Rentas | Assignee: | Andreas Dilger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 12365 | ||||||||
| Description |
|
From time to time, KIT are seeing ldlm_cli_enqueue and ll_inode_revalidate_fini LustreError messages. They mainly appear on login nodes of our clusters. Here is an example of the error messages: The Lustre client in this case is at version 2.4.1 plus patch for What do the messages mean, and how can we get rid of these error messages? |
| Comments |
| Comment by Oleg Drokin [ 21/Jan/14 ] |
|
Could this be that login nodes have some users that are not known to MDS, similar to |
| Comment by Andreas Dilger [ 24/Jan/14 ] |
|
In Lustre 1.8 we used to return -EIDRM (Identifier Removed) so that it was clear this was an issue with missing users in the MDS user database, rather than some other kind of permission problem. We should also avoid printing these messages on the console, since they are just a distraction. I pushed http://review.whamcloud.com/8988 to quiet the client error messages for the common -EACCES error message. |
| Comment by Oz Rentas [ 10/Mar/14 ] |
|
We can go ahead and close this one. Thanks. From the customer: |
| Comment by Andreas Dilger [ 11/Mar/14 ] |
|
Patch 8828 was landed to master for 2.6.0. |