Re: [Gluster-devel] How to solve the FSYNC() ERR

Yes, I just used a text editor i.e. vi to test this out, but my real application is surveillance camera system. The video was stored in GlusterFS by FUSE and Samba. Because of the surveillance camera system 7*24 working mode, it doesn't have to cache the files. So I added O_DIRECT flag

Re: [Gluster-devel] How to solve the FSYNC() ERR

What's the application you are running? Sounds like you're using a text editor like vi(m) to test this out? Is the application opening the files with O_DIRECT? Do you have the strace output of the running application that confirms that it is open()ing the file with O_DIRECT? Also, what are the

Re: [Gluster-devel] How to solve the FSYNC() ERR

I have checked the page-aligned, i.e. the file was larger than one page, a part of the file(one page size) was saved successfully, and the rest(more than one page but less than two pages) was lost. At 2016-07-11 12:53:32, "Pranith Kumar Karampuri" wrote: Is it

Re: [Gluster-devel] How to solve the FSYNC() ERR

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

Re: [Gluster-devel] How to solve the FSYNC() ERR

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:

Re: [Gluster-devel] How to solve the FSYNC() ERR

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.

Re: [Gluster-devel] How to solve the FSYNC() ERR

Pranith/Krutika, Your inputs please, IIRC we'd need to turn on some o_direct option here? On Saturday 9 July 2016, Keiviw wrote: > The errors also occured in GlusterFS 3.6.7，I just add the O_DIRECT flag in > client protocol open() and create()! How to explain and solve the

[Gluster-devel] How to solve the FSYNC() ERR

hi, I have installed GlusterFS 3.3.0, and now I get Fsync failures when saving files with the O_DIRECT flag in open() and create(). 1, I tried to save a flie in vi and got this error: "test" E667: Fsync failed 2, I see this in the logs: [2016-07-07 14:20:10.325400]