[
https://issues.apache.org/jira/browse/MESOS-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599528#comment-16599528
]
Jie Yu commented on MESOS-9196:
-------------------------------
Posted a chain starting here:
https://reviews.apache.org/r/68594/
> Removing rootfs mounts may fail with EBUSY.
> -------------------------------------------
>
> Key: MESOS-9196
> URL: https://issues.apache.org/jira/browse/MESOS-9196
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Reporter: Gilbert Song
> Assignee: Gilbert Song
> Priority: Blocker
> Labels: containerizer
>
> We observed in production environment that this
> {code}
> Failed to destroy the provisioned rootfs when destroying container: Collect
> failed: Failed to destroy overlay-mounted rootfs
> '/var/lib/mesos/slave/provisioner/containers/6332cf3d-9897-475b-88b3-40e983a2a531/containers/e8f36ad7-c9ae-40da-9d14-431e98174735/backends/overlay/rootfses/d601ef1b-11b9-445a-b607-7c6366cd21ec':
> Failed to unmount
> '/var/lib/mesos/slave/provisioner/containers/6332cf3d-9897-475b-88b3-40e983a2a531/containers/e8f36ad7-c9ae-40da-9d14-431e98174735/backends/overlay/rootfses/d601ef1b-11b9-445a-b607-7c6366cd21ec':
> Device or resource busy
> {code}
> Consider fixing the issue by using detach unmount when unmounting container
> rootfs. See MESOS-3349 for details.
> The root cause on why "Device or resource busy" is received when doing rootfs
> unmount is still unknown.
> _UPDATE_: The production environment has a cronjob that scan filesystems to
> build index (updatedb for mlocate). This can explain the EBUSY we receive
> when doing `unmount`.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
