found 497572 0.8.7-1.2
tag 497572 +patch
thanks

Adding the -s command line switch helps a lot, and makes the program
usable. However, it doesn't completely resolve the problem. Fusesmb
will still sometimes crash with Transport endpoint is not connected.

To reproduce with -s:
1) Set up ~/.smb/fusesmb.conf to use a remote smb share
2) Install storebackup with apt-get install storebackup
3) fusesmb -s mntpnt
4) cd remotefs/WORKGROUP/RemoteComputerName/ShareName
5) mkdir tmp && cd tmp
6) storeBackup -s ../LargeRemoteDirNameHere -b . -S test

LargeRemoteDirName should have lots of files and take lots of time to
copy. Something like Users on Windows should work fine.

For me, this results in Transport endpoint is not connected about 50%
of the time in about 30 seconds. If it doesn't crash within 2 minutes,
fusermount -u mntpnt and try steps 3-6 again. I've noticed that it's
more likely to crash if steps 3-6 are executed as quickly as possible.
It might help to have the destination directory (tmp in this example)
already created. It might also help to increase storeBackup options
--noCopy and/or --noCompress.

The patch provided by Maciej Babinski, however, works fine. After
patching, I've used fusesmb 7 times, and it's never crashed. I've used
storeBackup to copy files back to the remote machine as well as my
local one.

-Brandon


-- 
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