I'd try to stop docker gracefully (service docker stop), do a health check of your devicemapper (thin_check --clear-needs-check-flag /var/lib/docker/devicemapper/devicemapper/metadata), and presuming that doesn't return any errors, retry starting the container.
Failing that, after referencing a couple of similarissues, it seems like the issue is likely with the docker devicemapper driver, but can be resolved by switching to their aufs driver. Unfortunately, the suggested action to do so is to wipe out your /var/lib/docker directory, install aufs (sudo apt-get install linux-image-extra-$(uname -r)), and re-install docker.
Aaron_Peterson
1 Rookie
•
26 Posts
0
July 6th, 2016 16:00
fdisk may showing you devices which are physically connected but unmounted; do they show up in df -h ? If not, you may want to try mounting them via:
mount /dev/sdb1 /ecs/uuid-1 -o noatime,seclabel,attr2,inode64,noquota
and so on.
KTice1
1 Rookie
•
8 Posts
0
July 7th, 2016 06:00
Aaron - Thanks for the reply. The disks are mounted:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/centos-root 37G 14G 24G 37% /
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 8.5M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/sdc1 100G 91G 10G 91% /ecs/uuid-2
/dev/sdb1 100G 91G 10G 91% /ecs/uuid-1
/dev/sdd1 100G 91G 10G 91% /ecs/uuid-3
/dev/sde1 100G 91G 10G 91% /ecs/uuid-4
/dev/sda1 497M 164M 334M 33% /boot
tmpfs 3.2G 0 3.2G 0% /run/user/0
I have them in fstab:
/dev/sdb1 /ecs/uuid-1 xfs rw,noatime,seclabel,attr2,inode64,noquota 0 0
/dev/sdc1 /ecs/uuid-2 xfs rw,noatime,seclabel,attr2,inode64,noquota 0 0
/dev/sdd1 /ecs/uuid-3 xfs rw,noatime,seclabel,attr2,inode64,noquota 0 0
/dev/sde1 /ecs/uuid-4 xfs rw,noatime,seclabel,attr2,inode64,noquota 0 0
Aaron_Peterson
1 Rookie
•
26 Posts
0
July 7th, 2016 09:00
KTice,
I'd try to stop docker gracefully (service docker stop), do a health check of your devicemapper (thin_check --clear-needs-check-flag /var/lib/docker/devicemapper/devicemapper/metadata), and presuming that doesn't return any errors, retry starting the container.
Failing that, after referencing a couple of similar issues, it seems like the issue is likely with the docker devicemapper driver, but can be resolved by switching to their aufs driver. Unfortunately, the suggested action to do so is to wipe out your /var/lib/docker directory, install aufs (
sudo apt-get install linux-image-extra-$(uname -r)), and re-install docker.