Explain snapshot failures caused by regular directories - #11287
Open
hussainanjar wants to merge 1 commit into
Open
Explain snapshot failures caused by regular directories#11287hussainanjar wants to merge 1 commit into
hussainanjar wants to merge 1 commit into
Conversation
This file contains hidden or 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
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 a backup restore leaves
.snapshotsas a regular directory,omarchy snapshot createstops with Snapper's opaque Btrfs error. Add guidance to locate the affected config's subvolume, preserve the directory's contents, and recreate it as a Btrfs subvolume before retrying.Keep the original error and exit status, skip cleanup after failed creation, and leave unrelated failures without subvolume repair advice.
Fixes #11100.
Validation:
./test/cli, Bash syntax checks, andgit diff --checkpass../test/all(236 shell test files). Five environment/artifact failures passed on focused reruns after supplying theomarchy-pkgsandomarchy-isocheckouts, unsettingNO_COLOR, and removing generated Python bytecode.runtime-smoke-test.shfails its duplicate IPC-handler check on this two-monitor session. The same check also fails on a clean upstreamquattrocheckout atb5589faa.