Repository navigation
Odmontowanie osieroconego montowania po padzie rclone - #29
Merged
Merged
Conversation
On 25.10 and 27.10 rclone ended with "Mount failed" / "failed to umount FUSE fs" during a backup, but the FUSE-T NFS mount stayed in the mount table. mount-drive then saw it as "Already mounted" and never started rclone again, while every stat of the mount hung - 8 h on 27.10, until the Mac was restarted. OrphanMount checks the mount table (MNT_NOWAIT) and the process table (pgrep/ps, exiting and zombie processes do not count), never the file system. buffer-guard watches in its own task and runs `umount -f` after 60 s of a listed mount with no live rclone; mount-drive does the same at start-up, before deciding the mount is already up. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Co
OrphanMount: gdy montowanie Drive jest w tablicy montowań, a żaden żywy rclone go nie trzyma, agenty robiąumount -f.buffer-guardsprawdza co 30 s w osobnym zadaniu (zawieszona sonda głównej pętli go nie blokuje); działa po 60 s, bo zwykły restart rclone przez launchd też ma chwilę bez procesu.mount-driverobi to samo przy starcie, zanim uzna, że jest „Already mounted”.Sprawdzenie nie dotyka systemu plików: tablica montowań przez
getmntinfo(MNT_NOWAIT), procesy przezpgrep/ps(stanE/Z= nieżywy). Każda wątpliwość (nie da się odczytać) = nic nie robi.Dlaczego
25.10 00:02 i 27.10 00:19, obie w trakcie kopii: rclone
Mount failed/CRITICAL: failed to umount FUSE fsi wyjście, a martwe NFSfuse-t:/gdrivezostało.mount-drivewidział „Already mounted”, wszystko, co robistatmontowania, wisiało. 27.10 trwało to 8 h, do restartu Maca. 25.10 ręcznyumount -fwystarczył, rclone wrócił po 30 s. #28 (seria EAGAIN) tego nie łapie.Testy
swift test: 436 zielonych (6 nowych wOrphanMountTests), lint--strictczysty.pgrepz tym wzorcem znajduje żywy rclone (stanS). Na prawdziwym osieroconym montowaniu niesprawdzone.🤖 Generated with Claude Code