Add support for overlayfs #106
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: philmmanjaro
Since linux318 overlayfs is supported within Manjaro Linux. Currently we are using aufs within buildiso for all kernels. It would be also good to support another filesystem for our install medias. Here is a small example for how to use overlayfs:
A full documentation can be found here.
Created by: Kirek
Even it's it supported since linux318, until linux40 it didn't gain all features we need: multiple lower layers.
Created by: philmmanjaro
Yes, only with linux40 or higher we should enable overlayfs. That's why we should re-add displaying kernel version in -q switch again.
Created by: Kirek
First try
github.com/manjaro/manjaro-tools@2a06b641c1Created by: ryanvade
Is there a benefit to using overlayfs?
Created by: philmmanjaro
@ryanvade: if we don't try we never would know. To have options is always good. We try to use it anyway with our Manjaro 0.9-series ...
Created by: telephone
It's pretty awesome with profile-sync-daemon and anything-sync-daemon 👍.
Created by: Kirek
With overlayfs branch an linux40 it currently boot to desktop (checked kde and xfce) using only overlayfs, seems to be some problems with starting calamares thought.
Created by: philmmanjaro
@Kirek: can you post me any terminal log of calamares using the -d switch? Does thus start up?
Created by: Kirek
After testing thus (crashed when trying to rsync the new system because the thus.conf was not created in that iso), tried calamares again and started. It seems it didn't like the system partitions and closed itself, after thus recreated the partitions it worked fine...
Rebooted, and installed the new system with calamares without problems.
Created by: philmmanjaro
@Kirek: Calamares don't support lvm/luks yet. That's why. Regarding thus, yes - the config needed to be modified first. This means your work is "working" ;). Please adjust the code as mentioned by @udeved earlier and push all overlayfs related stuff in a separate lib we can source.
Created by: udeved
The idea is to dynamically source the proper lib according to switch, and we adjust the code and use same function names for the two file system mount operations.
Created by: Kirek
What's to separate? they are one line commands...
Created by: udeved
Nevermind, is it ready to merge?
Created by: udeved
I actually like the overlayfs.
It much better in handling mounted images.
Need to correct couple of things though after my changes, but very nice.
Created by: udeved
Whats the mimimum kernel req for overlayfs so we can document it in the config?
Starting with 4.0 series?
3.19 doesn't work, 4.1 does.
Created by: Kirek
4.0 is the minimum, it added support for multiple lower layers
Created by: udeved
Ah, thx, exactly what the error cause, joining multiple images.
Created by: philmmanjaro
Currently I'm building 4.1 again. Somehow the i686 build doesn't boot up on my end. I might have found a patch for that matter, still don't know why x86_64 boots, though ...
Created by: udeved
I will try with kernel 4.0.
I've only tested x86_64 iso yet, but building with overlayfs enabled is fine.
Created by: philmmanjaro
With build I ment the kernel itself. I always hit a kernel fault.