Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No mount cleanup after kill -9 and restart #172

Open
Juul opened this issue Jul 12, 2024 · 1 comment
Open

No mount cleanup after kill -9 and restart #172

Juul opened this issue Jul 12, 2024 · 1 comment

Comments

@Juul
Copy link

Juul commented Jul 12, 2024

After killing ouisync with kill -9 due to issue #171 and then re-starting ouisync with ouisync start the ~/ouisync directory still contains what appears to be both a normal empty directory for one repo (locally created repo) and one hung mountpoint in a weird state for a repo created by another peer and synced to this peer:

$ ls -l ~/ouisync/
ls: cannot access '/home/<user>/ouisync/eq test 1': Transport endpoint is not connected
total 0
d????????? ? ?    ?      ?            ? 'eq test 1'
dr-xr-xr-x 1 root root 193 Dec 31  1969  phone

Stopping ouisync with ctrl-c (which worked this time), then manually unmounting /home/<user>/ouisync/eq test 1 and re-starting ouisync fixed the issue.

ouisync should probably recover better from an unclean exit by e.g. detecting stale ouisync mounts and unmounting them

@Juul
Copy link
Author

Juul commented Jul 12, 2024

I should add that after a kill -9 I can't unmount repos at all without sudo, which is interesting since at no point did I use sudo to install or run ouisync:

$ umount ~/ouisync/phone 
umount: /home/<user>/ouisync/phone: Transport endpoint is not connected

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

No branches or pull requests

1 participant