Should unmount real filesystems once all loop-mounted filesystems are unmounted
Bug #1229409 reported by
Loïc Minier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lxc-android-config (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
I'm sometimes getting what appears to be filesystem corruption when I mount -o remount,rw + apt-get install stuff + immediately reboot. I suspect this could similary affect user data in /home.
I'm rebooting cleanly with shutdown -r now or reboot, so either software drivers / hardware is doing the sync wrong, or we're not unmounting the loop-mounted fses correctly. Since I don't think we have any code to unmount the loop-mounted filesystems I'm assuming the latter and filing this here where we could fix it.
It would also be good to ensure we have "sync"s in place after applying a system-update.
Cheers,
| Changed in lxc-android-config (Ubuntu): | |
| assignee: | nobody → Stéphane Graber (stgraber) |
Revision history for this message
| Stéphane Graber (stgraber) wrote | #1 |
| Changed in lxc-android-config (Ubuntu): | |
| assignee: | Stéphane Graber (stgraber) → nobody |
To post a comment you must log in.
System updates are applied from the recovery environment and certainly does call sync at that point.
As for the rest of the system, I don't think we should try to hack around this. Our standard shutdown sequence is supposed to be clever enough to unmount everything and call sync before rebooting. If we somehow bypass that on touch, that's the problem, if we don't, then we have a larger bug which affects Ubuntu at large and should be fixed.
In any case, I'd be opposed to doing any change to lxc-android-config for that specific problem (since it's the wrong place).