Occasionally pods fails to start and the message "SELinux: mount invalid. Same superblock, different security settings for (dev dm-N, type xfs) is seen in the logs

Solution Unverified - Updated -

Issue

  • Occasionally pods fails to start and the message "SELinux: mount invalid. Same superblock, different security settings for (dev dm-N, type xfs) is seen in the logs. From the logs
Apr 06 14:49:45 localhost kernel: SELinux: mount invalid.  Same superblock, different security settings for (dev dm-9, type xfs)
Apr 06 14:49:45 localhost docker[3946]: time="2016-04-06T14:49:45.272036708+02:00" level=error msg="Error unmounting device ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d: UnmountDevice: device not-mounted id ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d"
Apr 06 14:49:45 localhost docker[3946]: time="2016-04-06T14:49:45.272224632+02:00" level=error msg="HTTP Error" err="Cannot start container ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d: Error getting container ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d from driver devicemapper: Error mounting '/dev/mapper/docker-253:0-68067266-ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d' on '/var/lib/docker/devicemapper/mnt/ac58004eea05c383f6bd633f6822a182f17d073a0fe36bf4c87f522224a02c7d': invalid argument" statusCode=500

Environment

  • Red Hat Enterprise Linux 7.2
  • Red Hat Openshift Enterprise 3.1.1
  • Kernel: 3.10.0-327.10.1.el7.x86_64
  • lvm2: 2.02.130-5.el7_2.1.x86_64
  • docker: 1.8.2-10.el7.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content