Following condition:

• a mounted volume within the jboss.log.dir
• the mounted volume is an ext filesystem

as a consequence a lost+found directory is automatically created, owned by root.root, permissions are 700.

Now when you spin up a jboss instance, the logging directory is recursively scanned, due to the lost+found folder the logging subsystem throws the error https://github.com/wildfly/wildfly-core/blob/802d4dfcf58e24030d6c43ed2b0102a0c3620ae1/logging/src/main/java/org/jboss/as/logging/logging/LoggingLogger.java#L909

using the cli or mgmt console to read the log is then not possible.

it might be good to skip reading those files/directories and continue rather than throwing an error.

i tested it using the EAP7 (so wildfly-logging-2.1.2-final-redhat.jar), but also built the 3.0.6-SNAPSHOT and used this jar in the logging subsystem to check whether it may have been already fixed.