[Bugs] [Bug 1548517] write failed with EINVAL due O_DIRECT write buffer with unaligned size

bugzilla at redhat.com bugzilla at redhat.com
Tue Nov 19 15:04:19 UTC 2019


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

Olaf Buitelaar <olaf.buitelaar at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olaf.buitelaar at gmail.com



--- Comment #3 from Olaf Buitelaar <olaf.buitelaar at gmail.com> ---
i'm seeing a similar issue on gluster 6.6 with centos 7 (kernel 
3.10.0-1062.4.3.el7.x86_64);

[2019-11-19 14:56:04.017381] E [MSGID: 113072]
[posix-inode-fd-ops.c:1886:posix_writev] 0-ovirt-data-posix: write failed:
offset 0, [Invalid argument]
[2019-11-19 14:56:04.017462] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-ovirt-data-server: 221969:
WRITEV 0 (309c077f-8882-43f7-a95b-ca2c4d27d2b5), client:
CTX_ID:b3c80b69-0651-4e87-96d1-ee767cb7e425-GRAPH_ID:10-PID:19184-HOST:lease-16.dc01.adsolutions-PC_NAME:ovirt-data-client-1-RECON_NO:-0,
error-xlator: ovirt-data-posix [Invalid argument]
[2019-11-19 14:56:12.430962] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-ovirt-data-server: 219748:
WRITEV 0 (921dfa09-b252-4087-9c7c-47eda2a6266d), client:
CTX_ID:05f7b92c-8dd6-434b-b835-7254dae1d1bc-GRAPH_ID:4-PID:93937-HOST:lease-23.dc01.adsolutions-PC_NAME:ovirt-data-client-1-RECON_NO:-0,
error-xlator: ovirt-data-posix [Invalid argument]
[2019-11-19 14:56:27.345631] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-ovirt-data-server: 203815:
WRITEV 4 (981676ff-6dbe-4a4c-8478-6e4f991a04f4), client:
CTX_ID:366e668d-91ba-4373-960e-82e56f1ed7af-GRAPH_ID:0-PID:22624-HOST:lease-08.dc01.adsolutions-PC_NAME:ovirt-data-client-1-RECON_NO:-0,
error-xlator: ovirt-data-posix [Invalid argument]
[2019-11-19 14:56:45.491788] E [MSGID: 115067]
[server-rpc-fops_v2.c:1373:server4_writev_cbk] 0-ovirt-data-server: 210249:
WRITEV 2 (a27a81c0-de78-40ee-9855-a62b6be01ffe), client:
CTX_ID:4472864a-0fec-4e2c-ad3f-b9684b0808f6-GRAPH_ID:0-PID:30323-HOST:lease-21.dc01.adsolutions-PC_NAME:ovirt-data-client-1-RECON_NO:-0,
error-xlator: ovirt-data-posix [Invalid argument]

Also i notice the cpu usage when this error occurs is very high.

The volume is configured with O_DIRECT;
Volume Name: ovirt-data
Type: Distributed-Replicate
Volume ID: 2775dc10-c197-446e-a73f-275853d38666
Status: Started
Snapshot Count: 0
Number of Bricks: 4 x (2 + 1) = 12
Transport-type: tcp
Bricks:
Brick1: 10.201.0.5:/data5/gfs/bricks/brick1/ovirt-data
Brick2: 10.201.0.1:/data5/gfs/bricks/brick1/ovirt-data
Brick3: 10.201.0.9:/data0/gfs/bricks/bricka/ovirt-data (arbiter)
Brick4: 10.201.0.7:/data5/gfs/bricks/brick1/ovirt-data
Brick5: 10.201.0.9:/data5/gfs/bricks/brick1/ovirt-data
Brick6: 10.201.0.11:/data0/gfs/bricks/bricka/ovirt-data (arbiter)
Brick7: 10.201.0.6:/data5/gfs/bricks/brick1/ovirt-data
Brick8: 10.201.0.8:/data5/gfs/bricks/brick1/ovirt-data
Brick9: 10.201.0.12:/data0/gfs/bricks/bricka/ovirt-data (arbiter)
Brick10: 10.201.0.12:/data5/gfs/bricks/brick1/ovirt-data
Brick11: 10.201.0.11:/data5/gfs/bricks/brick1/ovirt-data
Brick12: 10.201.0.10:/data0/gfs/bricks/bricka/ovirt-data (arbiter)
Options Reconfigured:
performance.strict-o-direct: on
server.event-threads: 6
performance.cache-size: 384MB
performance.write-behind-window-size: 512MB
user.cifs: off
features.shard: on
cluster.shd-wait-qlength: 10000
cluster.shd-max-threads: 8
cluster.locking-scheme: granular
cluster.data-self-heal-algorithm: full
cluster.server-quorum-type: server
cluster.quorum-type: auto
cluster.eager-lock: enable
network.remote-dio: off
performance.low-prio-threads: 32
performance.stat-prefetch: off
performance.io-cache: off
performance.read-ahead: off
performance.quick-read: off
nfs.disable: on
performance.readdir-ahead: on
transport.address-family: inet
storage.owner-uid: 36
storage.owner-gid: 36
server.outstanding-rpc-limit: 1024
cluster.choose-local: off
cluster.brick-multiplex: on

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


More information about the Bugs mailing list