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

overlayfs: upperdir is in-use by another mount when docker data dir mounted from another disk #2279

Closed
matti opened this Issue Dec 7, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@matti

matti commented Dec 7, 2017

Bug

dmesg has warnings similar to moby/moby#34672 when /var/lib/docker mounted from extfs4 disk

[  447.193907] overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[  447.196018] overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[  454.388022] overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.
[  454.390110] overlayfs: workdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.

comment moby/moby#34672 (comment) mentions this

$ zgrep OVERLAY_FS_INDEX /proc/config.gz
# CONFIG_OVERLAY_FS_INDEX is not set

environment

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1576.4.0
VERSION_ID=1576.4.0
BUILD_ID=2017-12-06-0449
PRETTY_NAME="Container Linux by CoreOS 1576.4.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Reproduction Steps

# before docker
mkdir -p /var/lib/docker
mount /dev/sdb1 /var/lib/docker
# start docker
@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Dec 7, 2017

Member

Hi @matti, those warnings are indeed a result of moby/moby#34672, but they're harmless and can be ignored. (See moby/moby#34672 (comment).)

Member

bgilbert commented Dec 7, 2017

Hi @matti, those warnings are indeed a result of moby/moby#34672, but they're harmless and can be ignored. (See moby/moby#34672 (comment).)

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert May 11, 2018

Member

These warnings should be gone in the latest stable. Closing.

Member

bgilbert commented May 11, 2018

These warnings should be gone in the latest stable. Closing.

@bgilbert bgilbert closed this May 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment