Is it possible to share the test you are running? As per your volume,
o-direct is not enabled on your volume, i.e. the file shouldn't be opened
with o-direct but as per the logs it is giving Invalid Argument as if there
is something wrong with the arguments when we do o-direct write with wrong
My volume info:
Volume Name: test
Type: Distribute
Volume ID: 9294b122-d81e-4b12-9b5c-46e89ee0e40b
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: compute2:/home/brick1
Brick2: compute2:/home/brick2
Options Reconfigured:
To me it looks like a case of a flush triggering a write() that was cached
by write-behind and because the write buffer
did not meet the page alignment requirement with o-direct write, it was
failed with EINVAL and the trigger fop - i.e., flush() was failed with the
'Invalid argument' error code.