]
Brian Stansberry commented on WFCORE-2301:
------------------------------------------
Hi [~bjoernstuetztss]. It looks like the stack trace in the description is missing some
items, as our code doesn't call LinuxFileStore.findMountEntry. Do you have the
missing bits, and also what WildFly release they come from?
The Stack Overflow entry has that and it looks like the problem is a call to
java.nio.files.File.getFileStore. But I'm not sure if that's the only thing that
triggers this. But if that's the only trigger point then it may be easier to work
around it.
Mount point not found exception raised by
createTempFileWithAttributes on overlayfs [JDK-8165852]
-------------------------------------------------------------------------------------------------
Key: WFCORE-2301
URL:
https://issues.jboss.org/browse/WFCORE-2301
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Environment: WildFly on Docker with overlayfs or overlayfs2 as storage driver
# docker info | grep -i storage
aufs: works (e.g., boot2docker, legacy minikube)
overlay (e.g., CoreOS, current minikube): problem
devicemapper (e.g., CentOS): works
overlay2 (e.g., Docker for Mac): problem
Reporter: Bjoern Stuetz
Assignee: Brian Stansberry
Mount point not found exception raised by createTempFileWithAttributes on overlayfs
[JDK-8165852], i.e.,
/opt/jboss/bin/jboss-cli.sh --file=/opt/jboss/jboss-config.cli
inside a Docker container running on overlayfs as storage driver
causes:
{code:java}
java.io.IOException: Mount point not foundImage
at sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91)
at
org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:117)
at
org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:104)
{code}
due to OpenJDK bug/overlayfs bug.
We acknowledge that this is in fact an OpenJDK AND/OR overlayfs bug. However everything
seems to run fine in WildFly except once the backup of the config is triggered, for
example by using the cli. Hence WildFly is of limited functionality when the more and more
popular overlayfs storage driver is used, and the WildFly team might be interested in
providing a workaround on their side since there is no indication the OpenJDK bug will be
promptly fixed. We are happy to help in any way, we are still trying to find a workaround
on the Java or WildFly side; but we might need insights on why findMountEntry is invoked.
Java Bug Overview:
https://bugs.openjdk.java.net/browse/JDK-8165852
http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/8u...
Wildfly Stack Overflow issue, not solved:
https://stackoverflow.com/questions/41022393/mount-point-not-found
Background Info:
http://mail.openjdk.java.net/pipermail/nio-dev/2016-October/003915.html
A) chroot environment [1]
B) Docker container with overlay and overlay2 storage drivers [2]
C) btrfs file system with an unmounted sub-volume [2]
[1]
https://bugs.openjdk.java.net/browse/JDK-8165323 - cannot get FileStore in chroot
environment
[2]
https://bugs.openjdk.java.net/browse/JDK-8165852 - cannot get FileStore for a file in
overlayfs in Docker
Docker file system/storage driver:
https://docs.docker.com/engine/userguide/storagedriver/selectadriver/)
Yum yum-plugin-ovl, similar problem:
https://github.com/CentOS/sig-cloud-instance-images/issues/15