RGBCube/Site
1
Fork 0
mirror of https://github.com/RGBCube/Site synced 2025-07-29 20:17:46 +00:00
Code Issues Activity Actions

dump(posix.fsync-pitfalls): update

Browse source
This commit is contained in:
RGBCube 2025-07-11 23:41:49 +03:00
parent ad7e1a12c1
commit a765c5fadc
Signed by: RGBCube
SSH key fingerprint: SHA256:CzqbPcfwt+GxFYNnFVCqoN5Itn4YFrshg1TrnACpA5M
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
site/dump/posix/fsync-pitfalls.md
View file

@ -71,9 +71,10 @@ wrong. You can imagine a directory as a file containing a list of children, and
the list is just pointers to inodes. So `fsync`ing a directory will just write
the list of pointers to disk.
## More reading on `fsync`
## More reading on `fsync` and other things related to files
- [(danluu) Fsyncgate: Errors on `fsync` are unrecoverable](https://danluu.com/fsyncgate/)
- [(danluu) Files are hard](https://danluu.com/file-consistency/)
- [(puzpuzpuz) The secret life of `fsync`](https://puzpuzpuz.dev/the-secret-life-of-fsync)
- [(stackoverflow) Difference between `syncfs` (Linux only) and `fsync` (POSIX)](https://stackoverflow.com/questions/48171855/what-is-the-difference-between-fsync-and-syncfs)
(TL;DR: `syncfs` is "pretty please" fsync and doesn't block until the