SMBNetFS Activity
Status: Beta
Brought to you by:
kshevetskiy
Activity for SMBNetFS
-
Brunetton posted a comment on ticket #3
Good question. I'd like to know too. This is very strange
-
joachim-f modified a comment on ticket #35
I noticed the same issue if I try to write to a Windows share via smbnetfs in the way you described. Have you found a solution? I have created a question on SO => https://stackoverflow.com/questions/73104395/smbnetfs-how-to-resolve-input-output-error-while-writing-file-to-windows-serve
-
I noticed the same issue if I try to write to a Windows share via smbnetfs in the way you described. Have you found a solution? => https://stackoverflow.com/questions/73104395/smbnetfs-how-to-resolve-input-output-error-while-writing-file-to-windows-serve
-
I noticed the same issue if I try to write to a Windows share via smbnetfs in the way you described. Have you found a solution?
-
Jocelyn Viau posted a comment on ticket #51
Last line should say ls: cannot access 'test': Invalid argument
-
Group is not applied to hosts
-
Mikhail T. created ticket #50
Cannot write with 0.6.3
-
stat seems to have become much slower in 0.6.3
-
Tried 0.6.3 today. The lines are now counted correctly -- tail, actually, outputs 10 lines. But the -f flag is ineffective -- although the file continues to grow on the server, and clients accessing the server via NFS see the growth -- my FreeBSD client using smbnetfs does not detect the changes. Not until I restart tail.
-
Mikhail Kshevetskiy posted a comment on ticket #10
This output is not full. It seems to me you miss '-d' option so smbnetfs become a daemon process and the rest of output was not printed. what I need (in short) 1) enable debug output 2) do actions to get an error 3) send me whole debug output (better with the commands from step 2) by email (the output will be quite large There are 2 ways to enable debug output 1) run smbnetfs with options smbnetfs -d -o smbnetfs_debug=7 mountpoint | tee -o smbnetfs.log smbnetfs -d -o smbnetfs_debug=7,smb_query_browsers=false...
-
Here is the recommendation from the ENGLISH.FAQ Q5: I have a problem, what should I do ? A5: It's quite often that the cause of errors is the samba and/or SMBNetFS misconfiguration. To understand the cause of the error, set the value of “smbnetfs_debug” to 5, 6 or 7 (also it maybe useful to setup “smb_query_browsers” to false) and run “smbnetfs” with an additional option "-d". Repeat your steps to reproduce the error. Examine the debug information and try to fix the error by yourself. If it does...
-
return back INSTALL file as a link to doc/INSTALL
-
apply debian mentor changes
-
update debian build rules
-
SMBNetFS released /smbnetfs/SMBNetFS-0.6.3/smbnetfs-0.6.3.txt
-
-
add debian building rules
-
I have no test environment now. The only possible testing is localhost :-(
-
try 0.6.2, probably the problem was fixed
-
could you try 0.6.2 ?
-
Elke Hofmann created ticket #10
I/O Exceptions with Windows shares from version 0.6.1
-
Lantizia created ticket #9
Input/output error - possible locking issues with Windows Servers?
-
-
-
Tail is not working right...
-
smbnetfs may return wrong subsecond value in times
-
bump version and update changelog
-
fix opening a file with O_CREAT and reading created files
-
add noexec option support
-
smbnetfs is slow because of libsecret
-
that was caused by missprint. now it fixed
-
fix misprint that caused #47 (smbnetfs is slow because of libsecret)
-
probably fixed in upstream
-
probably fix #46 smbnetfs may return wrong subsecond value in times
-
check /etc/samba/smb.conf or ~/.smb/smb.conf file.
-
hm, you have no smbclient.pc file et all?
-
clang complains about crash-triggering hack in list.h
-
attr/xattr.h is a Linux only "thing"
-
use __builtin_trap() instead of NULL pointer dereference, thanks to Mikhail T.
-
not needed under linux anymore, so just removed.
-
fix #38 attr/xattr.h is a Linux only thing
-
fix warning
-
Andrey Bondarenko created ticket #47
smbnetfs is slow because of libsecret
-
Reported Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/smbnetfs/+bug/1811353 with dirty patch that works for me.
-
smbnetfs may return wrong subsecond value in times
-
georg created ticket #45
mountpoint empty (although shares are shown in smbtree)
-
Trevor Hodges posted a comment on ticket #8
I was able to resolve this issue by installing FUSE 2.9 rather than 3.2.4.
-
Configure fails despite FUSE instaled
-
strarsis created ticket #44
Specify port
-
Porting to libfuse-3.x
-
Sorry, the 398e8169ea6d3d854af0173b1e66bf13c124f901 is not a fix -- there is no sys/xattr.h on FreeBSD either. If you think, the include is necessary at all -- have you tried compiling without it? -- then it should be protected by #ifdef __linux__, I think...
-
I used FreeBSD-11.1, but the iconv_open and friends are found in libc on FreeBSD-10.x as well -- not sure about 9.x, because I don't have any around.
-
There is no /opt/lib/samba4/lib/pkgconfig on my system, but invoking pkgconf --libs smbclient outputs the correct information without any special hacks. At any rate, the SMBCLIENT_LIBS should work to overwrite whatever pkgconf outputs, should not it? And it does not -- not quite...
-
Tried setting max_rw_block_size to 4194304 and then to 41943040 -- the performance dropped back down to mere hundreds of KB per second, direct_io or not.
-
What FreeBSD version is used?
-
You should use pkg-config for this task. Try something like PKG_CONFIG_PATH=/opt/lib/samba4/lib/pkgconfig:$PKG_CONFIG_PATH ./configure
-
probably fixed
-
use proper xattr
-
[Mikhail T] Fix warnings, add const-ness, reduce calls to time()
-
SMBNetFS isolate samba communication in separate process, so shared memory used to avoid data coping to/from child process. Try increaseasing shared memory size from 128Kb to some large value. See max_rw_block_size config option
-
By adding direct_io flag to the list of options of mount_fusefs, I was able to raise the throughput to 5-8 megabytes per second depending on the reader's options. Although a spectacular gain, this is still far below the 20MB/s reported by smbclient...
-
FWIW, I tried redefining the COMM_BUF_SIZE from 4096 to 16384, and even to 65536 -- but the throughput did not improve at all... Please, help.
-
smb_conn_no_reply -- empty, unused, but triggers a compiler warning
-
configure ignores SMBCLIENT_LIBS-variable
-
Very SLOW reads
-
FreeBSD has iconv-functions in libc
-
there is need to link Make that there is no need... Sorry...
-
No need to link with -lglib
-
clang complains about crash-triggering hack in list.h
-
attr/xattr.h is a Linux only "thing"
-
I was having the same problem and found this ticket with Google. The work-around I found is to put one of the options you'd like to pass to smbnetfs into the first column of the fstab-entry. For example, here is, what I have: -obig_writes /smb fusefs rw,failok,uid=101,late,mountprog=/opt/bin/smbnetfs (/opt is what I have for $LOCALBASE -- you, likely, have /usr/local). This works because the first field is passed by mount_fusefs to the specified program verbatim -- after the options. So the above...
-
-
-
fix username selection
-
strndup() is required now
-
replace deprecated gnome-keyring with libsecret
-
setxattr() is required now
-
use dprintf()/vdprintf() to print debug messages
-
I am having the same problem and found this ticket with Google. The work-around I found is to put one of the options you'd like to pass to smbnetfs into the first column of the fstab-entry. For example, here is, what I have: -obig_writes /smb fusefs rw,failok,uid=101,late,mountprog=/opt/bin/smbnetfs (/opt is what I have for $LOCALBASE -- you, likely, have /usr/local). This works because the first field is passed by mount_fusefs to the specified program verbatim -- after the options. So the above...
-
I am having the same problem and found this ticket with Google. The work-around I found is to put one of the options you'd like to pass to smbnetfs into the first column of the fstab-entry. For example, here is, what I have: -obig_writes /smb fusefs rw,failok,uid=101,late,mountprog=/opt/bin/smbnetfs (/opt is what I have for $LOCALBASE -- you, likely, have /usr/local). This works because the first field is passed by mount_fusefs to the specified program verbatim -- after the options. So the above...
-
FERNANDO created ticket #6
input/output error copying and pasting documents in shared folders
-
Mathias H modified a comment on ticket #37
I forgot to mention, the usual Linux formatting for Linux boxes in fstab does not work in FreeBSD and throws the errors mentioned. https://sourceforge.net/p/smbnetfs/bugs/28/ Addresses this very issue and it was set to invalid. I can confirm application of the patch resolves this issue.
-
https://sourceforge.net/p/smbnetfs/bugs/28/ Addresses this very issue and it was set to invalid.
-
FreeBSD 10.3-STABLE - fstab formatting
-
drop old libsmbclient support, libsmbclient >= ...
-
Laurent Riffard created ticket #36
EBusy when deleting open file
-
Mat. created ticket #35
Azure File Service can only be used readonly
-
Max created ticket #11
XDG spec support
-
Mark Nuzzolilo created ticket #34
CMake hangs when running with a smbnetfs target destination
-
AMDanischewski created ticket #5
Very slow in creating remote archive
-
Lomedhi posted a comment on ticket #4
Never mind, I just got it working! Thanks for this tool, and please close this t...
-
Basic usage example
-
SMBNetFS uses libsmbclient library to work with samba networks. libsmbclient library...
-
Jonathan Liu posted a comment on ticket #33
The behavior is different from mount.cifs which shows '@' as expected in the folder...
-
This is an expected behavior. The '@' symbol is used as a divider to split user/password...
-
I have the following in smbnetfs.conf: local_charset "utf-8" samba_charset "utf-...
-
@ symbol in folder name shown as %40
-
Milan Knizek created ticket #3
What is the need of a complete smb.conf in user's HOME dir?
1 >
