Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

devmapper: show device and loop file , if used #10003

Merged
merged 1 commit into from
Jan 13, 2015

Conversation

vbatts
Copy link
Contributor

@vbatts vbatts commented Jan 9, 2015

Presenly the "Data file:" shows either the loopback file or the block device.
With this, the "Data file:" will always show the device, and if it is a
loopback, then there will additionally be a "Data loop file:".
(Same for "Metadata file:")

@unclejack

Signed-off-by: Vincent Batts vbatts@redhat.com

Presenly the "Data file:" shows either the loopback _file_ or the block device.
With this, the "Data file:" will always show the device, and if it is a
loopback, then there will additionally be a "Data loop file:".
(Same for "Metadata file:")

Signed-off-by: Vincent Batts <vbatts@redhat.com>
@crosbymichael
Copy link
Contributor

LGTM

@SvenDowideit
Copy link
Contributor

It would be nice if the devicemapper docker info output was documented in daemon/graphdriver/devmapper/README.md - I'm going to bet at some stage soon, the labels won't tell a new user what they mean.

and yes, I'm thankful for what's there already :)

} else {
status.MetadataLoopback = path.Join(devices.loopbackDir(), "metadata")
}
status.DataFile = devices.DataDevicePath()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder why you created methods for devices.dataDevice and not for devices.dataLoopFile?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah. good catch. I was initially having an "intelligent" function to return the information, but decided both device and file name is important.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, i remember now. If an inspectors of the DeviceSet instance wanted to access that information, having it in a function protects the private variable.

@vbatts
Copy link
Contributor Author

vbatts commented Jan 13, 2015

@SvenDowideit I will cook you up some docker info explanation in a separate PR <3

@unclejack
Copy link
Contributor

LGTM

unclejack added a commit that referenced this pull request Jan 13, 2015
devmapper: show device and loop file , if used
@unclejack unclejack merged commit 044d979 into moby:master Jan 13, 2015
@vbatts vbatts deleted the vbatts-dm_loop_file_info branch April 27, 2016 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants