Bug 649430 – sshfs checks for errors in the wrong order

Bug 649430 - sshfs checks for errors in the wrong order

Summary:	sshfs checks for errors in the wrong order

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	fuse (Show other bugs)
Sub Component:
Version:	14
Hardware:	Unspecified Unspecified

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Peter Lemenkov
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-11-03 14:01 EDT by Need Real Name
Modified:	2011-12-17 09:40 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-12-17 09:40:45 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2010-11-03 14:01:54 EDT

sshfs does not check if a mountpoint exists before attempting a mount. It fails later, after the expensive part.

$ sshfs 1.2.3.4:/something localdir
user@1.2.3.4's password: 
fuse: bad mount point `localdir': No such file or directory

It would be good if the existance of "localdir", the local mountpoint was checked before the network part began.

Comment 1 Peter Lemenkov 2011-12-17 09:40:45 EST

It seems fixed in the recent fuse.

Note You need to log in before you can comment on or make changes to this bug.