Description of problem: seeing thousands of SEEK* errors in two bricks' logs on one particular node, gluster02.example.com. The following shows the start of the errors: [server-rpc-fops.c:2091:server_seek_cbk] 0-vol01-server: 4947: SEEK-2 (53920aee-062c-4598-aa50-2b4d7821b204), client: worker.example.com-7808-2019/02/08-18:04:57:903430-vol01-client-0-0-0, error-xlator: vol01-posix [Invalid argument] Version-Release number of selected component (if applicable): glusterfs server 3.12.2 on el6 How reproducible: Run an application on an el7 gluster client, against a glusterfs server on el6. The application should call lseek() with whence=SEEK_HOLE/SEEK_DATA. Actual results: glusterfs server on el6 fills the brick logs, disk can run out of space quickly Expected results: no logging if this is correct behaviour, limit logging in case it is an error.
REVIEW: https://review.gluster.org/22526 (core: only log seek errors if SEEK_HOLE/SEEK_DATA is available) posted (#1) for review on master by Niels de Vos
REVIEW: https://review.gluster.org/22526 (core: only log seek errors if SEEK_HOLE/SEEK_DATA is available) merged (#3) on master by Amar Tumballi