samba - Nov 1999 - smbmount problem after kernel recompile

Hi all,

I am running SuSE 6.2 on a machine with 2 processors, so I just recompiled
the kernel to pick up the second cpu.    

I now have problems using smbmount (2.0.5a that came with distrubution) or
using the newer mount syntax (I just installed 2.0.6) to mount a share from
an NT 4.0 server.  After issuing the smbmount/mount command, and then going
to the mount point, I get i/o errors on the mounted directory, i.e. I
created /mnt/test, and the following:
>cd /mnt/test
>ls 
produces the following error:
"ls: test: Input/output error"

At this point the mount point is in a state of limbo. I can't unmount as I
receive error "device or resource busy".  At this point the only way
to
resolve it is to reboot the server (sounds like NT).  

The other odd thing about all of this is that everything else seems to work
just fine.  I can use smbclient to talk to the same NT share and the local
host just fine.  I haven't tried to map a drive from an NT workstation to
the linux server yet, but I'm going to guess that works fine also.

There is a note in the SuSE support db regarding recompiling of kernel for
smp support that mentions some modules may need to be recompiled because
"single processor modules will not work with an smp kernel".  I'm
wondering
if that maybe the smb module is one of those.  I've looked at the config
file I used to recompile the kernel and it shows smb support is a module,
not compiled into the kernel.    

At this point I'll admit that I'm a little lost.  Is there a module I
need
to recompile to fix the mount problems, and if so, which one, and how.  I
think I kind of know how to recompile a module, I'm just not sure which one
and where to find the source.  OR...is there some other problem?

I'd appreciate any help....

Thanks,
Cary Mader
cary.mader@eds.com



Cary Mader     /  Phoenix Dev Center
602-770-0241   /  cary.mader@eds.com

Email Text Messages (100 characters)
6027700241@messaging.sprintpcs.com

On Sat, 13 Nov 1999, Mader, Cary J wrote:
> to the mount point, I get i/o errors on the mounted directory, i.e. I
> created /mnt/test, and the following:
> >cd /mnt/test
> >ls 
> produces the following error:
> "ls: test: Input/output error"
Do you get any funny messages in the syslog?
> At this point the mount point is in a state of limbo. I can't unmount
as I
> receive error "device or resource busy".  At this point the only
way to
> resolve it is to reboot the server (sounds like NT).  
It could very well be that the smbfs part has "crashed" (because of
up/smp
differences), something that normally gives you a BSOD on NT, I think ...
> The other odd thing about all of this is that everything else seems to work
> just fine.  I can use smbclient to talk to the same NT share and the local
> host just fine.  I haven't tried to map a drive from an NT workstation
to
> the linux server yet, but I'm going to guess that works fine also.
Those are userspace things, and they only require the kernel to give them
a network connection.
> There is a note in the SuSE support db regarding recompiling of kernel for
> smp support that mentions some modules may need to be recompiled because
> "single processor modules will not work with an smp kernel". 
I'm wondering
                            ^^^^^^^^
If they say so. Sounds like a very good idea to me.
> At this point I'll admit that I'm a little lost.  Is there a module
I need
> to recompile to fix the mount problems, and if so, which one, and how.  I
> think I kind of know how to recompile a module, I'm just not sure which
one
> and where to find the source.  OR...is there some other problem?
You should probably recompile all your modules. As I don't know SuSE I
don't know if they have made any changes to this but if you had the normal
kernel tree you do:

% make modules modules_install

Wherever your kernel sourcetree lives (the same place where you'd
otherwise do 'make bzImage'), smbfs is included in the normal kernel
sources.

I'd suggest you then remove any modules you have loaded with rmmod
(possibly by rebooting, if all else fails) before testing your new smbfs
module, to make sure that you are using your new modules and not your old.

/Urban