Repository navigation
Sync filesystem instead of freezing it before snapshots - #3866
Merged
Merged
Conversation
β¦t before snapshots
A userspace filesystem freeze held across a LINSTOR snapshot leaves the
DRBD device frozen even once the filesystem has been thawed. The volume
can then never be mounted again ("Can't mount, blockdev is frozen").
Sync the filesystem instead.
Signed-off-by: Piotr Resztak <piotr.resztak@futurfusion.io>
stgraber
approved these changes
Aug 18, 2026
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.
Summary
Snapshotting a LINSTOR volume whose filesystem is mounted leaves the DRBD device permanently unmountable.
The kernel logs:
drbd1001: Can't mount, blockdev is frozen.The trigger is
CreateVolumeSnapshotfreezing the filesystem withfsfreezeand holding that freeze across the LINSTOR snapshot.Reproducer
Fix
Sync the filesystem rather than freezing it. This is a workaround. Bug also reported to LINSTOR: LINBIT/linstor-server#525