You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say that we boot to a disk at /, then resize2fs will happily online resize it.
But what we do in skiff-init-squashfs is then mount an overlayfs and a squashfs from / and then chroot into a different root. Then what happens is / is now a chroot, resize2fs doesn't detect that it needs online resizing, and fails to resize it.
There is a fix for this somewhere in making a patch for resize2fs to always do online resizing.
Let's say that we boot to a disk at /, then resize2fs will happily online resize it.
But what we do in skiff-init-squashfs is then mount an overlayfs and a squashfs from / and then chroot into a different root. Then what happens is / is now a chroot, resize2fs doesn't detect that it needs online resizing, and fails to resize it.
There is a fix for this somewhere in making a patch for resize2fs to always do online resizing.
Related: #272
cc @maxberger
The text was updated successfully, but these errors were encountered: