You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found weird situation: if I constantly use fsync application works steadily, but if I change it on fsyncdata, it sometimes returns error: Bad file descriptor (os error 9). In linux man I found only one thing, which MAY cause an error (but does it?): (read the paragraph, which start from fdatasync() is similar to fsync()) https://man7.org/linux/man-pages/man2/fdatasync.2.html.
So do I understand it right: if some data sensitive metadata changed (size, for example) fdatasync returns error? I am a little bit confused, because bad file descriptor doesn't point on need to fsync metadata either.
Sorry in advance if this question is silly, I am not experienced enough:C
The text was updated successfully, but these errors were encountered:
I am sorry, I'll show you my case, in which it doesn't work appropriate way: qoollo/pearl@aab6804
After this changes ioring started to work steadily. You may run tests for both versions and see the differences (run them twice for bad version and on the second run it'll return many errors)
I found weird situation: if I constantly use
fsync
application works steadily, but if I change it onfsyncdata
, it sometimes returns error:Bad file descriptor (os error 9)
. In linux man I found only one thing, which MAY cause an error (but does it?): (read the paragraph, which start from fdatasync() is similar to fsync()) https://man7.org/linux/man-pages/man2/fdatasync.2.html.So do I understand it right: if some data sensitive metadata changed (size, for example) fdatasync returns error? I am a little bit confused, because
bad file descriptor
doesn't point onneed to fsync metadata either
.Sorry in advance if this question is silly, I am not experienced enough:C
The text was updated successfully, but these errors were encountered: