[help] My jolla slowly dying [answered]

-_- I can't manage to copy message from terminal, I feel really dumb...

@Xurb an easy way to do this is to SSH into your Jolla instead of opening a terminal (you can see the IP address in Settings -> Developer Mode) and then go on from there.

I can't connect my phone in SSH right now we have to wait this eve'...

Does it say 'size 13.75GiB used 13.75 GiB'? That's the important part.

Yup! you're right nthn that's what the first command line say whereas the phone say 11gigs of 13gigs... weird!

here are both of the output:

[nemo@Jolla ~]$ devel-su
Password:
[root@Jolla nemo]# btrfs fi show
ERROR: unable get label Inappropriate ioctl for device
Label: 'sailfish'  uuid: 0f8a2490-53ed-4ff6-ba34-b81df3430387
        Total devices 1 FS bytes used 10.97GiB
        devid    1 size 13.75GiB used 13.75GiB path /dev/mmcblk0p28

Btrfs v3.16
[root@Jolla nemo]# btrfs fi df /
Data, single: total=13.01GiB, used=10.73GiB
System, DUP: total=40.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00
Metadata, DUP: total=330.00MiB, used=245.25MiB
Metadata, single: total=8.00MiB, used=0.00
[root@Jolla nemo]#

I got the third line output as well, do you want me to past it?

Alright, you can fix this by:

• moving (a bunch of) (big) files to the SD card to free space
• after doing that, in the terminal, use the commands 'devel-su', enter the password, and then 'btrfs-balancer balance'.

Once that command finishes, you can check again what 'btrfs fi show' tells you, and the 'used' amount should be lower, hopefully by a lot, than before.

lol new problem a brand brand new one I can't delete files -_-'

Ok, "btrfs-balancer balance" done I got now 11G for 13Go and in used I got 8G for 10G... Still weird because I only have 300Mo of picture and few documentation... Hope you could help me all tomorrow. Thank a lot nthn my phone re-work better the before but still some things I don't understand.

@Xurb if you ssh into the device and then do:

 devel-su
 cd /home/nemo/.local/share/system/privileged/
 du --si -c .

what does it say? It's possible that a database corruption or something is causing data to duplicate.

You can also do the same under /var to see if you have a lot of cached packages which can be cleaned up.

@Xurb Thank you for running those commands! No, you don't need to post the ~1000 lines of log output of the third command for now. Your phone seems to be suffering from a combination of two issues:

1. something is filling up your device's storage
2. BTRFS, the file system used for the internal storage, is known to misbehave when filled up. Note that BTRFS needs 2 GB - 4 GB "spare" space for its operation - this is a trade-off that allows this file system to be really fast and at the same time prevents flash wear-down.

Now what?

You seem to have fixed issue 2. already by issuing a re-balance (i.e. free all of the "spare" space that's not really needed right now). Let's drill down on issue 1. @chris.adams already provided valuable advice; I'd like to offer an alternative, more interactive, use of the du command.

Before we start I'd like you to remove the sd-card from the phone (should you use one). This will ease the following steps; the device file system is mounted several times w/ several partitions - and we'd like to cover them all (i.e. we can't use du -x). However, we do not want to cover files stored on the sd-card.

OK, here we go. The following steps assume you already issued devel-su. First, go to the top level directory

cd /

Now, let's see how much space the top level directories are occupying. Issue

[root@Jolla /]# du --max-depth=1 -h . 2>/dev/null

and you will get something like (output abbreviated):

2.4G    ./home
88K     ./dev
...
7G     ./opt
76K     ./root
...
3.8G    ./data
...
0       ./config
14.7 G    .

Don't worry about the seemingly too large total size at the bottom - du gets confused by the same BTRFS partition being mounted several times across the device. We're not interested in totals but in space occupied by individual folders. Now, /home has your data/media files, /opt has aliendalvik (Android runtime) and all its data, which is partially re-mounted at /data.

Part II (Sorry, I ran out of characters for my comment :) ):

Let's drill down on /opt/ since (on my device) this seems unusually large (7G):

[root@Jolla /]# cd /opt
[root@Jolla opt]# du --max-depth=1  -h . 2>/dev/null

and we'll get

7G     ./alien
0       ./sdk
7G     .

Drill down further:

[root@Jolla opt]# cd /alien
[root@Jolla alien]# du --max-depth=1  -h . 2>/dev/null
116M    ./system
...
616M    ./usr
....
2.4G    ./home
....
3.8G    ./data
...
7G     .

Let's ignore ./home for the time being; it's the same mount-point as /home in the root directory, and we want to dig down on aliendalvik.

[root@Jolla alien]# cd data
[root@Jolla data]# du --max-depth=1  -h . 2>/dev/null
20K     ./property
....
462M    ./data
...
1.5G    ./app
0       ./ssh
...
0       ./ramdump
1.7G    ./media
0       ./keystore
...
3.8G    .
[root@Jolla data]# cd app
[root@Jolla app]# du --max-depth=1  -h . 2>/dev/null
0       ./incoming
0       ./packaged
1.5G    .

Heh, looks like I got 1.5 GB worth of Android apps installed on my Jolla.

You may use the same procedure to drill down on /home, or /opt/alien/data/media/, or whatever else looks suspicious. Be careful with deletion, though! Only remove stuff you put on the device yourself. Everything else please report in this answer here. People will help you to determine whether it's safe to remove.