[MESOS-3349] Removing mount point fails with EBUSY in LinuxFilesystemIsolator.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.27.0
• Component/s: test
• Labels: flaky-test

Environment

Ubuntu 14.04, CentOS 5

• Epic Link: filesystem isolation
• Sprint: Twitter Mesos Q3 Sprint 5
• Story Points: 5
• Assignee: Jie Yu
• Reporter: Benjamin Mahler
• Shepherd: Yan Xu
• Created: 01/Sep/15 02:26
• Updated: 16/Jan/16 08:46
• Resolved: 14/Sep/15 23:39

Description

When running the tests as root, we found PersistentVolumeTest.AccessPersistentVolume fails consistently on some platforms.

[ RUN      ] PersistentVolumeTest.AccessPersistentVolume
I0901 02:17:26.435140 39432 exec.cpp:133] Version: 0.25.0
I0901 02:17:26.442129 39461 exec.cpp:207] Executor registered on slave 20150901-021726-1828659978-52102-32604-S0
Registered executor on hostname
Starting task d8ff1f00-e720-4a61-b440-e111009dfdc3
sh -c 'echo abc > path1/file'
Forked command at 39484
Command exited with status 0 (pid: 39484)
../../src/tests/persistent_volume_tests.cpp:579: Failure
Value of: os::exists(path::join(directory, "path1"))
  Actual: true
Expected: false
[  FAILED  ] PersistentVolumeTest.AccessPersistentVolume (777 ms)

Turns out that the 'rmdir' after the 'umount' fails with EBUSY because there's still some references to the mount.

FYI jieyu mcypark

Issue Links

• is related to: MESOS-3430 LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithoutRootFilesystem fails on CentOS 7.1