[Bug] Device unable to write anything

asked 2014-08-29 11:49:36 +0200

chemist gravatar image

updated 2015-02-03 13:33:04 +0200

To be clear, this is not an issue of 'no-space-left-on-device'

Last night I started up gallery, while navigating to it the device was already slow'ish. In the app then ambiences folder was missing. Later that night I was about looking after it and found as-launcher segfaulting, as-daemon not restarting because of it, gallery not starting with missing ambiences, trackerd not starting because of missing dbus engines for all of its crawlers and to make this even a better bug report - journald crashed too. So I have about the 4 lines of log where as-daemon tried to restart, some kernel messages and thats it. The I found some "no space left" messages and "no such file" messages too but all mounts in need of rw were rw.

Long story short, I think it was btrfs failing - and everything else is just collateral. 13 days of uptime. There were only native harbour apps running (I think it was Msg, Phone, Contacts, Settings, Clock), aliendalvik is installed and running in the bg. Any idea how to track this? I do not see anything in logs and logs are not getting written to device or even segfault (should not segfault on unavailable diskspace, should it?)

edit retag flag offensive close delete

Comments

Did you get this resolved? Can this be closed?

anandrkris ( 2015-02-03 12:04:34 +0200 )edit

as long as jolla does not say they have fixed it this is open, it is a bugreport after all... and by reading it carefully you recognize that it isn't / wasn't about full internal memory (failing kernel module probably).

chemist ( 2015-02-03 12:29:32 +0200 )edit

Ok...am just trying to clean up issues and wanted to know if Update 10 solved the issue :) If you believe Jolla would respond to this bug report, (considering number of votes, activity, etc), I wish you good luck and appreciate your optimism ;-) P.S. My own issues, i keep doing false edits to garner attention / votes.

anandrkris ( 2015-02-03 12:57:50 +0200 )edit

No need for attention on things tagged as bug, togethers with that tag get exported to their internal bugtracker iirc - the issue happened to me once and to many others, some had to recover the FS from recovery mode some just needed a reboot... this still happens, not as frequent as a year ago but there are still people popping into view having issues with locked FS or related

chemist ( 2015-02-03 13:23:58 +0200 )edit