Package: curlftpfs
Version: 0.9.2-1
Severity: normal

  When copying and editing files (using vim) on a curlftpfs share, I
get very frequent hangs that require killing the curlftpfs process and
remounting everything.  One example is below; when I tried to copy a
file and then edit it, vim hung forever.  An strace showed:

mo...@mole:~$ sudo strace -p 3274
[sudo] password for moise: 
Process 3274 attached - interrupt to quit
futex(0xbfb97074, FUTEX_WAIT_PRIVATE, 0, NULL

  ... waiting forever.  The debug information that was printed out
right before the hang was:

unique: 422, opcode: OPENDIR (27), nodeid: 2, insize: 48
   unique: 422, error: 0 (Success), outsize: 32
unique: 423, opcode: RELEASEDIR (29), nodeid: 2, insize: 64
   unique: 423, error: 0 (Success), outsize: 16
unique: 424, opcode: OPEN (14), nodeid: 25, insize: 48
1238399123 ftpfs.c:734 opening /my.web.site.com/mypage-new.htm O_RDONLY
1238399123 ftpfs.c:348 We need to restart the connection 0x8edc160
unique: 425, opcode: LOOKUP (1), nodeid: 2, insize: 55
LOOKUP /my.web.site.com/mypage.htm

  Cheers!

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages curlftpfs depends on:
ii  fuse-utils                    2.7.4-1.1  Filesystem in USErspace (utilities
ii  libc6                         2.9-6      GNU C Library: Shared libraries
ii  libcurl3-gnutls               7.18.2-8.1 Multi-protocol file transfer libra
ii  libfuse2                      2.7.4-1.1  Filesystem in USErspace library
ii  libglib2.0-0                  2.20.0-2   The GLib library of C routines

curlftpfs recommends no packages.

curlftpfs 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