Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fsync and fsyncdata error cases #45

Open
Justarone opened this issue Mar 21, 2021 · 2 comments
Open

fsync and fsyncdata error cases #45

Justarone opened this issue Mar 21, 2021 · 2 comments

Comments

@Justarone
Copy link

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

@Justarone
Copy link
Author

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)

@Justarone
Copy link
Author

I misunderstood: fdatasync does update necessary metadata itself. Now I am totally confused, is it a bug then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant