Bug 1291852

Summary:	docker info Backing Filesystem for devicemapper is an empty string
Product:	Red Hat Enterprise Linux 7	Reporter:	Antonio Murdaca <amurdaca>
Component:	docker-latest	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	ajia, amurdaca, lsm5
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-12 14:54:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1303656

Description Antonio Murdaca 2015-12-15 17:45:56 UTC

Description of problem:

After the very first run of the docker daemon with devicemapper as the storage backend, docker info will show an empty string for Backing Filesystem 


Version-Release number of selected component (if applicable):

docker-1.10.0-12.gitc3726aa.fc24.x86_64


How reproducible:

Always


Steps to Reproduce:
1. systemctl stop docker
2. rm -rf /var/lib/docker
3. systemctl start docker
4. docker info (shows "xfs")
5. systemctl restart docker
6. docker info (shows "")


Actual results:

docker info shows an empty string for Backing Filesystem after the very first run


Expected results:

docker info always shows Backing Filesystem


Additional info:

None

Comment 1 Antonio Murdaca 2015-12-15 17:46:47 UTC

fixed in docker-1.10

Comment 4 Alex Jia 2016-02-03 08:44:05 UTC

(In reply to Antonio Murdaca from comment #0)

> 6. docker info (shows "")
> 

Antonio, I gave a try on docker-1.9.1-15.el7.x86_64, there is no any value/string is showed in 'Backing Filesystem:' after step 6, just a confirmation, it should be an expected result, right?

# docker info|grep "Backing Filesystem"
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
 Backing Filesystem:

Comment 5 Antonio Murdaca 2016-02-03 10:01:10 UTC

(In reply to Alex Jia from comment #4)
> (In reply to Antonio Murdaca from comment #0)
> 
> > 6. docker info (shows "")
> > 
> 
> Antonio, I gave a try on docker-1.9.1-15.el7.x86_64, there is no any
> value/string is showed in 'Backing Filesystem:' after step 6, just a
> confirmation, it should be an expected result, right?
> 
> # docker info|grep "Backing Filesystem"
> WARNING: bridge-nf-call-iptables is disabled
> WARNING: bridge-nf-call-ip6tables is disabled
>  Backing Filesystem:

This is fxed in docker-1.10 not 1.9

Comment 8 Alex Jia 2016-04-29 10:43:39 UTC

The Backing Filesystem still is xfs after step 5 in Description w/ docker-latest 1.10.3-10 and 1.10.3-19

Ater step 5 in Description.

# docker-latest info|grep xfs
 WARNING: Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
 Backing Filesystem: xfs

# docker info|grep xfs
 Backing Filesystem: xfs
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Comment 10 errata-xmlrpc 2016-05-12 14:54:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1057.html