Subject: sshfs in combination with bind mounts and umount -f fails
Package: sshfs
Version: 2.2-1
Severity: normal

*** Please type your report below this line ***

If an sshfs file system is mounted, then mapped to a different location
in the file system using a bind mount and then the bind mount is unmounted
using the -f (force) flag (as is done for example in /etc/init.d/umountfs),
the sshfs mount breaks:

---
root:~/.ssh# mkdir -p /mnt/mp1
root:~/.ssh# mkdir -p /mnt/mp2
root:~/.ssh# sshfs localhost:/home /mnt/mp1
root:~/.ssh# mount -o bind /mnt/mp1 /mnt/mp2
root:~/.ssh# umount -f /mnt/mp2
root:~/.ssh# ls /mnt/mp1
ls: cannot access /mnt/mp1: Transport endpoint is not connected
---

This is a problem when the bind mount is within a container
(OpenVZ, lxc) and the container runs unmodified init scripts
that unmount the bind mount with the -f flag. It leads to all
other applications and containers to not be able to read
from the sshfs mount any more.

The problem also occurs with glusterfs, the it may be a problem
in the fuse libraries or kernel driver.

-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sshfs depends on:
ii  fuse-utils                    2.8.4-1.1  Filesystem in USErspace
(utilities
ii  libc6                         2.11.2-10  Embedded GNU C Library:
Shared lib
ii  libfuse2                      2.8.4-1.1  Filesystem in USErspace library
ii  libglib2.0-0                  2.24.2-1   The GLib library of C routines
ii  openssh-client                1:5.5p1-6  secure shell (SSH) client,
for sec

sshfs recommends no packages.

sshfs suggests no packages.

-- no debconf information




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to