New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add lz4 initrd compression support for even faster mkrescue #1218
Comments
Apparently I did something wrong. The commit that was intended for a new pull request was merged with my earlier pull request. I don't know (yet) how to fix this. My uneducated guess is that I need to make a git branch somewhere in the process. Note: with REAR_INITRD_COMPRESSION="lz4" the 64M initrd file creation is now done in 4 till 5 seconds:
I can't test whether it boots correctly because I have an issue with:
|
@ProBackup-nl $ git checkout master $ git checkout -b implement_new_lz4_initrd_compression_issue1218 Switched to a new branch 'implement_new_lz4_initrd_compression_issue1218' code hacking $ git commit -am "implemented new lz4 initrd compression (issue 1218)" $ git push origin implement_new_lz4_initrd_compression_issue1218 Now my new branch In general see |
@ProBackup-nl $ git checkout master $ git checkout implement_new_lz4_initrd_compression_issue1218 Switched to branch 'implement_new_lz4_initrd_compression_issue1218' further code hacking $ git commit -am "improved lz4 initrd compression (issue 1218)" $ git push origin implement_new_lz4_initrd_compression_issue1218 |
With |
There is a bug in the code for this lz4 initramfs feature. When the initramfs of Arch Linux itself is build using
@jsmeix Should this issue be re-opened or a new issue created? |
|
Adding Linux legacy
|
Reopening because it needs some enhancement, see |
The strange thing here is that Arch Linux on the source system boots even with an |
Create initrd.lz4 with lz4 -l compression '-l' = legacy format is preferred because otherwise it may fail to get uncompressed, see #1218
Document initrd.lz4 with lz4 -l compression and comparison with other compression methods, see #1218
@ProBackup-nl As far as I understand it Because the ReaR recovery system uses the exact same kernel Because at the time when the kernel uncompresses the initrd That the difference must be in the initrds matches the fact A colleague told me that he thinks to remember in the past |
Even with REAR_INITRD_COMPRESSION="fast",
rear mkrescue
does spend significant time in compressing rootfs into a compressed initrd file. After inserting some bash timer code in 900_create_initramfs.sh, it seems that the creation of the 51M file takes 9 seconds.I'd wish support for the even faster lz4 codec, which seems understood by the Arch Linux kernel by default according to:
The text was updated successfully, but these errors were encountered: