fscache: simple fixup for busy mountpoint #83
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
imeoer
force-pushed
the
fix-erofs-mountpoint
branch
from
09bf7d4
to
2286176
Compare
imeoer
changed the title
When snapshotter exits (either normally or abnormally), it will not have a chance to umount erofs mountpoint, so if snapshotter resumes running and mount again (by a new request to create container), it will need to ignore the mount error `device or resource busy`. Signed-off-by: Yan Song <yansong.ys@antfin.com>
imeoer
force-pushed
the
fix-erofs-mountpoint
branch
from
2286176
to
dc3e940
Compare
Codecov Report
@@ Coverage Diff @@
## main #83 +/- ##
=======================================
Coverage 28.78% 28.78%
=======================================
Files 17 17
Lines 1501 1501
=======================================
Hits 432 432
Misses 1005 1005
Partials 64 64 Continue to review full report at Codecov.
|
hsiangkao
approved these changes
Jun 29, 2022
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.
When snapshotter exits (either normally or abnormally), it will not have a
chance to umount erofs mountpoint, so if snapshotter resumes running and mount
again (by a new request to create container), it will need to ignore the mount
error
device or resource busy.Signed-off-by: Yan Song yansong.ys@antfin.com