From: Florian E. <fl...@or...> - 2013-07-04 20:45:04
|
Hi, I've just come across a "problem" I encounter with sshfs and using the "-o reconnect" option. The reconnect does work fine, however all open files on the mountpoint are closed when ssh is disconnected and an error is returned to the application opening the files. After the reconnect the files (must/can) be reopened again. Now, this behaviour makes sense on the one hand to ensure data integrity (the files might have changed on the server during the disconnect). However, I'm using sshfs to mount a single large truecrypt container on a remote machine. Obviously the disconnect and closing of open files brakes the truecrypt mount and can potentially corrupt the filesystem in the mounted container. My question now: Is it somehow possible/feasible to add a "blocking/no-close" option to keep all currently open files open during a reconnect and have all i/o operations on these files block until we are reconnected. Data integrity is no problem in my use case, as I'm the only person acessing the remote truecrypt container, so nothing will have changed after the reboot (and of course these problems and potential dangers could be documented alongside this option). I would also be willing to help developing this option, if I could get some help from someone with a good understanding of the sshfs code where to look in the code or how such a thing might potentially be implemented. Thanks, Florian. |