FS#17639 - [initscripts] net: netfs does not mount sshfs on boot

Attached to Project: Arch Linux
Opened by jasin (rooloo) - Tuesday, 29 December 2009, 16:12 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 27 April 2011, 10:20 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Netfs seems to be a little flaky. I was having issues with sshfs not mounting on boot. The link to the thread can be found here http://bbs.archlinux.org/viewtopic.php?id=87658.



Additional info:
The solution was to delete /root/.ssh/known_hosts file and then from root/ssh to 'user' on the machine you want to mount. This will ask you to re-authenticate and create a new /root/.ssh/known_host file. The known_hosts file had two entires in it. I think this is where netfs is getting confused on boot.


Steps to reproduce:
1. setup ssh w/rsa and sshfs automount on boot from /etc/fstab.
2. change ip address of the machine you're mounting
3. re-authenticate root */root/.ssh/known_hosts should now have two entries, one for each ip, with the working host as entry #2
4. now restart and watch netfs fail on boot with error 'connection reset by peer'
5. once fully booted, re-issue the cmd /etc/rc.d/netfs start and it should connect with no issues.

Please refer to the forum thread for some specifics on my fstab configuration.

Seems that netfs on boot quits as soon as the first rsa authentication fails, but while the machine is fully booted it seems to not care about the first ras authentication failure.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Wednesday, 27 April 2011, 10:20 GMT
Reason for closing:  No response
Comment by jasin (rooloo) - Tuesday, 29 December 2009, 23:24 GMT
I should add that ssh and sshfs bothed worked just fine when the machine was fully booted. I keep thinking that maybe my known_hosts file was corrupt or something, but it clearly couldn't have been.

I don't know why this ended up in community packages??? if some dev could move it to the appropriate place.
Comment by Roman Kyrylych (Romashka) - Tuesday, 10 August 2010, 10:03 GMT
what this has to do with netfs which only calls mount?
Comment by Tom Gundersen (tomegun) - Friday, 22 April 2011, 17:14 GMT
Is this still a problem?

As Roman points out, netfs doesn't really do anything except call mount. The only possible problem I can see is that netfs is started too early (no network yet), but this we cannot solve (and from our description I don't think this is the issue here).

Loading...