[Bugs] [Bug 1697316] New: Getting SEEK-2 and SEEK7 errors with [Invalid argument] in the bricks' logs

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1697316

            Bug ID: 1697316
           Summary: Getting SEEK-2 and SEEK7 errors with [Invalid
                    argument] in the bricks' logs
           Product: GlusterFS
           Version: mainline
            Status: ASSIGNED
         Component: core
          Assignee: ndevos at redhat.com
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org
            Blocks: 1696903
  Target Milestone: ---
    Classification: Community



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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.