tanantharaman

I was just alerted by onlyjob that his writeboost wrapper script (listed in the dm-writeboost main page as a related project) already allows a backing device with data to be...

Thanks for the explanation. I can see the advantage of not having to unmount the device X for a local drive, which might require terminating all local jobs with open...

A simpler solution is to set /proc/sys/vm/vfs_cache_pressure to 1 (default is 100), which will keep the inode blocks in RAM, in preference to any data blocks. Also any inode blocks...

dm-writeboost does NOT support existing block devices with data, though there is an open enhancement request since 2017 to add that feature, specifically because EnhanceIO has it! With dm-writeboost, just...

> > dm-writeboost does NOT support existing block devices with data > > @tanantharaman, stop that nonsense already. I'm using _dm-writeboost_ with existing devices (with data) all the time, ever...

> @tanantharaman i use dm-writeboost, and i have setup it over a 4-years old raid5 device, it does NOT requires to recreate the backed device, you can enable or disable...

@onlyjob : Your response is much appreciated. I am stuck with Centos7 and cannot use Bcache so dm-writeboost seemed to be the only option but I was dreading having to...

@Ristovski : EnhanceIO with basic settings (random cache replacement policy) uses 4 bytes per 4KB SSD block, so around 0.1% of SSD. However if you choose FIFO cache replacement policy...