Re: sshfs does not seem to work correctly
Again I am guessing, but OpenBSD might disconnect if there is a sufficient period of inactivity on the sshfs file system. Usb drives disconnect if left long enough, for example. A running process, such as an open terminal on the usb prevents this. It is a security feature. There had only be seconds (at least one or two minutes) of inactivity. Can this feature be disabled? I'd like to use sshfs just as nfs so it should not disconnect if possible. A ssh session does not disconnect too, I see no difference between ssh and sshfs regarding security here. Carsten
Re: sshfs does not seem to work correctly
On 04-08-2014 05:17, Carsten Kunze wrote: Again I am guessing, but OpenBSD might disconnect if there is a sufficient period of inactivity on the sshfs file system. Usb drives disconnect if left long enough, for example. A running process, such as an open terminal on the usb prevents this. It is a security feature. There had only be seconds (at least one or two minutes) of inactivity. Can this feature be disabled? I'd like to use sshfs just as nfs so it should not disconnect if possible. A ssh session does not disconnect too, I see no difference between ssh and sshfs regarding security here. Carsten I've never used sshfs on OpenBSD yet, but there is a -o reconnect option in it on linux. I've used sshfs to move even larger datasets than 15GB with no problems. But you might want to tune it with by playing with the cache, compression, ciphers, etc options so it will give you better performance. Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
Re: sshfs does not seem to work correctly
On 2014-08-03, Carsten Kunze carsten.ku...@arcor.de wrote: I use sshfs to synchronize a filesystem of 15 GB between two machines. Read access seems to be ok but on writing the mount point does not seem to work anymore. Error message of cp(1) is No such file or directory ls(1) to the mount point gives the same message. (Nothing in /var/log/messages) Is it a known problem for sshfs that the mount point may disappear? (OpenBSD 5.5 amd64) --Carsten There were some problems with FUSE that were fixed post-5.5, perhaps you ran into one of those. (There are still certainly some missing features and possibly also other problems in the existing code, but no recent reports). If you still see such problems on -current/forthcoming 5.6 then the best option would be to make a proper problem report, with log information / output from a run with FUSE_DEBUG set, backtraces from the sshfs process if it crashes, etc.
Re: sshfs does not seem to work correctly
On 2014-08-04 09:17, Carsten Kunze wrote: Again I am guessing, but OpenBSD might disconnect if there is a sufficient period of inactivity on the sshfs file system. Usb drives disconnect if left long enough, for example. A running process, such as an open terminal on the usb prevents this. It is a security feature. There had only be seconds (at least one or two minutes) of inactivity. Can this feature be disabled? I'd like to use sshfs just as nfs so it should not disconnect if possible. A ssh session does not disconnect too, I see no difference between ssh and sshfs regarding security here. Carsten My guess is quite wrong. Sorry to say you need someone more knowledgeable than myself. :( Moss
Re: sshfs does not seem to work correctly
hmm, on Mon, Aug 04, 2014 at 01:15:03PM +, Stuart Henderson said that On 2014-08-03, Carsten Kunze carsten.ku...@arcor.de wrote: I use sshfs to synchronize a filesystem of 15 GB between two machines. Read access seems to be ok but on writing the mount point does not seem to work anymore. Error message of cp(1) is No such file or directory ls(1) to the mount point gives the same message. (Nothing in /var/log/messages) Is it a known problem for sshfs that the mount point may disappear? (OpenBSD 5.5 amd64) --Carsten There were some problems with FUSE that were fixed post-5.5, perhaps you ran into one of those. (There are still certainly some missing features and possibly also other problems in the existing code, but no recent reports). If you still see such problems on -current/forthcoming 5.6 then the best option would be to make a proper problem report, with log information / output from a run with FUSE_DEBUG set, backtraces from the sshfs process if it crashes, etc. actually i am seeing fuse regression with ntfs-3g in -current. i was able to copy ~1TB of data from external usb drives formatted ntfs in 5.5. in -current the process accessing the drive will inevitably spin and is not possible to kill. i was looking for a way to make a debug build and make a more detailed report. of course it could be also ntfs-3g but it wasn't updated since april. -f -- if money doesn't grow on trees, why is it green?
sshfs does not seem to work correctly
I use sshfs to synchronize a filesystem of 15 GB between two machines. Read access seems to be ok but on writing the mount point does not seem to work anymore. Error message of cp(1) is No such file or directory ls(1) to the mount point gives the same message. (Nothing in /var/log/messages) Is it a known problem for sshfs that the mount point may disappear? (OpenBSD 5.5 amd64) --Carsten
Re: sshfs does not seem to work correctly
On 2014-08-03 22:12, Carsten Kunze wrote: I use sshfs to synchronize a filesystem of 15 GB between two machines. Read access seems to be ok but on writing the mount point does not seem to work anymore. Error message of cp(1) is No such file or directory ls(1) to the mount point gives the same message. (Nothing in /var/log/messages) Is it a known problem for sshfs that the mount point may disappear? (OpenBSD 5.5 amd64) --Carsten Again I am guessing, but OpenBSD might disconnect if there is a sufficient period of inactivity on the sshfs file system. Usb drives disconnect if left long enough, for example. A running process, such as an open terminal on the usb prevents this. It is a security feature. Moss
