Jolla Phone data lost because disk is full

asked 2015-06-10 12:44:14 +0300

updated 2015-06-10 15:13:25 +0300

jiit gravatar image

My phone just stopped working over night, and didn't even wake me up as it was supposed to in the morning. running the recovery mode and going for the btrfs commands gives me this:

/ # btrfs fi show Label: 'sailfish' uuid: 86180ca0-d351-4551-b262-22b49e1adf47 Total devices 1 FS bytes used 11.84GiB devid 1 size 13.75GiB used 13.74GiB path /dev/mmcblk0p28

Btrfs v3.16 / #

So the main partition is obviously full. Any btrfs command attempting to balance and free some space fails miserably with ioctl errors:

/ # btrfs balance start -dusage=1 / ERROR: error during balancing '/' - Inappropriate ioctl for device There may be more info in syslog - try dmesg | tail

I am also UNABLE TO MOUNT IT AND RECOVER ANY OF MY DATA! This is extremely frustrating, and as a Jolla fan, and as a person who used to work personally with the main people that built this company, I can only say that I am really disappointed that in 2 years of development, basic features are still not present. I am referring to features such as enabling the camera to save on SD card instead of the device memory.

And now this. How is it possible that a device dies completely and all the data is irrecoverable when the disk is full?

Really guys, I have bought 2 Jollas already and have a couple of friends who bought them because I suggested them the device, but if my data is lost forever because of this idiotic software bug, then this is the last one I will ever use.

It is incredibly frustrating, and instead of playing 250 EUR for something that dies every now and then for reasons like misalignment of planets, I would rather spend double or triple for something else that just works and I can at least rely on to wake me up in the morning...

edit retag flag offensive close delete



Sadly I too am also coming around to this way of thinking.

strongm ( 2015-06-10 12:47:54 +0300 )edit

What is the error when attempting to mount /dev/mmcblk0p28 /mnt? Or how did you attempt to mount it? From what you tell something else is wrong.

For your other complaints it is bad seamanship to rely solely on electronic systems especially if there is only one device for each task, close to all phones I had did fail to wake me up at some point, and when I say phones I mean down to my first device - that is why I have an alarm-clock (5€) waking me 5 minutes after my phone, yeah I am kind of oldschool, I have an analogue wristwatch too!

Yes it is frustrating that so many things are still WIP with Jolla, and I love to have all features I have in mind right now but well this is no polly pocket island.

chemist ( 2015-06-10 12:56:47 +0300 )edit

@chemist I have attempted to mount mmcblk0p28 and the command just hangs:

/ # mount /dev/mmcblk0p28 /mnt

And then nothing. And the only way to recover to the console is restart the telnet session.

Moreover, if I run "btrfs fi df /" I get this:

/ # btrfs fi df / ERROR: couldn't get space info - Inappropriate ioctl for device ERROR: get_df failed Inappropriate ioctl for device / #

lhorga ( 2015-06-10 13:01:12 +0300 )edit

When in recovery shell you are running from within the recovery image, that works a tad different than you'd expect. try mounting it with mount -o nospace_cache,clear_cache,enospc_debug,nodatacow /dev/mmcblk0p28 /mnt (this may take a while, be patient! probably normal mount would work too if you'd just wait long enough) then delete one or two bigger files, and start balancing on /mnt try -dusage=5 (can do that several times with increasing number) before attempting to just balance all of it

chemist ( 2015-06-10 13:13:19 +0300 )edit

@chemist Thanks, I started the mount command, letting it run for a while see if it finishes. Will get back with info. Thanks again for the help!

lhorga ( 2015-06-10 13:31:18 +0300 )edit