Skip to main content
10 events
when toggle format what by license comment
Jun 23 at 4:25 comment added rsaxvc @Kolay.Ne, I think dirty_expire_centisecs + dirty_writeback_centisecs puts some bounds on when dirty data would trigger a flush operation to start.
Jun 27, 2021 at 9:46 comment added Kolay.Ne @Ini, I'm not 100% sure, so I'd appreciate confirmation or refutation of my words, but as far as I'm concerned, there are no time limits in the Linux caching/buffering algorithms, there only are memory limits. OS does not care how long is data buffered, it cares how big the buffer is. So, the flush to a file system happens when the buffer gets filled with changes (or when a partition is unmounted, a machine is shut down or hibernated, etc)
Mar 28, 2019 at 20:45 comment added Cray Battery-based cache in some disks is really not a reason to not optimize for power loss 1) that's only in expensive professional servers. Not all users will have this 2) it will only save you in the situation where the data has even reached the disk controller at all. In many cases it will be stuck in OS cache, long before the controller will ever see that data - and that will be lost in an event of a power failure.
Dec 17, 2018 at 11:28 comment added Ini The OS should anyway ensure that when you shutdown, that everything gets written to the ssd/hdd. In the case of a power-outage then you might loose some data. Is what I'm saying correct?
Dec 17, 2018 at 3:21 comment added bjd2385 @Ini seems it depends on the filesystem being used I believe.
Dec 9, 2018 at 1:00 comment added Ini async does not write for many seconds? How many seconds approximately?
Jun 8, 2018 at 11:59 comment added tonioc Modern servers have battery backed disk caches in RAID controllers, which will prevent from data loss even in case of a power loss.
Mar 12, 2018 at 10:55 review Late answers
Mar 12, 2018 at 10:57
Mar 12, 2018 at 10:40 review First posts
Mar 12, 2018 at 10:41
Mar 12, 2018 at 10:36 history answered Andreas Mikael Bank CC BY-SA 3.0