You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kevin Klues (JIRA)" <ji...@apache.org> on 2016/08/02 18:52:20 UTC
[jira] [Created] (MESOS-5969) Linux 'MountTable' not sorted as
expected
Kevin Klues created MESOS-5969:
----------------------------------
Summary: Linux 'MountTable' not sorted as expected
Key: MESOS-5969
URL: https://issues.apache.org/jira/browse/MESOS-5969
Project: Mesos
Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Kevin Klues
Assignee: Kevin Klues
Fix For: 1.0.1
Many places in the codebase assume that the mount table is sorted according to the order: {{parent mount point < child mount point}}.
However, in some cases this may not be true if (for example), a parent mount point (say {{/}}) is remounted to add some extra flags to it. When this happens, the remounted file system will appear in the mount table at the point where it was remounted.
We actually encountered this problem in the wild for the case of {{/}} being remounted after {{/run}} was mounted -- causing problems in the {{NvidiaVolume}} which assumes the {{parent < child}} ordering.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)