vault backup: 2025-01-19 21:14:51

1 files changed, 28 insertions, 0 deletions

diff --git a/0 Inbox/Writeback cache.md b/0 Inbox/Writeback cache.md
new file mode 100644
index 0000000..83495c4
--- /dev/null
+++ b/0 Inbox/Writeback cache.md
@@ -0,0 +1,28 @@
+---
+tags:
+  - linux
+  - qemu
+  - filesystem
+references:
+  - https://avidandrew.com/understanding-disk-cache-writeback-ext4.html
+  - https://docs.kernel.org/admin-guide/sysctl/vm.html#dirty-expire-centisecs
+---
+normal: write() -> cache (multiple layers) -> disk
+
+# Physical server write cache
+![[physical_write_cache.png]] 
+
+Page cache -> RAM
+
+Journal -> ensures data is fully written before the transaction is considered complete.
+`commit` mount option -> flushes cache to disk every x seconds (configurable)
+`barrier` mount option -> enables the ordering of groups of writes, controller ensures writes before barrier are written before writes after barrier.
+
+`commit` + dirty_expire_centisecs [2] ~ automatic persisting of data.
+
+If we call `sync`, `fsync` or `fdatasync` ourselves our data is forced on-disk right away by the kernel, no need to wait for commit + dirty_expirty_centisecs.
+
+# VM Write cache
+ Guest has its own page cache
+ ![[vm_write_cache.png]]
+ 
\ No newline at end of file