Why overlayfs increases boot time?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












Recently, I started using overlay filesystem. I'm using initram script (init=/sbin/myint) as described in Raspberry blog - raspberry overlay, yet, I noticed that it increases boot time significantly (about 10 seconds).



Is this increase in time happening because of mounting overlay filesystem?



EDIT:



I see that if I do the mount in init script instead of fstab file, then the additional time is reduced. Yet, I am not sure what's the difference.
in fstab:



/dev/mmcblock5 /app ext4 defaults 0 0
overlay /app overlay defaults,lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2


(/temp is mounted in initram script (init=/sbin/myint), see the link above)
in /etc/local.d/01.start
:



mount -t overlay -o lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2 none /app









share|improve this question























  • Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
    – slm♦
    Aug 19 at 18:22










  • I use overlay, not overlay2.
    – ransh
    Aug 19 at 18:25










  • Try w/ overlay2 to see if that's the issue.
    – slm♦
    Aug 19 at 18:25






  • 1




    you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
    – sourcejedi
    Aug 19 at 19:51











  • I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
    – ransh
    Aug 20 at 7:52















up vote
1
down vote

favorite












Recently, I started using overlay filesystem. I'm using initram script (init=/sbin/myint) as described in Raspberry blog - raspberry overlay, yet, I noticed that it increases boot time significantly (about 10 seconds).



Is this increase in time happening because of mounting overlay filesystem?



EDIT:



I see that if I do the mount in init script instead of fstab file, then the additional time is reduced. Yet, I am not sure what's the difference.
in fstab:



/dev/mmcblock5 /app ext4 defaults 0 0
overlay /app overlay defaults,lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2


(/temp is mounted in initram script (init=/sbin/myint), see the link above)
in /etc/local.d/01.start
:



mount -t overlay -o lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2 none /app









share|improve this question























  • Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
    – slm♦
    Aug 19 at 18:22










  • I use overlay, not overlay2.
    – ransh
    Aug 19 at 18:25










  • Try w/ overlay2 to see if that's the issue.
    – slm♦
    Aug 19 at 18:25






  • 1




    you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
    – sourcejedi
    Aug 19 at 19:51











  • I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
    – ransh
    Aug 20 at 7:52













up vote
1
down vote

favorite









up vote
1
down vote

favorite











Recently, I started using overlay filesystem. I'm using initram script (init=/sbin/myint) as described in Raspberry blog - raspberry overlay, yet, I noticed that it increases boot time significantly (about 10 seconds).



Is this increase in time happening because of mounting overlay filesystem?



EDIT:



I see that if I do the mount in init script instead of fstab file, then the additional time is reduced. Yet, I am not sure what's the difference.
in fstab:



/dev/mmcblock5 /app ext4 defaults 0 0
overlay /app overlay defaults,lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2


(/temp is mounted in initram script (init=/sbin/myint), see the link above)
in /etc/local.d/01.start
:



mount -t overlay -o lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2 none /app









share|improve this question















Recently, I started using overlay filesystem. I'm using initram script (init=/sbin/myint) as described in Raspberry blog - raspberry overlay, yet, I noticed that it increases boot time significantly (about 10 seconds).



Is this increase in time happening because of mounting overlay filesystem?



EDIT:



I see that if I do the mount in init script instead of fstab file, then the additional time is reduced. Yet, I am not sure what's the difference.
in fstab:



/dev/mmcblock5 /app ext4 defaults 0 0
overlay /app overlay defaults,lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2


(/temp is mounted in initram script (init=/sbin/myint), see the link above)
in /etc/local.d/01.start
:



mount -t overlay -o lowerdir=/app,upperdir=/mnt/temp/upper2,workdir=/mnt/temp/work2 none /app






filesystems overlayfs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 20 at 7:56

























asked Aug 19 at 18:08









ransh

344249




344249











  • Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
    – slm♦
    Aug 19 at 18:22










  • I use overlay, not overlay2.
    – ransh
    Aug 19 at 18:25










  • Try w/ overlay2 to see if that's the issue.
    – slm♦
    Aug 19 at 18:25






  • 1




    you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
    – sourcejedi
    Aug 19 at 19:51











  • I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
    – ransh
    Aug 20 at 7:52

















  • Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
    – slm♦
    Aug 19 at 18:22










  • I use overlay, not overlay2.
    – ransh
    Aug 19 at 18:25










  • Try w/ overlay2 to see if that's the issue.
    – slm♦
    Aug 19 at 18:25






  • 1




    you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
    – sourcejedi
    Aug 19 at 19:51











  • I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
    – ransh
    Aug 20 at 7:52
















Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
– slm♦
Aug 19 at 18:22




Are you loading overlay or overlay2? - unix.stackexchange.com/questions/328978/docker-and-overlayfs.
– slm♦
Aug 19 at 18:22












I use overlay, not overlay2.
– ransh
Aug 19 at 18:25




I use overlay, not overlay2.
– ransh
Aug 19 at 18:25












Try w/ overlay2 to see if that's the issue.
– slm♦
Aug 19 at 18:25




Try w/ overlay2 to see if that's the issue.
– slm♦
Aug 19 at 18:25




1




1




you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
– sourcejedi
Aug 19 at 19:51





you could try comparing the output of systemd-analyze blame and/or systemd-analyze plot > plot.svg. It might show which parts of the boot process happen more slowly / later on.
– sourcejedi
Aug 19 at 19:51













I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
– ransh
Aug 20 at 7:52





I made some progress , I see that if I mount the overlay in init script instead of fstab, the additional time is reduced. quite strange. any idea what's the difference ? The question was edited
– ransh
Aug 20 at 7:52
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463527%2fwhy-overlayfs-increases-boot-time%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463527%2fwhy-overlayfs-increases-boot-time%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?