Skip to content
This repository was archived by the owner on Jul 16, 2022. It is now read-only.
This repository was archived by the owner on Jul 16, 2022. It is now read-only.

Proper fsync on Windows #18

Closed
Closed

Description

@untitaker

See #6. This blogpost covers this issue in great detail. For Windows, this is mentioned:

On Windows, using FlushFileBuffers() is probably the way to go.

Not really a confident statement, more research needed.

Activity

  1. untitaker commented on Jul 26, 2016

    @untitaker
    OwnerAuthor

    We currently use _commit, which doesn't try to flush disk buffers. However, there is no indication that FlushFileBuffers is different in that regard.

  2. Dobatymo commented on Sep 15, 2020

    @Dobatymo

    First: _commit calls FlushFileBuffers internally (according to https://stackoverflow.com/a/1947818). Second: Where do you actually call _commit?

  3. untitaker commented on Sep 15, 2020

    @untitaker
    OwnerAuthor

    os.fsync is documented as calling _commit. I guess then this issue is not actionable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions