Skip to content

Remount fixes#55

Open
hsteinhaus wants to merge 1 commit intoMabezDev:masterfrom
emobotics-dev:remount-fixes
Open

Remount fixes#55
hsteinhaus wants to merge 1 commit intoMabezDev:masterfrom
emobotics-dev:remount-fixes

Conversation

@hsteinhaus
Copy link
Copy Markdown

Fix the use case of unmounting a file system after use and re-mounting it immediately again from the same storage device.

…ore trying to read BPB.

This is particulary important during a re-mount of a previously mounted storage device. BUT: do not try to seek in an debug_assert!() - otherwise this important side effect will not happen in a release build.
@hsteinhaus hsteinhaus force-pushed the remount-fixes branch 2 times, most recently from cbbfcd9 to 24c9e0b Compare February 27, 2026 18:06
@MabezDev
Copy link
Copy Markdown
Owner

MabezDev commented Apr 2, 2026

Why not just seek back to zero before passing the storage back into the new filesystem?

@hsteinhaus
Copy link
Copy Markdown
Author

Counter question: should the outcome of an attempt to mount an fs really depend on the state of the underlying block device? I personally would find this behaviour at least surprising.

@MabezDev
Copy link
Copy Markdown
Owner

MabezDev commented Apr 2, 2026

Fair enough, in which case remove the debug assert, I don't think it does anything anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants