Filesystem in Userspace

Hi.

I tried to find the manpage for sshfs but in vain. The
information I was
looking for is about how to set user rights to the
mounted directories
proper.
When I mount that ssh filesystem with a local user,
every other user
(even root) sees nothing but
d?????????  ? ?      ?         ?            ?
/mnt/sshfs
with ls -la
Though I need so set groupaccess to one of these
mountpoints to have a
server script access to a sshfs directory with certain
rights.
What are the options sshfs accepts to set group? 
~# mount
sshfs#remoteuser@... on /mnt/sshfs
type fuse
(rw,nosuid,nodev,max_read=65536,user=localuser)
Is there a way to set group=somegroup or to get rid of
the "?" in the ls
output?

Regards
G.Koseleck




      Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: 
http://de.yahoo.com/set

Hi again,

Are there more suggestions for hanging hyper-threads?

>From being rid of this problem for a month, it has popped up again. I
had a fiery crash after about a week of uptime, thought it was a
hardware problem, then another within 24 hours, updated to latest fuse,
and now again after 32 hours (this time on file delete on sshfs share.)

I have a web of servers and VMs hooked up with sshfs, and after some
time, the real-hardware hyper-threading Pentium 4 one crashes. The
symptom is that process by process, as they attempt a disk write, hangs
until you are either out of shells or the computer becomes unresponsive.
A write does not have to be to an sshfs mount. You may have 98% iowait
but no network or disk activity.

This box used to be CentOS5, now it is the same hardware but on fedora
core 7, same symptoms. The non-hyperthreading boxes appear to do fine,
but they are also on Ubuntu 7.10.

Yesterday, I installed the latest stable fuse 2.7.0 from source as
instructed by Miklos:
  tar xfz fuse*.tar.gz
  cd fuse*
  ./configure --enable-kernel-module
  make
  make install
  rmmod fuse
  modprobe fuse

$ sshfs -V
SSHFS version 1.7
FUSE library version: 2.7.0
fusermount version: 2.7.0
using FUSE kernel interface version 7.8
[foxyboy@... ~]$ dmesg | grep fuse
fuse init (API version 7.8)
fuse distribution version: 2.7.0

It survived for 32 hours. Now, I will see how long it runs without sshfs
just to make sure that's the problem. A future step may be to run in
singleton mode?

Grateful for any help

Harald Rudell

-----Original Message-----
From: Miklos Szeredi [mailto:miklos@...
Sent: Monday, August 27, 2007 6:18
To: Harald Rudell
Cc: fuse-sshfs@...
Subject: Re: [sshfs] mounted sshfs disconnects or hangs - solved

> So there were three issues on Linux, ntfsclone, concurrent copying,
and
> CentOS5 crashing. I came up with some nasty shell scripts that I could
> run on various machines for repro. Here are solutions:
>=20
> Ubuntu 7.04 comes with sshfs 1.6 that is deficient, while sshfs 1.7 in
> gutsy 7.10 works fine. Do this:
> $ sshfs -V
> SSHFS version 1.6
> --now, that's bad
> 1. Browse to http://packages.ubuntu.com/gutsy/allpackages
> 2. Click around and download three packages
> 2a. Libc6 (filename libc6_2.6.1-0ubuntu1_i386.deb)
> 2b. Libglib2.0-0 (filename libglib2.0-0_2.13.7-1ubuntu4_i386.deb)
> 2c. Sshfs (filename sshfs_1.7-2.1_i386.deb)
> 3. Install all three with dpkg -i filename
> $ sshfs -V
> SSHFS version 1.7
> -- problem gone
>=20
> For the crashing Red Hat, I compiled the kernel module as outlined by
> Miklos. Sshfs -V and modinfo fuse lists the EXACT same information
> before/after, but the problem seems to be gone. So either somebody is
> not compiling right, or there is a version change not reflected?

The version change is only reflected in 'dmesg | grep fuse' output.

But the fact that using the module from the source package cured it
for you makes it very likely that it was indeed the suspected problem.

Thanks for confirming that everything works OK.

Miklos

Dear All,

I have installed sshfs 1.3.0 on my Ubuntu 6.06.1 x86 machine. I mounted 
a directory /test in abcd24 to my Ubuntu machine and mount shows the 
following report

<mount>
sshfs#XXXXX@... on /mnt/test type fuse 
(rw,nosuid,nodev,max_read=65536)
</mount>

Now the problem is when I try to create a file with Owner-Read and 
Owner-Execute permissions, it creates the file with specified 
permissions, but reports Permission denied error message. please see the 
following code, result and strace report. I would like to know whether 
this is known issue and if the fix for the same is available.

<code>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <fcntl.h>
#include <sys/types.h>
#include <sys/stat.h>

int main(int argc, char *argv[]) {
    int oflags = O_CREAT | O_EXCL | O_WRONLY;
    mode_t mode = S_IRUSR | S_IXUSR;

    int fd = open64(argv[1], oflags, mode);
    if (fd == -1) {
    fprintf(stderr, "open64 failed: %s\n", strerror(errno));
    return -1;
    } else {
    close(fd);
    }
    return 0;
}
</code>

<result>
root@...# strace -o ctrace ./test /mnt/test/cfile
open64 failed: Permission denied
root@...# ls -l /mnt/test/cfile
-r-x------ 1 158576 uucp 0 Sep 24 14:18 /mnt/test/cfile
</result>

<strace report>
open("/mnt/test/cfile", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0500) = -1 
EACCES (Permission denied)
write(2, "open64 failed: Permission denied"..., 33) = 33
exit_group(-1)                          = ?
</strace report>

Thanks
Rajendra.

When I try to mount sshfs I get the following error unless I change
ownership to my user or I run it as root.  Neither option seems optimal.

The error message is:
fusermount: failed to open /dev/fuse: Permission denied

and when I do an ls -la /dev/fuse I get
crw-rw---- 1 root fuse 10, 229 2007-09-19 20:07 /dev/fuse
Is there a way to get it to work without the previous options?  Thanks.

I've been getting a crash of some sort with sshfs-1.8.

Some system details:
ppc arch
openssh-4.7p1
fuse-2.6.4
kernel 2.6.20


Test details:

I have some media files I want to transfer from encoders to a remote 
server via ssh since it can be niced better than nfs and is faster than 
smb.  FTP was also ruled out, though I forget why now.  During file copy 
sshfs segfaults or just dies and the client side gets this message: 
"Transport endpoint is not connected."

Here's a test I've been using the reproduce the problem:

# Make some fake media files.
cd /tmp
mkdir tmp
for i in `seq 1 3`; do
	dd if=/dev/urandom of=test${i} bs=1M count=128
done
for i in `seq 4 6`; do
	dd if=/dev/urandom of=test${i} bs=1M count=512
done
for i in `seq 7 9`; do
	dd if=/dev/urandom of=test${i} bs=1M count=1024
done


# Mount the remote server via sshfs
sshfs user@... /mnt/tmp -d -s -o sshfs_debug -o reconnect -o 
intr -o IdentityFile=/home/user/.ssh/id_dsa -o Ciphers=arcfour -o 
ServerAliveInterval=15 2>&1 | tee sshfs.out
mkdir /mnt/tmp/.tmp

### Repeat from here down ####
cp test[1-9] tmp/

# Cleanup the remote server side to avoid rename workaround.
rm /mnt/tmp/.tmp/test[1-9]
rm /mnt/tmp/test[1-9]

# Move them to a remote server so that they're
# only visible once they're ready.
for i in `seq 1 9`; do
	mv tmp/test${i} /mnt/tmp/.tmp/test{$i} \
	&& mv /mnt/tmp/.tmp/test{$i} /mnt/tmp/
done


Eventually, the program output will do one of several things:
1) just die
2) segfault
3) report an out of memory condition

All three result in output like this when I do a df:
# df /mnt/tmp

"Transport endpoint is not connected"


To correct the error I can do "umount /mnt/tmp" and remount it, but 
that's such a pain with how often its happening.

Any suggestions?

Let me know if you need more output.

Thanks,
Brian


Brief snippit from the 8M+ output capture:

[101818] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101966, error: 0 (Success), outsize: 24
   [101817]         STATUS       28bytes (0ms)
unique: 101967, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13963264
[101819] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101967, error: 0 (Success), outsize: 24
   [101818]         STATUS       28bytes (0ms)
unique: 101968, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13967360
[101820] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101968, error: 0 (Success), outsize: 24
   [101819]         STATUS       28bytes (0ms)
unique: 101969, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13971456
[101821] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101969, error: 0 (Success), outsize: 24
unique: 101970, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13975552
[101822] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101970, error: 0 (Success), outsize: 24
   [101820]         STATUS       28bytes (1ms)
   [101821]         STATUS       28bytes (0ms)
unique: 101971, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13979648
[101823] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101971, error: 0 (Success), outsize: 24
unique: 101972, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13983744
[101824] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101972, error: 0 (Success), outsize: 24
unique: 101973, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13987840
[101825] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101973, error: 0 (Success), outsize: 24
   [101822]         STATUS       28bytes (1ms)
unique: 101974, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13991936
[101826] WRITE
   [101823]         STATUS       28bytes (1ms)
   [101824]         STATUS       28bytes (0ms)
    WRITE[4148168864] 4096 bytes
    unique: 101974, error: 0 (Success), outsize: 24
   [101825]         STATUS       28bytes (0ms)
unique: 101975, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 13996032
[101827] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101975, error: 0 (Success), outsize: 24
   [101826]         STATUS       28bytes (0ms)
unique: 101976, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 14000128
[101828] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101976, error: 0 (Success), outsize: 24
unique: 101977, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 14004224
[101829] WRITE
    WRITE[4148168864] 4096 bytes
    unique: 101977, error: 0 (Success), outsize: 24
   [101827]         STATUS       28bytes (0ms)
   [101828]         STATUS       28bytes (0ms)
   [101829]         STATUS       28bytes (0ms)
unique: 101978, opcode: WRITE (16), nodeid: 10, insize: 4160
WRITE[4148168864] 4096 bytes to 14008320
sshfs: memory allocation failed

Hi,

=20

i use command

 sshfs -o ConnectTimeout=3D5 -o ServerAliveInterval=3D60 -o=
 ServerAliveCountMax=3D1 -o TCPKeepAlive=3Dyes -o reconnect -o LogLevel=
=3DDEBUG3 -f -d user@...=
 <mailto:user@...>  /partage/tmp/logs/CLI /


whith version:

 $ sshfs -V
SSHFS version 1=2E6
FUSE library version: 2=2E5=2E3
fusermount version: 2=2E5=2E3
using FUSE kernel interface version 7=2E5

Then=20

on first terminal i copy a bigtext to the  mounted directory =
 /partage/tmp/logs/CLI
on second terminal  i do  command "ls /partage/tmp/logs/CLI/CE" to test=20

=20

I start firewall on host remote  to simulate a broken line=2E=2E=2E
after 60 second i have got normal error (input /ouptut error) and suddenly=
 after repeating  ls,  sshfs crash=2E=2E=2E

After that the monted directory is in strange state=20

=20

$ls /partage/tmp/logs/CLI
ls: /partage/tmp/logs/CLI: Noeud final de transport n'est pas connect=E9


Translated to english


$ls /partage/tmp/logs/CLI
ls: /partage/tmp/logs/CLI: Transport endpoint is already connected=20

=20

sshfs did a segmentation fault =2E=2E=2E=20

write: Broken pipe
   unique: 17133, error: -5 (Input/output error), outsize: 16
remote host has disconnected
unique: 17134, opcode: GETATTR (3), nodeid: 1, insize: 40
remote host has disconnected
   unique: 17134, error: -5 (Input/output error), outsize: 16
unique: 17135, opcode: LOOKUP (1), nodeid: 1, insize: 43
LOOKUP /CE
write: Broken pipe
   unique: 17135, error: -5 (Input/output error), outsize: 16
remote host has disconnected
unique: 17136, opcode: LOOKUP (1), nodeid: 1, insize: 43
LOOKUP /CE
remote host has disconnected
   unique: 17136, error: -5 (Input/output error), outsize: 16
unique: 17137, opcode: LOOKUP (1), nodeid: 1, insize: 43
LOOKUP /CE
write: Broken pipe
   unique: 17137, error: -5 (Input/output error), outsize: 16
remote host has disconnected
unique: 17138, opcode: LOOKUP (1), nodeid: 1, insize: 43
LOOKUP /CE
   NODEID: 2
   unique: 17138, error: 0 (Success), outsize: 136
unique: 17139, opcode: OPENDIR (27), nodeid: 2, insize: 48
   unique: 17139, error: 0 (Success), outsize: 32
unique: 17140, opcode: READDIR (28), nodeid: 2, insize: 64
Erreur de segmentation




*********************************
This message and any attachments (the "message") are confidential and=
 intended solely for the addressees=2E=20
Any unauthorised use or dissemination is prohibited=2E
Messages are susceptible to alteration=2E=20
France Telecom Group shall not be liable for the message if altered,=
 changed or falsified=2E
If you are not the intended addressee of this message, please cancel it=
 immediately and inform the sender=2E
********************************

> Just encountered this, I've pasted in the dmesg which should supply you with
> any necessary info, if you need any more, just shout.
> 
> I've posted this incase it's of any use to anyone ! ;o)

Thanks.

Should be fixed in newer kernels (2.6.21 or greater I think).

Miklos

Hi


Command:
sshfs -o ConnectTimeout=3D5 -o ServerAliveInterval=3D60 -o
ServerAliveCountMax=3D1 -o TCPKeepAlive=3Dyes -o reconnect -o
LogLevel=3DDEBUG3 -f -d -o debug -o  sshfs_debug -o loglevel=3Ddebug
x@... /partage/tmp/logs/CLI


A error during reconnection afert ServerAliveInterval timeout reached :=20

=20

debug2: client_session2_setup: id 0
debug1: Sending subsystem: sftp
debug2: channel 0: request subsystem confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
Server version: 3
[08489] LSTAT
  [08489]         STATUS       33bytes (2ms)
   unique: 10448, error: -2 (No such file or directory), outsize: 16
unique: 10449, opcode: GETATTR (3), nodeid: 1, insize: 40
[08490] LSTAT
  [08490]          ATTRS       41bytes (0ms)
   unique: 10449, error: 0 (Success), outsize: 112
unique: 10450, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 10450, error: 0 (Success), outsize: 32
unique: 10451, opcode: GETATTR (3), nodeid: 1, insize: 40
   unique: 10451, error: 0 (Success), outsize: 112
unique: 10452, opcode: READDIR (28), nodeid: 1, insize: 64
[08491] OPENDIR
  [08491]         HANDLE       17bytes (1ms)
[08492] READDIR
debug2: channel 0: read<=3D0 rfd 5 len 0
debug2: channel 0: read failed
debug2: channel 0: close_read
debug2: channel 0: input open -> drain
debug2: channel 0: ibuf empty
debug2: channel 0: send eof
debug2: channel 0: input drain -> closed
Erreur de segmentation
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)

debug3: channel 0: close_fds r -1 w -1 e 7 c -1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 2=2E0 seconds
debug1: Bytes per second: stdin 0=2E0, stdout 0=2E0, stderr 0=2E0
debug1: Exit status 0



*********************************
This message and any attachments (the "message") are confidential and=
 intended solely for the addressees=2E=20
Any unauthorised use or dissemination is prohibited=2E
Messages are susceptible to alteration=2E=20
France Telecom Group shall not be liable for the message if altered,=
 changed or falsified=2E
If you are not the intended addressee of this message, please cancel it=
 immediately and inform the sender=2E
********************************