Use Win32_Volume WMI class to list filesystems #111
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GetLogicalDriveStrings doesn't list filesystems that are mounted with access paths but don't have a drive letter. Querying Win32_Volume with WMI lists all volumes, mounted or not.
|
Are there any alternatives to using WMI? In the past we have had several issues like high CPU usage from the WMI service, WMI not being up and ready when the bear starts. |
|
I will try with these volume iterators. |
|
Closing this by now, implementation with volume iterators in #112 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GetLogicalDriveStringsdoesn't list filesystems that are mounted withaccess paths but don't have a drive letter. Querying
Win32_VolumewithWMI lists all volumes, mounted or not.
Reported on elastic/beats#8916