feat(mount): moving to legacy mount #151
Merged
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
pawanpraka1
added
enhancement
Codecov Report
@@ Coverage Diff @@
## master #151 +/- ##
==========================================
- Coverage 22.90% 22.71% -0.19%
==========================================
Files 14 14
Lines 489 493 +4
==========================================
Hits 112 112
- Misses 376 380 +4
Partials 1 1
Continue to review full report at Codecov.
|
pawanpraka1
removed
pr/hold-merge
pawanpraka1
force-pushed
the
mount
branch
3 times, most recently
from
b0cb873
to
e193069
Compare
kmova
reviewed
Jun 9, 2020
We can not mount the datasets to more than one path via zfs mount command, shifting to the legacy way of handling ZFS volumes where we can mount/umount the datasets via legacy mount and umount commands. This will also add a building block for SINGLE-NODE-MULTI-WRITER Capability. Signed-off-by: Pawan <pawan@mayadata.io>
kmova
approved these changes
Jun 9, 2020
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.
Signed-off-by: Pawan pawan@mayadata.io
Pull Request template
Please, go through these steps before you submit a PR.
Why is this PR required? What issue does it fix?:
We can not mount the datasets to more than one path via zfs mount command, shifting to the legacy way of handling ZFS volumes where we can mount/umount the datasets via legacy mount and umount commands.
This will also add a building block for SINGLE-NODE-MULTI-WRITER Capability.
Checklist:
<type>(<scope>): <subject>