| commit | 73bd6807678ff80b46196b7113f0582f03e84637 | |
| author | Bruno Wolff III <bruno@wolff.to> | |
| Sat, 24 Jul 2010 13:26:56 +0000 (24 08:26 -0500) | ||
| committer | Bruno Wolff III <bruno@wolff.to> | |
| Sat, 24 Jul 2010 13:26:56 +0000 (24 08:26 -0500) | ||
| tree | 0742bc4068ceab3de20f8b05a908fb37a7476c7e | treesnapshot (tar.gz zip) |
| parent | 9eb92898e3ea9a34a0fa1b0e0bb30ab50c4133da | commitdiff |
Do lazy umounts to reduce the impact of umount issues.
By doing lazy umounts, if a umount can't be done (such as in the case of
the problem triggered by bug 617844), livecd-creator doesn't clean up after
itself. This ties up storage and loop devices.
This will mitigate problems where mounts are pinned by livecd-creator,
umounts are incorrectly done in the wrong order, or if the user is poking
around in the mount points while livecd-creator is running. It will not
fix a case where a umount is missed.
This should mitigate the symptoms of bug 509427, but not the root cause
(which is likely the problem reported in bug 617844.
By doing lazy umounts, if a umount can't be done (such as in the case of
the problem triggered by bug 617844), livecd-creator doesn't clean up after
itself. This ties up storage and loop devices.
This will mitigate problems where mounts are pinned by livecd-creator,
umounts are incorrectly done in the wrong order, or if the user is poking
around in the mount points while livecd-creator is running. It will not
fix a case where a umount is missed.
This should mitigate the symptoms of bug 509427, but not the root cause
(which is likely the problem reported in bug 617844.
| imgcreate/fs.py | diffblobblamehistory |