>
> I mount a few shared window$ drives at start up via fstab as
>
>
> Code:
> --------------------
> //geirfugl/smidja$ /home/XXXX/smidja cifs
credentials=/home/XXXX/.smbpasswd,uid=XXXX,gid=users 0 0
> --------------------
>
>
> When I was digging through /var/log/messages looking for something
> completely different, I found a bunch of these …
>
>> Aug 11 09:48:42 nattfari kernel: [174919.476344] CIFS VFS: Unexpected
>> SMB signature
>
> Is this something to worry about? Is it some sort of a kernel bug?
>
> Currently I’m running an 11.4 with Gnome (2.32.1) and
<snip>
plesset;
It seems there is a problem with smb signing and large writes. You might try
adding the option:
wsize = 16384
to the mount command. This should keep the writes smaller than where the bug
occurs.
I have not duplicated the error so this is a bit of speculation on my part.
However, as long as there is no degradation in performance I would not be
overly concerned.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
In fact there is a serious performance degradation. From my OpenSuse 11.4 partition I’m able to read/write at about 9 Mb/s (average value) from/to my common windows file server. Booting from a windows 7 partition on the same machine the rate of transfer is 10x.
I have found a few references to this issuse on various forums and chats, but no real solution. All signs hint at a difficulty with the kernel so I wonder if it would be better to upgrade or downgrade my kernel ( 2.6.37.6-0.7-desktop as is )?
>
> In fact there is a serious performance degradation. From my OpenSuse
> 11.4 partition I’m able to read/write at about 9 Mb/s (average value)
> from/to my common windows file server. Booting from a windows 7
> partition on the same machine the rate of transfer is 10x.
>
> I have found a few references to this issuse on various forums and
> chats, but no real solution. All signs hint at a difficulty with the
> kernel so I wonder if it would be better to upgrade or downgrade my
> kernel ( 2.6.37.6-0.7-desktop as is )?
>
plesset;
Ok, I’m not sure how to do this properly but I found the solution in a different thread … CIFS writing error in 11.4 .
Step 1 – alter apparmor
go to Yast → apparmor and enter the Control Panel → configure profiles area. Highlight usr.sbin.smbd and use the ToggleMode button to flip it to “complain” Similarly flip usr.sbin.nmbd to “complain”. Click Done to exit.
Step 2 – turn on Samba daemons
Go to Yast → system → runlevels. (a) Highlight nmb and make sure the setting is = yes (use the Enable button). (b) Highlight smb and make sure the setting is = yes (use the Enable button). (c) Highlight cifs and make sure the setting is = yes (use the Enable button).
Step 3: test again the command: su -c “rcnmb status;rcsmb status”
Should be good now, tell us if it isn’t
>
> Ok, I’m not sure how to do this properly but I found the solution in a
> different thread … ‘CIFS writing error in 11.4’
> (http://tinyurl.com/44ryhkq) .
>
>>
>> Step 1 – alter apparmor
>> go to Yast → apparmor and enter the Control Panel → configure
>> profiles area. Highlight usr.sbin.smbd and use the ToggleMode button to
>> flip it to “complain” Similarly flip usr.sbin.nmbd to “complain”. Click
>> Done to exit.
>>
>> Step 2 – turn on Samba daemons
>> Go to Yast → system → runlevels. (a) Highlight nmb and make sure
>> the setting is = yes (use the Enable button). (b) Highlight smb and make
>> sure the setting is = yes (use the Enable button). (c) Highlight cifs
>> and make sure the setting is = yes (use the Enable button).
>>
>> Step 3: test again the command: su -c “rcnmb status;rcsmb status”
>> Should be good now, tell us if it isn’t
>>
>> Step 4: reboot
>>
>
>
>
> Thanks to user Swerdna ( ‘openSUSE SuSE Linux HOWTOs and Tutorials by
> Swerdna’ (http://opensuse.swerdna.org/))
>
Plesset;
Glad to see it’s solved. I was under the impression that the apparmor problem
had been fixed in an update subsequent to the release of 11.4.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Actually I’m going to take a closer look tomorrow (after I sober up). I noticed that the cifsd was set to be off in the runlevel panel so I wonder if all the AppArmor & nmbd/smbd adjustments where necessary as well. On my 11.3, the cifsd is on (and not nmbd/smbd) and I have had no problems (with this particular issuse).
>
> venzkep;2379740 Wrote:
<snip>
>>
>> Glad to see it’s solved. I was under the impression that the apparmor
>> problem
>> had been fixed in an update subsequent to the release of 11.4.
>> –
>> P. V.
>> “We’re all in this together, I’m pulling for you.” Red Green
>
>
> Actually I’m going to take a closer look tomorrow (after I sober up). I
> noticed that the cifsd was set to be off in the runlevel panel so I
> wonder if all the AppArmor & nmbd/smbd adjustments where necessary as
> well. On my 11.3, the cifsd is on (and not nmbd/smbd) and I have had no
> problems (with this particular issuse).
>
Plesset;
You do need nmbd running for the resolution of netbios names. For a cifs mount
you would want to add:
wins
to the hosts line of /etc/nsswitch.conf. You should also adjust the name
resolve parameter in the [Global] section of /etc/samba/smb.conf to something
like:
#with no wins server on the network
name resolve order = bcast host lmhosts wins
#with a wins server on the network
name resolve order = wins host lmhosts bcast
wins server = <IP of your wins server>
NOTE: If the machine you are configuring is also the wins server do NOT use
the “wins server” parameter! The wins server parameter is ONLY used when
another (different) machine is the wins server.
The default value for the name resolve parameter has lmhosts first with bcast
last and is, in my opinion, not very useful. If your smb.conf does not
contain this parameter you are using the default and the name resolve parameter
should probably be added as shown above.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green