We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-05-02 11:02:44 +0200 |
It seems like there are either something wrong with the btrfs tools or the jolla kernel has a quite broken implementation of btrfs.
When you do a: btrfs balance start -dusage=xx /
the higher xx is it seems the more likely the process will hang, I did a balance with 90 (this is less than the 96 which the jolla balance uses), the process been running for 12 hours, still on the last block according to btrfs status. Running a "btrfs balance cancel /" do not stop the balance process and the cancel process hangs too. The only way to recover is to reboot the phone and start balance again first with metadata and then disk.
Suggestion, upgrade kernel to 3.18 or later, as there will be a balance functionality built in and you shouldn't need to run the balance manually. Also upgrade to btrfs-progs 3.19.1 could be of benefit. Sure this will not fix the issue that the disk is too small for btrfs, but should make it less likely that you will run out of "disk".
2 | No.2 Revision |
It seems like there are either something wrong with the btrfs tools or the jolla kernel has a quite broken implementation of btrfs.
When you do a: btrfs balance start -dusage=xx /
the higher xx is it seems the more likely the process will hang, I did a balance with 90 (this is less than the 96 which the jolla balance uses), the process been running for 12 hours, still on the last block according to btrfs status. Running a "btrfs balance cancel /" do not stop the balance process and the cancel process hangs too. The only way to recover is to reboot the phone and start balance again first with metadata and then disk.
Suggestion, upgrade kernel to 3.18 or later, as there will be a balance functionality built in and you shouldn't need to run the balance manually. Also upgrade to btrfs-progs 3.19.1 could be of benefit. Sure this will not fix the issue that the disk is too small for btrfs, but should make it less likely that you will run out of "disk".
Currently: Kernel 3.4.98.20150206.1.1, Btrfs-progs v3.16 (Sailfish 1.1.4.29)
3 | retagged |
It seems like there are either something wrong with the btrfs tools or the jolla kernel has a quite broken implementation of btrfs.
When you do a: btrfs balance start -dusage=xx /
the higher xx is it seems the more likely the process will hang, I did a balance with 90 (this is less than the 96 which the jolla balance uses), the process been running for 12 hours, still on the last block according to btrfs status. Running a "btrfs balance cancel /" do not stop the balance process and the cancel process hangs too. The only way to recover is to reboot the phone and start balance again first with metadata and then disk.
Suggestion, upgrade kernel to 3.18 or later, as there will be a balance functionality built in and you shouldn't need to run the balance manually. Also upgrade to btrfs-progs 3.19.1 could be of benefit. Sure this will not fix the issue that the disk is too small for btrfs, but should make it less likely that you will run out of "disk".
Currently: Kernel 3.4.98.20150206.1.1, Btrfs-progs v3.16 (Sailfish 1.1.4.29)
4 | No.4 Revision |
It seems like there are either something wrong with the btrfs tools or the jolla kernel has a quite broken implementation of btrfs.
When you do a: btrfs balance start -dusage=xx /
the higher xx is it seems the more likely the process will hang, I did a balance with 90 (this is less than the 96 which the jolla balance uses), the process been running for 12 hours, still on the last block according to btrfs status. Running a "btrfs balance cancel /" do not stop the balance process and the cancel process hangs too. The only way to recover is to reboot the phone and start balance again first with metadata and then disk.
Suggestion, upgrade kernel to 3.18 or later, as there will be a balance functionality built in and you shouldn't need to run the balance manually. Also upgrade to btrfs-progs 3.19.1 could be of benefit. Sure this will not fix the issue that the disk is too small for btrfs, but should make it less likely that you will run out of "disk".
Update: Noticed also that battery consumption may be connected to how "full" the btrfs is, when down around 9.9GB then battery holds a whole weekend with 30+% left, when up on 11.9GB then battery do not last more than max 16 hours.
Currently: Kernel 3.4.98.20150206.1.1, Btrfs-progs v3.16 (Sailfish 1.1.4.29)