Bug 1461993
| Summary: | RFE - Log creation and removal of dm devices | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | John Pittman <jpittman> | ||||
| Component: | kernel | Assignee: | Heinz Mauelshagen <heinzm> | ||||
| kernel sub component: | Core | QA Contact: | Storage QE <storage-qe> | ||||
| Status: | CLOSED WONTFIX | Docs Contact: | |||||
| Severity: | low | ||||||
| Priority: | unspecified | CC: | agk, jbrassow, msnitzer, mthacker | ||||
| Version: | 7.4 | Keywords: | FutureFeature | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-10-13 14:59:37 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: | |||||||
| Attachments: |
|
||||||
Meant to mention we log sd layer attach/creation as well, so logging dm would line up with that layer too. Don't you rather want to see logging of 'lvm2' messages ?
Such feature already exists in lvm.conf.
See the lvm.conf 'syslog=1' setting for logging in log{} section.
You may also select your preferred 'verbosity' level for less or more detailed syslogging of any lvm2 command.
What'd be the purpose of 'dm-XX' logging - these numbers are rather meaningless - as it's quite hard to 'map' dm-X to i.e. VG/LV in system for just this 'trace'.
I do not think that all dm devices creation and removal should be logged by default. Note, there is difference between plugging of hw device (sd layer) and creating virtual (and possible private) device mapping. For example, cryptsetup in some situations uses temporary devices that maps keyslots. This action is private to cryptsetup and should be visible only if users explicitly switch debug on. (It could reveal which keyslot was used, how many tries user did etc). And if you are using hidden disk mapping for Truecrypt compatible device, it is even security problem for the user (it documents that user mapped something that should be, well, "hidden". There are probably other info that already reveals such action in log but we should not make this even worse. Please be very careful with enabling such features. For lvm it maybe makes sense (but just for top-level device and not with dm-X name) but for other users of device-mapper subsystem is is not so great idea. Milan, Zdenek, Yes, I agree. My need was related to wanting to see multipath partition devices being created. Perhaps I can focus my efforts there and see if I can come up with a better solution. Will close this or change component with updated possible patch as soon as I'm able to research this more. Thanks for your time. Sorry guys, I forgot about this. I am fine if this is closed. The premise is good for troubleshooting rare conditions, but that's about it I think. Going to close this as alternatives were suggested. |
Created attachment 1288202 [details] example patch to add dm creation/removal logging Description of problem: RFE proposal to log addition and removal of dm devices by default. Thought of this while troubleshooting an environment in which I needed to know if a multipath partition device was created during a particular boot process. Then realized that there is no record of dm device creation. This is inconsistent with other devices, as their creation is logged (dm, mdadm, multipath, lvm activation). Very rarely are there systems that do not have an active dm layer. Even though the names are not persistent, troubleshooting information can be gathered from knowing when the dm layer is increased or reduced. Adding the actual dmsetup name to the output would be wonderful, but unsure if this is possible; I could not find an easy way. Version-Release number of selected component (if applicable): kernel-3.10.0-681.el7 Actual results: dm-x device addition and removal is not logged Expected results: Jun 15 16:27:26 localhost.localdomain kernel: device-mapper: core: Created dm-0 Jun 15 16:27:26 localhost.localdomain kernel: device-mapper: core: Created dm-1 Jun 15 16:27:28 localhost.localdomain kernel: device-mapper: core: Created dm-2 Jun 15 16:27:28 localhost.localdomain kernel: device-mapper: core: Created dm-3 Jun 15 16:27:28 localhost.localdomain kernel: device-mapper: core: Created dm-4 Jun 15 16:27:28 localhost.localdomain kernel: device-mapper: core: Removing dm-4 Jun 15 16:27:29 localhost.localdomain kernel: device-mapper: core: Created dm-4 Jun 15 16:27:29 localhost.localdomain kernel: device-mapper: core: Created dm-5 ...... Jun 15 16:31:57 localhost.localdomain kernel: device-mapper: core: Removing dm-4 Any consideration is appreciated.