log-level=ERROR mount option not working in gluster, W level messages rapidly filling up storage
Issue
I am seeing a high volume of warning level messages that seem to be coming from a defect in one of our applications (in this case, EBADF errors). While figuring out this issue, the W level messages need to be suppressed, because they are rapidly filling up storage.
This should be doable with the following mount option:
log-level=LOG-LEVEL
Logging severity. Valid options are TRACE, DEBUG, WARNING, ERROR, CRITICAL INFO and NONE [default: INFO]
But even with this option in place, the client log is still rapidly filling up with W level messages:
[2018-xx-xx 19:34:38.225605] W [MSGID: 114031] [client-rpc-fops.c:3002:client3_3_readv_cbk] 0-home-client-3: remote operation failed [Bad file descriptor]
[2018-xx-xx 19:34:38.226525] W [MSGID: 114031] [client-rpc-fops.c:3002:client3_3_readv_cbk] 0-home-client-2: remote operation failed [Bad file descriptor]
[2018-xx-xx 19:34:38.226633] W [fuse-bridge.c:2228:fuse_readv_cbk] 0-glusterfs-fuse: 7223: READ => -1 gfid=ef78d2ed-382a-4c22-a410-b100a3dc6ecd fd=0x7fa16401206c (Bad file descriptor)
[2018-xx-xx 19:34:38.227251] W [MSGID: 114031] [client-rpc-fops.c:3002:client3_3_readv_cbk] 0-home-client-3: remote operation failed [Bad file descriptor]
Environment
- Red Hat Gluster Storage 3.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
