SMBNetFS

It believed that i found and fix this bug in the latest git. If the bug
still observed, please reopen this topic.

> I confirm what forest noticed. Upgrading to 0.50git the crash ( Transport
endpoint is not connected ) occur much less frequently. The app is quite
usable, i can access to my samba share for stream videos, but the crash
happen again when i try to copy many tiny files.

I really need logs and/or gdb backtrace of this situation.
try "smbnetfs -d mountpoint | tee -o smbnetfs.log", reproduce situation
and send me a log.

>That upload speed is much improved since the last git pull, but it's still
relatively slow. Any chance it could be improved further?

try "smbnetfs mountpoint -o max_write=131072"

I confirm what forest noticed.
Upgrading to 0.50git the crash ( Transport endpoint is not connected )
occur much less frequently.
The app is quite usable, i can access to my samba share for stream videos,
but the crash happen again when i try to copy many tiny files.

Anyway thx for this little useful app :).

I just updated my git checkout and tried again. Here are the new transfer
time estimates:

NAS -> workstation using mount.cifs: 6 minutes
NAS -> workstation using smbnetfs: 6 minutes
workstation -> NAS using mount.cifs: 5 minutes
workstation -> NAS using smbnetfs: 21 minutes

That upload speed is much improved since the last git pull, but it's still
relatively slow. Any chance it could be improved further?

Next, I'll try to make it crash again with logging enabled...

> smbnetfs died.

The restart of samba server can kill smbnetfs-0.3.x, but it should not
affect smbnetfs-0.5.0.
So the question is: what's happen in reality? Is there any logs available?
Can you reproduce it
once more with logs enabled?

> smbnetfs die or just an i/o error happens?

smbnetfs died.

> Okay, I finally got the "transport endpoint is not connected" crash with
> the new version. It happened when I was restarting samba on the server
> while playing an audio file from a samba share.

can you describe it with more details.
can you reproduce it with logging enabled

smbnetfs -d mountpoint | tee smbnetfs.log

> Okay, I finally got the "transport endpoint is not connected" crash with
the new version.

smbnetfs die or just an i/o error happens?

> workstation -> NAS using smbnetfs: 192 hours

already fixed in the latest git

> Is there any chance it will make it into this month's Ubuntu Jaunty
release?

i think, it is not possible. It's too close to release

Okay, I finally got the "transport endpoint is not connected" crash with
the new version. It happened when I was restarting samba on the server
while playing an audio file from a samba share.

No crashes so far with the new version, but there is a worrying speed
problem. I'm testing by copying 3.4 GB of DVD VOB files between my
workstation and my NAS box. Look at these file copy times (as reported by
the xfce file manager):

NAS -> workstation using mount.cifs: 6 minutes
NAS -> workstation using smbnetfs: 6 minutes
workstation -> NAS using mount.cifs: 5 minutes
workstation -> NAS using smbnetfs: 192 hours

I'm testing the new version now. Is there any chance it will make it into
this month's Ubuntu Jaunty release?
https://wiki.ubuntu.com/JauntyReleaseSchedule

please try a new smbnetfs version

git clone git://smbnetfs.git.sourceforge.net/gitroot/smbnetfs
cd smbnetfs
./autogen.sh
./configure
make && make install

having same problem with samba/smbclient > 3.2 ... I am very thankfull to
you kshevetskiy that you are working on it

> I'm reluctant to downgrade libsmbclient just for smbnetfs

hm, what about LD_LIBRARY_PATH magic?

LD_LIBRARY_PATH=dir_with_old_libsmbclient_so:$LD_LIBRARY_PATH smbnetfs
mountpoint

in this case you can place old libsmbclient.so file (and all it's depth)
to some directory out of common library path search. Other program will use
default shared libsmbclient library, but smbnetfs will use the old one

I'm reluctant to downgrade libsmbclient just for smbnetfs, since 23 other
packages on my system depend on it as well. I think I'll wait for your new
version instead.

> I'm using libsmbclient 3.2.3, as distributed with Ubuntu 8.10
(Intrepid).

This is a typical problem with libsmbclient >= 3.2. (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503038 for more details).
Please downgrade libsmbclient version to libsmbclient-3.0.x for now. I
write an announcement here when the newer version of smbnetfs will be
available for testing.

I'm using libsmbclient 3.2.3, as distributed with Ubuntu 8.10 (Intrepid).

I am near the new smbnetfs version. It will require samba>=3.2 and
linux>=2.6.4. This version maybe a little slower then previous but should
be much more stable due to libsmbclient code isolation. Currently i mostly
rework communication with samba (not in subversion yet). If nothing has
changed, the experimental version for testing will be available in the week
or two.

what libsmbclient version do you use?
libsmbclient >= 3.2 is not compatible with smbnetfs, please use
libsmbclient-3.0.x until the issue will be resolved.

Just confirming this.

Output from smbnetfs -d :
READ[145683856] 131072 bytes from 133259264
READ[145683856] 131072 bytes
unique: 1195, error: 0 (Success), outsize: 131088
unique: 1196, opcode: READ (15), nodeid: 119, insize: 80
READ[145683856] 131072 bytes from 133390336
25286->sig_handler: SIGILL or SIGSEGV received
25286->print_backtrace: dumping ...
smbnetfs(print_backtrace+0x4c)[0x804bccc]
smbnetfs(sig_handler+0x36)[0x8054226]
[0xb7f1c400]
/usr/lib/libsmbclient.so.0[0xb7bed28c]
/usr/lib/libsmbclient.so.0[0xb7c0f6b3]
/usr/lib/libsmbclient.so.0[0xb7c0f763]
/usr/lib/libsmbclient.so.0[0xb7b8d1dd]
smbnetfs[0x80537d6]
/usr/lib/libfuse.so.2(fuse_fs_read+0x6e)[0xb7b5e07e]
/usr/lib/libfuse.so.2[0xb7b637da]
/usr/lib/libfuse.so.2[0xb7b677aa]
/usr/lib/libfuse.so.2[0xb7b68211]
/usr/lib/libfuse.so.2(fuse_session_process+0x26)[0xb7b69c06]
/usr/lib/libfuse.so.2[0xb7b65c19]
/lib/i686/cmov/libpthread.so.0[0xb7b444c0]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb7ac361e]

This is the smbnetfs version in debian (lenny)

This might be caused by insufficient locking, as described in these bug
reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503038
https://bugzilla.samba.org/show_bug.cgi?id=5847