Why overlayfs increases boot time?
Clash 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
filesystems overlayfs
 |Â
show 1 more comment
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
filesystems overlayfs
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 ofsystemd-analyze blame
and/orsystemd-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
 |Â
show 1 more comment
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
filesystems overlayfs
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
filesystems overlayfs
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 ofsystemd-analyze blame
and/orsystemd-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
 |Â
show 1 more comment
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 ofsystemd-analyze blame
and/orsystemd-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
 |Â
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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/orsystemd-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