Mounting a ssh filesystem with FUSE succeeds but still gives error

[Ketil Wendelbo Aanensen]

Binary package hint: sshfs

Karmic alpha6, all updates.

Not quite sure if this is the correct package to assign this to.

I ssh into my server, and mount it now through Places > ssh-backup
When I click the item ssh-backup is mounted and I see it on my desktop, and I can access it fine. However, I *always* get an error dialog:

Unable to mount ssh-backup
Timeout waiting for mount to appear

I close the dialog, and all is still well. Rather annoying and unpolished thing.

[shankao (shankao)]

Confirmed in Karmic Beta

[tave (tave)]

also in karmic final

[shankao (shankao)]

And lucid alpha2 :)

[Charlie Kravetz (cjkgeek)]

Thanks for this report. Does this error appear when not mounting through nautilus (Places)? I have not seen the error, using Xubuntu Lucid with SSHFS manually run to mount my 12 directories.

[tave (tave)]

I get the error via nautilus

if i try "sudo mount /media/server" i get "read: Connection reset by peer"

my fstab entry is: sshfs#<email address hidden>:/media/data /media/server fuse users,rw,noauto 0 0

maybe its a configproblem

the command "sshfs <email address hidden>:/media/data /media/server/" works well

[Charlie Kravetz (cjkgeek)]

tave: I think you might be seeing a different bug, bug 243298. Try using

sshfs#<email address hidden>:/home/user /mnt/sshdisk fuse user,noauto,fsname=sshfs#<email address hidden>:/home/user 0 0

(this is supposed to be one line in fstab)

If this works, you have that bug instead.

As for this bug, I have attempted to reproduce this issue in Nautilus using Ubuntu Lucid Beta1, dated 2010-03-17.1 and cannot get the error. Could you please give me step-by-step instructions if you can reproduce it.

[strangedata (rcteigao)]

Indeed, adding fsname to my fstab entry solved both the mounting and unmounting problems.

[Charlie Kravetz (cjkgeek)]

I have attempted to reproduce this issue in Nautilus using Ubuntu Lucid and cannot get the error. Could you please give me step-by-step instructions if you can reproduce it.

[Charlie Kravetz (cjkgeek)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Ash Kyd (k-launchpad-kyd-com-au)]

I can reproduce this bug by:

# Add the following line to my fstab: sshfs#ash@10.0.2.4:/media/Backups/ash /media/Backups fuse user,noauto,reconnect,nonempty 0 0
# Click the entry "Backups" in the Nautilus "Computer" place.

Actual result:
# Nautilus waits to connect to the server, displaying the message "Opening 'Backups'. You can stop this operation by clicking cancel."
# Another icon with the same name "Backups" appears in the "Computer" place. The second icon contains the desired remote filesystem.
# Eventually Nautilus times out with the message "Unable to mount location. Timeout waiting for mount to appear"

Desired result:
The mountpoint should mount under the first icon instead of creating another.

Solution:
The solution is to add the following option to the fstab line: fsname=sshfs#ash@10.0.2.4:/media/Backups/ash

This appears to tell Nautilus that the mounted filesystem and the fstab entry are the same item, and makes clicking the unmounted filesystem mount in the right place instead of creating another icon. I'm not sure if this is merely a configuration error or truly a bug, but I thought I'd provide the workaround here, because it's truly frustrating.

I have attached a screenshot of this taking place.