Is this fork still maintained? about enhanceio

[lanconnected]

Hi guys! Thanks a lot for your interest in my work, this fork is maintained, and i'll do my best to keep compatibility with modern kernels and to address reported issues. The documentation is a bit (quite a big bit) outdated, sorry for that, i'll get to it once i add all new features i want to the code. If somebody is willing to help with documentation, don't hesitate to contact me :)
We are using enhanceio intensively in our internal projects, always in write-back mode and we did not have any data loss or crashes for the last 2 years or so. That is the main reason there are no new commits - we are (almost) satisfied with the current code. There are packages available for RHEL6 kernels, if someone is interested, i'll add .spec file and packaging instructions.

[onlyjob]

Do you know of any packaging of your fork to Debian format (.deb)?

@adamryczkowski, here is the EnhanceIO package from official Debian repositories:

https://packages.debian.org/search?searchon=sourcenames&keywords=enhanceio

As of 2020 the package is based on this repository.

[ojgarciab]

This was the last commit (Compatibility for kernels >= 4.14), 9 months ago: 69565a2

[adamryczkowski]

Thanks! I would really want to give it a try.
Do you know of any packaging of your fork to Debian format (.deb)? If not, tell me, are the installation instructions (Install.txt) still relevant for current kernels?

Do you use cache write-through write-back and how stable it is in your opinion?

[ojgarciab]

I used it without write-back in root (global) device. Sorry, I can't help you with installation instructions. I had a trick to compile the new code with old dkms package, but it was almost two years ago. Now I'm using lvmcache.

[adamryczkowski]

I just tried it on XUbuntu 16.04 virtual guest under VirtualBox for non-root drive. The installation instructions worked flawlessly and there were no problems whatsoever. I tested write back and it really works. Udev scripts also were able to restore the device automatically after reboot. Since both virtual block devices I used for testing were backed by the same SSD drive, I cannot vouch for the actual caching performance, but definitely both "ssd" and "spinning disk" parts were used, when using the eio device.

The kernel was 4.15.0-34-generic.

[ojgarciab]

Thanks for the update @lanconnected, I stopped using enhanceio due to the increasing difficulty of compiling using Ubuntu / DKMS (to avoid recompiling every kernel update).
I'll give it a try later and help with documentation related to debian / ubuntu, but I don't know when I'll have time to do it :( I would like to help.

[adamryczkowski]

That is a great news. How about the LFU caching algorithm, do you have any plans on implementing it? cf. stec-inc#91

[MasterCATZ]

thanks for the fork, you should provide PayPal or bitcoin address :P,
however, the reason I am looking for a cache system is that I am sick of the zfs Kernel / DKMS build fails ... and moving to SnapRaid and looking for a way to handle my smaller files better

[pasikarkkainen]

@lanconnected Hey! You mentioned earlier in this issue that you're happily using EnhanceIO on el6. Are you also using it on el7 these days, or still on el6 only? I'm interested in stability experiences on el7 (from others aswell). Thanks!

[pasikarkkainen]

Bump. How's the stability on el7 ?