On 05/11 18:06, Nir Soffer wrote: > On Wed, May 11, 2016 at 4:20 PM, David Caro <[email protected]> wrote: > > On 05/11 15:38, Nir Soffer wrote: > >> This ioprocess build failed with ci related issue: > >> > >> http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-el7-x86_64/1/ > >> > >> 12:18:34 + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) > >> 12:18:34 ++ mount > >> 12:18:34 ++ awk '{print $3}' > >> 12:18:34 ++ grep > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b > >> 12:18:34 + [[ -n > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc > >> ]] > >> 12:18:34 + echo 'Found mounted dirs inside the chroot > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b.' > >> 'Trying to umount.' > >> 12:18:34 Found mounted dirs inside the chroot > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b. > >> Trying to umount. > >> 12:18:34 + for mount in '"${mounts[@]}"' > >> 12:18:34 + sudo umount > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc > >> 12:18:34 umount: > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc: > >> target is busy. > >> 12:18:34 (In some cases useful info about processes that use > >> 12:18:34 the device is found by lsof(8) or fuser(1)) > >> 12:18:34 + echo 'ERROR: Failed to umount > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc.' > >> 12:18:34 ERROR: Failed to umount > >> /var/lib/mock/fedora-22-x86_64-d496d3daa673001f46dbbd9addf9ba1b/root/proc. > >> > >> We should check why the mountpoint is busy, but a quick fix may be using > >> the --lazy option: > >> > >> umount --lazy /mountpoint > > > > That's only available on newer kernels, for the el7 slaves it's not yet > > there > > Are you sure? Vdsm is using this for years.
You are right, from the manual:
-l, --lazy
Lazy unmount. Detach the filesystem from the filesystem
hierarchy now, and cleanup all references to the filesystem as soon as it is
not busy anymore. (Requires kernel 2.4.11 or later.)
I just confused 2.4.11 for 4.2.11... should be ok to use it
>
> Nir
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: [email protected]
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
signature.asc
Description: PGP signature
_______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
