Revision history [back]

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?)

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?)