smbnetfs stopped working

syre · 2010-03-08 15:47:02

hey archers

today i couldn't access my server and its shares with smbnetfs,
when trying to execute smbnetfs with sudo /etc/rc.d/smbnetfs start/restart it just fails, can you give me any clues to what might be the problem?

perbh · 2010-03-08 15:58:07

smbnetfs??
Are we talking about archlinux?
You _may_ have installed something that I don't have (and I do have samba), but I surely do not have any /etc/rc.d/smbnetfs

syre · 2010-03-08 16:05:47

http://wiki.archlinux.org/index.php/Samba#smbnetfs
i've checked some of my logs and i couldn't find anything.
Is there one specific log that could provide me with more information?

syre · 2010-03-08 16:09:57

i should probably state that mounting with the regular mount command works fine.

perbh · 2010-03-08 16:37:24

Oh ok - my fault ... I had just never come across or used it.
Personally I just use smb.conf and that works a treat.

syre · 2010-03-08 16:41:36

but smbnetfs is a tool for automounting samba shares, isn't smb.conf just a config file for samba?, i fail to see the similarity

perbh · 2010-03-08 16:54:33

*lol* Guilty as charged! (pulling the downie back over my head)
Sorry I spoke without thinking!

Yes you are right - but what I usually do is to have the entry in /etc/fstab with 'noauto' and then either mounting manually or using /etc/rc.local ... never had the need for any smbnetfs

Seeing you can mount manually, I presume you can also do it in /etc/rc.local - the advantage being that it gets mounted very late in the boot-sequence ...

syre · 2010-03-08 17:06:10

although it's not a solution to the problem, maybe you're right.
maybe i should follow your advice and just try adding the mounts to my rc.local, after all it's more KISS

rent0n · 2010-03-08 17:16:01

Just switched today from mounting a network folder with fstab and cifs to mount the whole network with smbnetfs.
Works fine here. You may want to check the wiki as I've added some useful information about authentication and permissions: http://wiki.archlinux.org/index.php/Samba#smbnetfs

syre · 2010-03-08 17:25:52

my shares require no authentication, tried changing the permissions, still no luck

rent0n · 2010-03-08 18:42:52

Ok, time for random order ideas...

1. Did your problem arise after some particular upgrade? Which packages where upgraded?
2. Is netfs daemon loaded at startup? smbnetfs also fails at startup?
3. Is fuse module loaded?

lsmod | grep fuse

4. Can you ping or access with smbclient the PCs of the network?

ping 192.168.xxx.xxx
smbclient -L 192.169.xxx.xxx

5. Post your /etc/fuse.conf
6. **WARNING: UNTESTED AND POTENTIALLY DANGEROUS!** If you want to get some logs, you may try to remove the redirections to /dev/null in /etc/rc.d/smbnetfs and look at the output of:

# /etc/rc.d/smbnetfs restart

Random ideas over...good luck!

syre · 2010-03-08 21:04:39

rent0n wrote:

1. Did your problem arise after some particular upgrade? Which packages where upgraded?

could've been i'm not sure

2. Is netfs daemon loaded at startup? smbnetfs also fails at startup?

the netfs daemon is loaded yes, and before smbnetfs aswell.
apparently smbnetfs doesn't fail at startup

3. Is fuse module loaded?

lsmod | grep fuse
fuse      58757  2

4. Can you ping or access with smbclient the PCs of the network?

ping 192.168.xxx.xxx
smbclient -L 192.169.xxx.xxx

pinging my server works fine, however smbclient -L <serverip> returns:

creating lame upcase table
creating lame lowcase table
params.c:OpenConfFile() - Unable to open configuration file "/etc/samba/smb.conf":
    No such file or directory
smbclient: Can't load /etc/samba/smb.conf - run testparm to debug it
Enter user's password: 
Domain=[SAMBA] OS=[Unix] Server=[Samba 3.5.0]
Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled
Segmentation fault

it doesn't look too good

5. Post your /etc/fuse.conf

only thing uncommented is user_allow_other

samhain · 2010-03-10 19:32:43

Exactly same problem here.

I use smbnetfs with pcmanfm to access samba shares on my arch server. It stopped working after last system upgrade.

Maybe the upgrade from samba 3.4.6 to 3.5.0 broke it.

Respen · 2010-03-19 01:45:21

I am pretty sure that the upgrade from samba 3.4 to 3.5 broke it. I get the same problems as well as the LANMAN error and segmentation fault. I got those errors when trying to connect to my own machine's server with smbclient, and smbnetfs just gives an IO error. Also, a Windows machine can connect to my server's share just fine.

I tried to enter the lanman fix on the Samba wiki page, smbnetfs section, into smb.conf. However, there is still a segmentation fault. Then I tried downgrading samba and smbclient from 3.5 to 3.4. That allowed me to access my server's share through smbclient, but smbnetfs fails to start.

I am guessing there are some things wrong with the current packages working with each other. I suppose we will have to wait until there are new versions available. Until then, I suppose I will have to mount each share that I want individually.:(

Cynical · 2010-03-19 14:09:50

Well thats strange. I'm not quite sure what problem you guys are having but I just upgraded to samba 3.5 and the command "smbnetfs /mnt/path" does exactly what I expect it to... although I will mention that I can't seem to get it to run on startup like it used to. Anyone know how to specify a default mount point? I looked through the config file but the option doesn't exist. It's not a huge deal but it would make things more simple.

Respen · 2010-03-19 17:41:09

I do not know how to change the default mount point for smbnetfs, but if it can be done I would assume it is an option in a config file.

Okay, I have done a bit more experimenting and successfully got it working again. However, I had to downgrade to 3.4 for samba and smbclient. Once you downgrade you will need to restart the netfs, samba, and smbnetfs daemons, in that order.

I am not sure what changed in 3.5 that broke my setup. I am using share-level security to provide open, read only access to the share. That is all, although I can post my smb.conf if any of you want it.

The problem is that after upgrading to version 3.5 of samba and smbclient, smbclient and smbnetfs will not connect properly to my share. When trying to browse into the share through the smbnetfs-mounted filesystem (whether through a file browser or terminal), it gives an IO error. When trying to connect to the share with smbclient using the command

smbclient //server/share

a segmentation fault occurs. However, mounting the share using this command:

mount -t cifs \\\\[server's network address]\\[share name] [mount point]

allows normal browsing of the share.

Is there something I need to change in my settings to get 3.5 to work properly? Or is it a bug?

Cynical · 2010-04-15 01:54:33

My smb.conf looks like this,

[global]
workgroup = WORKGROUP
server string =
netbios name = hostname
security = user
guest account = username

[public]
comment = Public Share
path = /home/username/public
writable = yes
available = yes
browsable = yes
public = yes

Arch Linux

#1 2010-03-08 15:47:02

smbnetfs stopped working

#2 2010-03-08 15:58:07

Re: smbnetfs stopped working

#3 2010-03-08 16:05:47

Re: smbnetfs stopped working

#4 2010-03-08 16:09:57

Re: smbnetfs stopped working

#5 2010-03-08 16:37:24

Re: smbnetfs stopped working

#6 2010-03-08 16:41:36

Re: smbnetfs stopped working

#7 2010-03-08 16:54:33

Re: smbnetfs stopped working

#8 2010-03-08 17:06:10

Re: smbnetfs stopped working

#9 2010-03-08 17:16:01

Re: smbnetfs stopped working

#10 2010-03-08 17:25:52

Re: smbnetfs stopped working

#11 2010-03-08 18:42:52

Re: smbnetfs stopped working

#12 2010-03-08 21:04:39

Re: smbnetfs stopped working

#13 2010-03-10 19:32:43

Re: smbnetfs stopped working

#14 2010-03-19 01:45:21

Re: smbnetfs stopped working

#15 2010-03-19 14:09:50

Re: smbnetfs stopped working

#16 2010-03-19 17:41:09

Re: smbnetfs stopped working

#17 2010-04-15 01:54:33

Re: smbnetfs stopped working

Board footer