[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[平凡]

** Changed in: linux-mako (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Chris Croome]

I might have hit this issue again, I have some files in a git repo on my
phone (mako running devel channel) and when I tried to do a `git commit
-a` just now I got:

error: corrupt loose object '4e1f9449b61f1b1eea1415de21c1c90db0a01f45'
fatal: loose object 4e1f9449b61f1b1eea1415de21c1c90db0a01f45 (stored in 
.git/objects/4e/1f9449b61f1b1eea1415de21c1c90db0a01f45) is corrupt

This is a 6.5K zlib compressed data file, when I moved it out of the way
and tried to do a `git commit -a` I was prompted to add things to the
repo that were already there, at this point I gave up and checked out a
fresh working copy of the repo.

It is of course possible that this corruption was caused by something
like a `git pull` failing half way though due to a network connection
issue, but I don't remember this happening.

-- 
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:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Pat McGowan]

marking resolved for purposes of this project

** Changed in: canonical-devices-system-image
   Status: New => Fix Released

-- 
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:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

setting the android-tools task to a realistic value, the remaining bit
is a corner case for normal users and is already shielded from doing any
damage by the fact that we do an fsck on every boot now.

** Changed in: android-tools (Ubuntu)
   Importance: Critical => Low

** Changed in: android-tools (Ubuntu RTM)
   Importance: Critical => Low

-- 
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:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[John McAleely]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
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:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

adbd can still not remount the filesystem readonly on "adb reboot" due
to the fact that we drop all privileges writing to /proc/sysrq-trigger
isnt possible and i havent found a way around this yet ... (this is a
corner case and potential fs corruption should be handled by the fsck on
next boot anyway, but it would be nice if adbd could work as expected
here, which is why the task is still open)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Jamie Strandboge]

There are multiple tasks still open for this bug. Can they be closed or
are there still things to do?

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

I think also we need to consider security of data is the ultimate goal.
Quite frankly, unpredictable things happen users can do all kinds of
things like yank out the battery and trip kernel panics.  Nobody has
formally verified that the kernel is perfect so there is always the
possibility of the device spontaneously rebooting or dieing before data
is written back.

-- 
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:
  [TOPBLOCKER] 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

Re: [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

On Tue, Dec 2, 2014 at 7:30 AM, Oliver Grawert  wrote:
> i think the "sudo reboot" and "low battery" case are the same, both
> should use init's shutdown/reboot commands ...

Right.

> i dont think a kernel panic is a "normal usecase", if we ship panicking
> devices i think we failed ... developers should simply be aware that
> panics can cause corruption, this is no different to desktop development

Well, it might not necessarily be a "normal" usecase, but we should
expect that to happen. It's better to better handle the crash than
expecting it to no crash at all, as we can't guarantee that with this
kernel.

And we should be thinking about normal users instead of developers :-)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

i think the "sudo reboot" and "low battery" case are the same, both
should use init's shutdown/reboot commands ...

i dont think a kernel panic is a "normal usecase", if we ship panicking
devices i think we failed ... developers should simply be aware that
panics can cause corruption, this is no different to desktop development

-- 
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:
  [TOPBLOCKER] 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

Re: [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

On Fri, Nov 28, 2014 at 3:29 PM, Oliver Grawert  wrote:
> it would be nice to have some upstart job that at least does an emergecy
> readonly mount on shutdown/reboot like we plan for adbd "adb reboot" by
> echoing "u" into /proc/sysrq-trigger ... that way we would at least be
> sure we do not unmount dirty and calling this command takes close to no
> time.

We could cover most of the possible causes for not unmounting it
properly, just wonder if we should still take the risk of moving back
to data=ordered.

Some use cases:
* Hard reboot (power + volume up): the userspace can probably be
notified by that, forcing the ro remount
* Adb: doing the emergency readonly mount as suggested by oliver
* $ sudo reboot: just making sure the halt process indeed umount the
partition successfully
* Low battery: forcing shutdown if batter lower than 3% (?)
* Kernel panic: can we force kernel to flush things into the disk when
we get a crash? This is important as well as it seems we can easily
make the kernel to crash still (specially when using bluetooth).

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

I don't thing we're seeing many writes to that partition, most of it's
probably data pages being flushed out in the background so it's not
going to bite too hard.  We do have tools to figure out how much is
being written if it needs some analysis.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

after running with the change for one week on my krillin i must say that
i dont really see any performance impact or any other bad behavior from
the change ...

it would be nice to have some upstart job that at least does an emergecy
readonly mount on shutdown/reboot like we plan for adbd "adb reboot" by
echoing "u" into /proc/sysrq-trigger ... that way we would at least be
sure we do not unmount dirty and calling this command takes close to no
time.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

So just to re-iterate:

1. I believe the file system is not being cleanly umounted.
2. data=journal saved us from disaster because it works so well.

My recommendation is to keep data=journal because a user can power off
the device (battery death, pulling out battery, random kernel reboot,
etc) and data=journal has conclusively shown it the only RELIABLE way to
ensure data and metadata are sane.

I really would like to warn against fixing this bug by doing the umount
and changing back to the faster but definitely less rugged data=ordered
option.  I think that would really be too risky IMHO.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

@Ricardo,

I'm added copious amounts of debug into the kernel and a shim on umount
too and I can't see /dev/mmcblk023 being unmounted anywhere.  Can you
inform me where to expect this umount is actioned on shutdown. I just
can't see it.

With full journaling on I'd expect this to cope with a non-umount as it
can replay the journaled data and metadata and so we don't get errors,
however, with the data=ordered option I could expect to see metadata
being perhaps sane where as the file data being not written back and
hence we see old data and possibly the reason for this corruption.

So, I'd really like to have some idea where the umount actually occurs.

The debug shows me:

boot --> initrd --> mount /dev/mmcpblk023 onto /tmpmnt

and then

[5.142499] mount: /root/userdata
[5.142591] do_mount: /tmpmnt -> /root/userdata []
[5.143811] do_mount return -> 0

But for the life of me, I can't see this being unmounted.  So that's my
concern, it may not be umounted and hence the root cause of the data
corruption.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

** Changed in: linux-mako (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Paolo Pisati (p-pisati)

** Changed in: linux-mako (Ubuntu RTM)
 Assignee: Colin Ian King (colin-king) => Paolo Pisati (p-pisati)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Colin Ian King]

We've been exercising the rtm images that include the latest workaround
now for a considerable amount of time repeating the test that originally
triggered the issue.

On mako, 2 devices running: 
 device #1, 329 iterations  - no corruption observed
 device #2, 251 iterations - no corruption observed

And also on another spare device using rtm image,
 device #3, 176 iterations, - no corruption observed

I can continue running these for another few days if need be, but I
think it is fairly conclusive that the data=journal change prevents the
apparmor metadata from ending up on the /var/lib/apparmor/profiles/*
files.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Łukasz Zemczak]

** Tags removed: lt-blocker

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package android - 20141117-0039-0ubuntu2

---
android (20141117-0039-0ubuntu2) vivid; urgency=medium

  * No change rebuild to pick up initramfs changes.
 -- Ricardo Salveti de AraujoTue, 18 Nov 
2014 22:21:39 -0200

** Changed in: android (Ubuntu RTM)
   Status: Fix Committed => Fix Released

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu RTM)
   Status: Fix Committed => Fix Released

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools-ubuntu-touch - 0.80

---
initramfs-tools-ubuntu-touch (0.80) vivid; urgency=medium

  * scripts/touch: mounting userdata with data=journal as a workaround
for bug LP: #1387214
 -- Ricardo Salveti de AraujoTue, 18 Nov 
2014 15:33:16 -0200

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

Colin King is investigating the issue on the filesystem level. He got an
easier way to reproduce the problem, and is currently investigating
possible patch sets from upstream.

** Changed in: linux-mako (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux-mako (Ubuntu RTM)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux-mako (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-mako (Ubuntu RTM)
   Status: New => Confirmed

** Changed in: linux-mako (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux-mako (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: android (Ubuntu RTM)
   Status: In Progress => Fix Committed

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu RTM)
   Status: In Progress => Fix Committed

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/initramfs-tools-ubuntu-touch

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

after researching the adbd part for two days it seems that adbd already
tries to call "echo u > /proc/sysrq-trigger" when adb reboot is issued
but at this point we already dropped privs to the phablet user ...

/proc/sysrq-trigger is owned by root:system and writable for both, the
only solution i see (beyond making /proc/sysrq-trigger owned by phablet
or its group which would rip a giant security hole) is to make adbd
start with "setguid system" and have it drop this group membership right
before any adb shell call (so that the logged in phablet user is not
member of system by default)

i'm trying to implement this but am constantly running into smaller
issues.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

I'm also unable to reproduce this issue when mounting /userdata (and
also it's bind mounts) with data=journal instead of data=ordered. This
might be a consequence of it being slower, not yet sure.

Decided to try that to see if I'd get any error when running e2fsck, but
still nothing. Only side effect is that I can't really reproduce the
problem.

Running for almost an hour now, will let it for a few more.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

It works fine if I move the writable paths under /, and it also works
fine after creating another image file (ext4) that gets stored under
/userdata, to be consumed by the writable paths (using bind-mounts and
everything).

But if I use bind mounts from /userdata/system-data directly, I can
easily get it to break. The same setup works fine when using / instead
(same bind-mounts and etc, but on a different dir path).

The only peculiarity with /userdata is that it's shared between both
containers. Ubuntu uses /userdata/system-data, /userdata/SWAP.img and
/userdata/user-data. Android uses /userdata/android-data.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

Used links instead of bind-mounts (for /userdata) and was still able to
reproduce the issue. So not necessarily related with bind-mounts itself.

** Also affects: linux-mako (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-mako (Ubuntu RTM)
   Importance: Undecided
   Status: New

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

Just migrated /opt/click.ubuntu.com under '/' (not bind-mounted) and was
able to run the same test case for more than 2 hours without any issue.

It fails again at the moment I move it back under /data (bind-mounted at
/opt/click.ubuntu.com), on the first run.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

So this is not a normal fs corruption issue. I was able to run the aa-
corruption test quite a few times with the extra e2fsck logic we added,
and was easily able to get the corrupted files on krillin, but which is
even more interesting is that the files are not actually corrupted for
e2fsck (not pointing out a single fs error, even though the files are
incorrect).

There's clearly a pattern with click paths under /opt/click.ubuntu.com
inside the corrupted files. /opt/click.ubuntu.com is also bind-mounted,
and it seems to be where it's mostly heavily used by the system.

So in the end it looks like with a quite bizarre error under rw
filesystems (ext4) that are bind-mounted. After migrating
/opt/click.ubuntu.com, /var/lib/apparmor and /var/cache/apparmor under
'/' (not bind-mounted), I was able to run the same aa-corruption test
case for a few without any issues (by default I can always get the issue
after the first test iteration).

Will let it running for a few more iterations and report back, but one
bad thing is that running e2fsck is really not going to help much here.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Launchpad Bug Tracker]

This bug was fixed in the package android - 20141117-0039-0ubuntu1

---
android (20141117-0039-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Checking partitions and filesystems when updating (LP: #1387214)
  * Dropping changing_series_to_vivid.patch and
fixing-adb-lock-inhibition.patch, both already upstream
 -- Ricardo Salveti de AraujoMon, 17 Nov 
2014 11:21:45 -0200

** Changed in: android (Ubuntu)
   Status: In Progress => Fix Released

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

** Changed in: android (Ubuntu RTM)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Changed in: android (Ubuntu RTM)
   Status: New => In Progress

** Changed in: android (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu RTM)
   Status: New => In Progress

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu RTM)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Daniel Holbach]

I think bug 1385464 was meant in the case of logrotate (comment 15).

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

adding an android-tools task, since "adb reboot" forces a hard reset
without unmounting the filesystems ... adding something along:

 root@ubuntu-phablet:~# echo u > /proc/sysrq-trigger
 root@ubuntu-phablet:~# touch /userdata/foo
 touch: cannot touch ‘/userdata/foo’: Read-only file system

to core/adbd/services.c in the reboot_service function (instead of the
vdc call) should help here

** Also affects: android-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: android-tools (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: android-tools (Ubuntu)
   Status: New => In Progress

** Changed in: android-tools (Ubuntu RTM)
   Status: New => In Progress

** Changed in: android-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: android-tools (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: android-tools (Ubuntu)
 Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: android-tools (Ubuntu RTM)
 Assignee: (unassigned) => Oliver Grawert (ogra)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

** Changed in: android (Ubuntu)
 Assignee: Ricardo Salveti (rsalveti) => Sergio Schvezov (sergiusens)

** Also affects: android (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools-ubuntu-touch (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
   Status: In Progress => Fix Released

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Ricardo Salveti]

** Changed in: android (Ubuntu)
   Status: Triaged => In Progress

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
   Status: Triaged => In Progress

** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Matthew Paul Thomas]

As far as I know, there is no design spec for the startup process, and
no designer assigned to it. In the meantime...

An automatic filesystem check being interactive makes less and less
sense over time. (As the sheer number of files on a device increases,
and the proportion of apps that are document-based decreases, you're
less and less likely to recognize a file by its pathname.) And it makes
*much* less sense on a phone, where you barely see the filesystem at
all, so the probability that you can make an informed decision about
fixing an individual file is pretty much zero.

So, in the "minimal fsck reveals an error" case, I suggest just
triggering a fsck -y. Don't make it interactive. Ideally, add text
something like "Repairing…" to the startup screen, or (during string
freeze) vary the visual design of the startup screen in *some* tasteful
way, to minimize the proportion of people who will think that the phone
has got stuck while starting up and try to fix it by holding down the
power button.

For the "immediately pull the latest full image and reboot for flashing"
case, you might find useful the design for a failed system update. You'd
need to change the text a bit.


-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Niklas Wenzel]

Doing a short grep, I also found that line in a lot of files, e.g. in
the following one: "~/.cache/upstart/logrotate.log"

The file started with 
"/opt/click.ubuntu.com/com.ubuntu.developer.filip-dobrocky.2048native/0.2", 
then continued with its normal content and in the middle of the file the 
following line could be found which clearly isn't there for logical reasons: 
"error: b/opt/click.ubuntu.com/com.ubuntu.developer.dpniel.dekko/0.2.9error: 
bad top line in state file /home/phablet/.cache/logrotate/status" All other 
lines looked like this one: "error: bad top line in state file 
/home/phablet/.cache/logrotate/status"

Having seen that error message, I checked the file it mentioned. Guess what its 
content is:
"/opt/click.ubuntu.com/com.ubuntu.developer.dpniel.dekko/0.2.9"

There actually seem to be a lot of corrupt files like these ones and
it's the second Ubuntu (Touch) installation which gives me those
results.

However, if you still think, it's a different bug, I will be happy to
hide all my comments here and file a new bug. ;)

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Niklas Wenzel]

@ogra: I don't think it's a dconf issue. Why would the same happen to
/cache/recovery/image-master.tar.xz.asc then?

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Oliver Grawert]

your dconf issues are caused by illegal use of dconf by an app (apps
should not be able to use dconf according to the security policy as i
understand it, to avoid exactly this), please file a fresh bug for this.

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Niklas Wenzel]

I've had this issue multiple times yet. For me it has always been like
that: The content of a file gets overriden and therefore the system
fails to do something.

Last time my system settings broke completely. When doing a "cat 
~/.config/dconf/user" I got:
"/opt/click.ubuntu.com/com.ubuntu.developer.webapps.webapp-gmail/1.0.25"
And after a reboot it now shows this:
"/opt/click.ubuntu.com/com.ubuntu.developer.filip-dobrocky.2048native/0.2"

Deleting "~/.config/dconf/user" did the trick for me.

Some other time system updates didn't work and doing a "cat 
/cache/recovery/image-master.tar.xz.asc" revealed it contained the following 
content:
"/opt/click.ubuntu.com/com.ubuntu.developer.majster-pl.utorch/1.6"

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Jamie Strandboge]

FYI, unconfirmed report via ubuntu-phone@: "Glad it isn't only me having
this issue -- I have come across this issue twice and it's been files in
/home/ getting corrupted."

** Description changed:

  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've
  already fixed several bugs in the apparmor and click-apparmor and made
  both more robust in the face of corruption and we've reduced the impact
  when there is a corrupted profile, but we've still not found the cause
  of the corruption. This corruption can still affect real-world devices:
  if a profile in /var/lib/apparmor/profiles is corrupted and the cache
  file is out of date, then the profile won't compile and that app/scope
  won't start.
  
  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.
  
  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.
  
  The security team and the kernel team have discussed this a lot and
- Colin is currently looking at this. This bug is just so it can be
+ Colin King is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:
  
  "I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:
  
  http://paste.ubuntu.com/8648109/
  
  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:
  
  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1
  
  In the paste you'll notice that in step 6 the profiles were successfully
  created by the installation of the packages, then verified, then copied
  aside, then apparmor_parser and aa-clickhook diverted, then rebooted,
  only to have the profiles in /var/lib/apparmor/profiles be different
  than what was copied aside. It would be nice to verify on your device as
  well (I reproduced several times here) and verify the reproducer
  algorithm. I think this suggests this is a kernel issue and not
  userspace.
  
  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...
  
  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...
  
  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"
  
  The kernel team has verified the above reproducer and symptoms.
  
  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Łukasz Zemczak]

** Tags added: lt-blocker lt-category-visible lt-prio-high

-- 
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:
  [TOPBLOCKER] 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

[Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Olli Ries]

** Summary changed:

- file corruption on touch images in rw portions of the filesystem
+ [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

-- 
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:
  [TOPBLOCKER] 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