We have moved to a new Sailfish OS Forum. Please start new discussions there.
4

/fimage/SailfishOS-2.1.3.5-f5121-0.0.1.16

asked 2017-11-11 11:15:06 +0300

objectifnul gravatar image

updated 2017-11-11 11:58:55 +0300

As I said elsewhere, my reflashed 32Gb Xperia has less than 200 Mb of available system data space, which doesn't allow to reinstall everything my 'old' 16Gb Jolla1 could easily accommodate.

Is it safe to empty the huge /fimage/SailfishOS-2.1.3.5-f5121-0.0.1.16 folder (containing home.img.gz and root.img.gz) to gain more system space?

Comments

Isn't that the factory reset image?

Dylan Van Assche ( 2017-11-11 11:18:51 +0300 )

Probably yes. I have a back-up of both. Now I'm considering to remove them from the phone or to replace them with symlinks.

objectifnul ( 2017-11-11 11:22:13 +0300 )

Symlink to SD card or internal Flash is possible I think?

Dylan Van Assche ( 2017-11-11 11:28:00 +0300 )

It's possible for sure. But will it allow me to reset/restore the device in case of need?

objectifnul ( 2017-11-11 11:36:20 +0300 )
add a comment

3 Answers

Sort by » oldest newest most voted
3

answered 2017-11-11 12:53:04 +0300

ghling gravatar image

SFOS X uses the partitioning scheme from Android. Due to that, there are so many partitions and some space is lost to the partition where the recovery image is located (since the image is much smaller than the size of the partition). However, as already mentioned, deleting the recovery image does not add space to your system partition. For that you would have to repartition.

Caution, Jolla strongly advises against repartitioning the storage on the Xperia X. Some of the partitions contain vital data for the system to function (like drivers and other stuff which can't be restored), deleting them will literally brick your phone (e.g. removing the partition for the modem will render it unusable without any possibility to restore, so you would end up with a device which can't use any mobile connections any more). If you wanf more information, this issue was already discussed in the second to last community meeting (Log), starting at around 08:30.

link

Comments

Ok. I'll obviously avoid repartitioning. So far, the only way I found to gain some little extra space is moving largest system logs (/var/log) to the SDcard. This is clearly not enough, as available system space is constantly decreasing.

objectifnul ( 2017-11-11 13:23:04 +0300 )
1

Your best option is probably to shrink the user space partition and enlarge the system partition. This is a rather safe operation (though you still need to resize the two partitions). A guide on how to do that on the Jolla C can be found here: https://together.jolla.com/question/156279/installing-system-updates-fails-when-there-is-not-enough-space-in-system-data-partition/?answer=156670#post-id-156670 It should be the same for the Xperia X

ghling ( 2017-11-11 14:20:43 +0300 )

I don't think I will take a chance. parted -l shows 52 partitions (yes, fifty two), most of them being totally mysterious. I need not only a clear 'how-to', but also a better understanding of what is behind. My documentation and my knowledge of SailfishX are too poor.

objectifnul ( 2017-11-11 14:51:06 +0300 )

Additionally, this conclusion of the Oct. 18 meeting appears to be totally unacceptable for those who purchased SailfishX and an Xperia X device to host it:

(quote)

" no safe solutions exist to the two problems: losing 7 GB to factory reset, and too small system partition (rootfs); we'll have in mind to enlarge rootfs in future devices, for now just install less apps and use SD card ;) (sledges, 08:54:50)"

(end of quote)

I assume the OS development team will not consider this topic closed.

objectifnul ( 2017-11-11 18:20:08 +0300 )
1

I don't think Jolla is happy with the current situation. The big question is if there is a solution that is safe to implement and easy to use. Since touching some of the partitions means bricking the phone, I'm pretty sure Jolla is not taking any chances here. Nobody wants their phone to get "destroyed" by an update. And even if there is a possibility it still depends if this can be done on-the-fly or requires reflashing etc. I guess we'll have to wait and see.

ghling ( 2017-11-11 19:50:08 +0300 )
add a comment
2

answered 2017-11-11 11:41:12 +0300

Pasko gravatar image

Hi.

I see this folder is mounted under a different partition:

[nemo@Sailfish ~]$ mount | grep fimage
/dev/mmcblk0p52 on /fimage type ext4 (rw,noatime,data=ordered)
[nemo@Sailfish ~]$ mount | grep /dev/mmcblk0p52
/dev/mmcblk0p52 on /fimage type ext4 (rw,noatime,data=ordered)
[nemo@Sailfish ~]$

And this probably means that even deleting the files the free space would not addup to the system partition. Indeed I think you would have to repartition to take advantage of the new free space...

Best regards.

link

Comments

1

OK, thanks. I'm afraid repartitioning is beyond my skills. Hopefully, next SailfishX release will solve this critical issue.

objectifnul ( 2017-11-11 11:46:21 +0300 )
add a comment
0

answered 2017-11-11 18:55:32 +0300

DarkTuring gravatar image

Clear available space and try:

The nemo home running out of its 2GB alotted and arguably SUPER tiny space is a different issue than the OS taking up 15GB.

Here is the way to increase it to 5GB.

https://together.jolla.com/question/156279/installing-system-updates-fails-when-there-is-not-enough-space-in-system-data-partition/?answer=156670#post-id-156670

There are a few file tree programs that are great at showing large files that are safe to delete (map offline tiles and downloads and left over apps);

I would not touch the restore image.

link
add a comment
Login/Signup to Answer

Question tools

Follow
2 followers

Stats

Asked: 2017-11-11 11:15:06 +0300

Seen: 795 times

Last updated: Nov 11 '17