Mount points created with the mkmountpoint command become invalid after the umount-all command is used. These two commands are considered incompatible. This is now documented in the guestfish man page. Customers should note that it is possible to safely unmount devices mounted with mkmountpoint by using the umount command.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
I changed the summary to be consistent with bug 599503.
We're not going to fix this, but we will document the problems
with mixing mkmountpoint and umount-all, for RHEL 6.1.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Fixed by the rebase.
the output of `guestfish help mkmountpoint` contains:
"mkmountpoint" is not compatible with "umount_all". You may get
unexpected errors if you try to mix these calls. It is safest to
manually unmount filesystems and remove mountpoints after use.
"umount_all" unmounts filesystems by sorting the paths longest first, so
for this to work for manual mountpoints, you must ensure that the
innermost mountpoints have the longest pathnames, as in the example code
so this could be VERIFIED.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.