Force disable VSMB direct map when the volume does not support it #894
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.
VSMB direct map requires support for querying FileIdInfo from the
backing volume. There is a bug in certain Windows versions where instead
of falling back to non-direct map when FileIdInfo is not supported, VSMB
instead causes errors whenever files on the share are accessed.
To work around this until the issue is fixed, we will query FileIdInfo
ourselves when setting up a VSMB share, and force disable direct map if
the query fails.
Signed-off-by: Kevin Parsons [email protected]