Thank you, very nice hint. I can confirm that it works. I added 4GB to rootfs (btw: I have /home/nemo on the sd card). what I did on my XperiaX (recovery shell): Code: lvm lvm> lvscan ACTIVE '/dev/sailfish/root' [2.44 GiB] inherit ACTIVE '/dev/sailfish/home' [18.25 GiB] inherit lvm> exit resize2fs /dev/sailfish/home 11G lvm lvm> lvresize -L -4096M /dev/sailfish/home lvm> lvresize -l +100%FREE /dev/sailfish/root lvm> lvscan ACTIVE '/dev/sailfish/root' [6.44 GiB] inherit ACTIVE '/dev/sailfish/home' [14.25 GiB] inherit lvm> exit resize2fs /dev/sailfish/home resize2fs /dev/sailfish/root exit
lvm lvm> lvscan ACTIVE '/dev/sailfish/root' [2.44 GiB] inherit ACTIVE '/dev/sailfish/home' [18.25 GiB] inherit lvm> exit resize2fs /dev/sailfish/home 11G lvm lvm> lvresize -L -4096M /dev/sailfish/home lvm> lvresize -l +100%FREE /dev/sailfish/root lvm> lvscan ACTIVE '/dev/sailfish/root' [6.44 GiB] inherit ACTIVE '/dev/sailfish/home' [14.25 GiB] inherit lvm> exit resize2fs /dev/sailfish/home resize2fs /dev/sailfish/root exit
/ # resize2fs /dev/sailfish/home resize2fs 1.43.1 (08-Jun-2016) Resizing the filesystem on /dev/sailfish/home to 4144128 (4k) blocks. resize2fs: Can't read a block bitmap while trying to resize /dev/sailfish/home Please run 'e2fsck -fy /dev/sailfish/home' to fix the filesystem after the aborted resize operation. / #
/ # e2fsck -fy /dev/sailfish/home e2fsck 1.43.1 (08-Jun-2016) The filesystem size (according to the superblock) is 5192704 blocks The physical size of the device is 4144128 blocks Either the superblock or the partition table is likely to be corrupt! Abort? yes