Remove implication that child disk
s aren't vdevs in zpoolconcepts(7)
#15247
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.
Motivation and Context
A poster on a ZFS forum pointed out to me that zpoolconcepts(7) currently says that "virtual devices cannot be nested," which was inconsistent with my assertion that (child)
disk
s are also "vdevs."Alternatively, if I'm wrong about that, please give me some clarification so I can think about how to clarify that instead!
Description
I rephrase the paragraph to be clearer that it is only certain types of vdevs that cannot be nested, so as not to imply that child
file
s anddisk
s are not considered "vdevs."How Has This Been Tested?
man ./zpoolconcepts.7
mandoc -T lint zpoolconcepts.7
Types of changes
Checklist:
Signed-off-by
.