Bug 731186

Summary: fusermount -u on sshfs mountpoint fails with "Bad address"
Product: Red Hat Enterprise Linux 6 Reporter: Matt Rogers <mrogers>
Component: fuseAssignee: Josef Bacik <jbacik>
Status: CLOSED DUPLICATE QA Contact: yanfu,wang <yanwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-17 12:35:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Rogers 2011-08-16 21:11:15 UTC
Description of problem:
With fuse 2.8.3-3.el6_1, trying to unmount an sshfs mountpoint using 'fusermount -u /mnt/point' results in the error "fusermount: failed to unmount /mnt/point: Bad address:

Using fuse 2.8.3-1.el6 does not exhibit this behavior.

The current workaround is to either use umount or stay on 2.8.3-1.el6

Version-Release number of selected component (if applicable):

How reproducible:

1. Mount sshfs:

# sshfs /mnt/fuse/
root@'s password: 

# mount | grep fuse on /mnt/fuse type fuse.sshfs (rw,nosuid,nodev,max_read=65536)

2. Unmount

# fusermount -u /mnt/fuse/
fusermount: failed to unmount /mnt/fuse: Bad address

Additional info:

For the sshfs filesystem I'm using fuse-sshfs-2.2-1.el6.rf from rpmfusion.

Comment 1 RHEL Program Management 2011-08-16 21:28:10 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support

Comment 2 Josef Bacik 2011-08-17 12:35:48 UTC

*** This bug has been marked as a duplicate of bug 723757 ***