Logstash docker container failed to start found this error in /var/log/messages mounted filesystem with ordered data mode. Opts: (null)

Hi Team,

I am using Docker version 17.05.0-ce, build 89658be
I have logstash container hosted which is scheduled to be stop and start every day.

Which is getting failed to start in the first attempt i have checked /var/log/messages i have found below error .

Mar 13 02:10:17 xyz02310048 kernel: [3612220.426658] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)

in dmseg i could see below errors

[3035738.189459] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3122140.781725] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3122204.444231] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3208542.442046] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3294937.864876] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3381340.920940] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3467733.422973] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3554130.208919] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3554192.374377] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3640532.794466] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3726933.664886] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3813330.426658] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3813393.623575] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3899728.058799] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3899796.604246] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[3986132.558920] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[4072537.173779] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[4072599.890596] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[4158925.502896] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
[4158994.460285] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)

[root@xyz02310048 ~]# docker info
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 28
Server Version: 17.05.0-ce
Storage Driver: devicemapper
Pool Name: docker-249:2-4718596-pool
Pool Blocksize: 65.54kB
Base Device Size: 10.74GB
Backing Filesystem: ext4
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 3.678GB
Data Space Total: 107.4GB
Data Space Available: 38.27GB
Metadata Space Used: 5.116MB
Metadata Space Total: 2.147GB
Metadata Space Available: 2.142GB
Thin Pool Minimum Free Space: 10.74GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /data/docker/devicemapper/devicemapper/data
Metadata loop file: /data/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.117-RHEL6 (2016-08-15)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea68997b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d602452adf14862e4f2228
init version: 949e6fa
Kernel Version: 4.1.12-124.15.1.el6uek.x86_64
Operating System: Oracle Linux Server 6.8
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.795GiB
Name: xyz02310048
ID: EZ7X:BPLS:BAJQ:TB3G:PHS8:K36D:NBNR:GTAC:PW3E:GIEN:UBGG:2POV
Docker Root Dir: /data/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: proxy internal
Https Proxy: proxy internal
No Proxy: 127.0.0.1,localhost,0.0.0.0,11.03.05.10
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/9
Live Restore Enabled: false

WARNING: devicemapper: usage of loopback devices is strongly discouraged for production use.
Use --storage-opt dm.thinpooldev to specify a custom block storage device.

Mar 13 02:10:16 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash
Mar 13 02:10:17 xyz02310048 kernel: [3612220.426658] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
Mar 13 02:11:00 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash
Mar 13 02:11:10 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash
Mar 13 02:11:19 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash
Mar 13 02:11:20 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash
Mar 13 02:11:20 xyz02310048 kernel: [3612220.623575] EXT4-fs (dm-10): mounted filesystem with ordered data mode. Opts: (null)
Mar 13 02:12:02 xyz02310048 sudo: rundeck : TTY=unknown ; PWD=/home/rundeck ; USER=root ; COMMAND=/bin/bash

dmsetup ls --tree

rootvg-scheduler (249:4)
└─ (8:2)
rootvg-osmf (249:3)
└─ (8:2)
docker-249:2-4718596-2182c82341443b5b99ead031f7ae3498e44fec39548254ed61ad1c577b24ebc3 (249:10)
└─docker-249:2-4718596-pool (249:9)
├─ (7:0)
└─ (7:1)
rootvg-usr (249:6)
└─ (8:2)
rootvg-var (249:7)
└─ (8:2)
swapvg-swap (249:1)
└─ (8:16)
rootvg-home (249:8)
└─ (8:2)
rootvg-opt (249:5)
└─ (8:2)
rootvg-root (249:0)
└─ (8:2)
appvg-applv1 (249:2)
└─ (8:33)

Please do let me know is this is a bug or do i need to do some thing from my end to fix this issue ?

Any help would be appreciated…!!

Regards,
Krishna