View Single Post
Posts: 1,335 | Thanked: 3,931 times | Joined on Jul 2010 @ Brittany, France
#355
Originally Posted by meemorph View Post
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
I am trying that on an X Compact (Sailfish X patched from here). The phone has been running Sailfish X for weeks with no issues. I went into Recovery mode (using this and this).

Except some Input/Output warnings at the beginning (but other people have had this too with no consequences), everything seemed to go well until "resize2fs /dev/sailfish/home". At this step, I get the following:

Code:
/ # 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.
/ #
And unfortunately "e2fsck -fy /dev/sailfish/home" fails too:

Code:
/ # 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
Any ideas? I haven't rebooted yet because I'm afraid it will fail, but on the other hand I don't expect to receive an answer tonight. :<
 

The Following User Says Thank You to Kabouik For This Useful Post: