-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker hosts would better exclude the file systems under control by docker #1749
Comments
We still see messages like:
but which are incorrect. The savelayout does contain:
The wrong assumption happens in script
The Log should only happen when we find a hit on docker_root_dir. |
@pcahyna I'm sorry I'm under the sea since a few months. Could you have a look at what is reported here? |
@rmetrich Under the sea? What do you mean (just for my knowledge if I can still bother you or not)? |
Well I'm in a deep dive under the water :-) and there is lots of water |
Is it related to #1989 (fixed by #2021)? A fix for that one was released with RHEL 7.8 two weeks ago. @yontalcar can you please have a look? |
Code is fixed in master branch. |
…rear#1749 rear#2365 Signed-off-by: Gratien D'haese <gratien.dhaese@gmail.com>
@pcahyna @yontalcar Found a minor bug in the script |
I think this isue is fixed by |
The docker device /dev/xvdb is not mounted by the system, but is under control by the docker application. Therefore all thin-pool mounted file systems should not be included in
savelayout.conf
file:The text was updated successfully, but these errors were encountered: