Huge thanks to Colin (and apw) for this find.
I want to state that this is a very real problem and not theoretical.
I've seen it many times, it is triggerable with enough reboots, and it
has been seen on krillin by non-developers (ie, just through normal
reboots and system-image updates). stgraber outlined the start of a fix
here: http://paste.ubuntu.com/8851794/
IMO, we must solve #2 from Colin's comment #9 (perform an fsck using
something like stgraber's approach) before the golden image. If we have
that, we can solve #1 in OTA (though in an ideal world that would be
fixed prior to golden image since we don't want people dropping into
recovery mode if we can at all help it).
** Changed in: system-image (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
Importance: Undecided => Critical
** Changed in: android (Ubuntu)
Importance: Undecided => Critical
** Changed in: system-image (Ubuntu)
Status: Confirmed => Triaged
** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
Status: New => Triaged
** Changed in: android (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387214
Title:
file corruption on touch images in rw portions of the filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
