[lxc-devel] [GIT] lxc branch, master, updated. 7df119eeaead89243486d33339fc039bde0eef04
Daniel Lezcano
git at users.sourceforge.net
Fri Jan 22 10:29:29 UTC 2010
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "lxc".
The branch, master has been updated
via 7df119eeaead89243486d33339fc039bde0eef04 (commit)
from bd288c265ac26dd4a63e7089858ea8f3d78447e6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 7df119eeaead89243486d33339fc039bde0eef04
Author: Daniel Lezcano <daniel.lezcano at free.fr>
Date: Fri Jan 22 11:29:10 2010 +0100
unmount failure is not fatal
There are several cases where the system can no longer access a mount
point or a mount point configuration makes the algorithm bogus.
For example, we mount something and then we chroot, the mount information
will give an unaccessible path and the container won't be able to start
because this mount point will be unaccessible. But if it's the case, then
we can just warn and continue running the container.
Another case is the path to a mount point is not accessible because there
is another mount point on top of it hiding the mount point. So the umount
will fail and the container won't start.
Easy to reproduce:
mkdir -p /tmp/dir1/dir2
mount -t tmpfs tmpfs /tmp/dir1/dir2
mount -t tmpfs tmpfs /tmp/dir1
So can we just ignore the error when unmounting and continue to the list again
and again until it shrinks.
At the end, we just display the list of the unmounted points.
Signed-off-by: Daniel Lezcano <dlezcano at fr.ibm.com>
-----------------------------------------------------------------------
Summary of changes:
src/lxc/conf.c | 13 ++++---------
1 files changed, 4 insertions(+), 9 deletions(-)
hooks/post-receive
--
lxc
More information about the lxc-devel
mailing list