Docker Community Forums

Share and learn in the Docker community.

Corrupt docker container, cannot masternode


(Dockershmocker2017) #1

I have overloaded my server 32GB RAM, HDD 2TB, i7 4770 with 190 docker containers all running cryptocoin masternodes.
after a day CPU went to 100% and stuck there, dockers became almost unresponsive, ssh as well…
not a crash but limbo

and now masternodes randomly die out
there is a corruption of filesystem inside dockers or something like this

how to fix file system inside dockers?
sudo fsck -f /
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: Is a directory while trying to open /

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

how to check that containers are ok?