Gluster brick logs are filling up with EBADF errors. What is causing this?
Issue
I am seeing errors like these filling up the logs in /var/log/glusterfs/bricks:
[2017-11-30 14:32:49.063339] E [MSGID: 113040] [posix.c:3190:posix_readv] 0-home-posix: read failed on gfid=4a2c80b8-0080-4fb1-9503-00dbf1ed7e8a, fd=0x7f4c810635f0, offset=0 size=131072, buf=0x7f4d0ef91000 [Bad file descriptor]
[2017-11-30 14:32:49.063454] E [MSGID: 115068] [server-rpc-fops.c:1397:server_readv_cbk] 0-home-server: 3756052: READV 2 (4a2c80b8-0080-4fb1-9503-00dbf1ed7e8a) ==> (Bad file descriptor) [Bad file descriptor]
[2017-11-30 14:32:49.064119] E [MSGID: 113040] [posix.c:3190:posix_readv] 0-home-posix: read failed on gfid=b11e1798-4a19-4ded-ae26-aaac46f1066b, fd=0x7f4cfd22dd90, offset=0 size=131072, buf=0x7f4d0ef91000 [Bad file descriptor]
[2017-11-30 14:32:49.064225] E [MSGID: 115068] [server-rpc-fops.c:1397:server_readv_cbk] 0-home-server: 3756054: READV 1 (b11e1798-4a19-4ded-ae26-aaac46f1066b) ==> (Bad file descriptor) [Bad file descriptor]
How can I determine the cause of these errors?
Environment
- Red Hat Gluster Storage 3.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.