Merge lp:~smoser/cloud-utils/trunk.lp1630274 into lp:cloud-utils
Proposed by
Scott Moser
Status: | Merged |
---|---|
Merged at revision: | 304 |
Proposed branch: | lp:~smoser/cloud-utils/trunk.lp1630274 |
Merge into: | lp:cloud-utils |
Diff against target: |
107 lines (+37/-34) 1 file modified
bin/mount-image-callback (+37/-34) |
To merge this branch: | bzr merge lp:~smoser/cloud-utils/trunk.lp1630274 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Registry Administrators | Pending | ||
Review via email: mp+307586@code.launchpad.net |
Commit message
mount-image-
The logic to determine if mount would work was flawed in it assumed
that both or neither of the following would succeed:
modprobe --quiet --use-blacklist fstype
mount -t fstype would succeed
That logic failed when modprobe could not load the module due to
being in a chroot or some other reason. The change here is to just
do try the mount. In order to avoid confusing output about trying
to mount overlayfs we first try mounting overlay. If that fails
and 'overlay' seems present in /proc/filesystems, then do not bother
trying to mount overlayfs.
To post a comment you must log in.