Topic: backup to windows share - cifs issues

[bradleyj00]

I've been using the SME backup tool, and DAR2 to do a workstation backup to a local windows share. It hasn't worked reliably, and as of late, not at all.

When the backup begins to run, using either application, the following errors show up in the log,

Feb 12 11:51:25 sme e-smith-bg: Connecting /mnt/dar2/backup to \\192.168.10.30\bkp
Feb 12 11:51:25 sme kernel:  CIFS VFS: Send error in SessSetup = -12
Feb 12 11:51:25 sme kernel:  CIFS VFS: cifs_mount failed w/return code = -12
Feb 12 11:51:25 sme e-smith-bg: mount error(12): Cannot allocate memory
Feb 12 11:51:25 sme e-smith-bg: Refer to the mount.cifs( manual page (e.g. man                     mount.cifs)

I know I've done this with SME 7.5 without issue. Just wondering if anyone has any insight? Are there parameters around the windows share that I need to consider? Maybe an update or an  add-on for SME8?  I have noticed some chatter about similar issues on the forum, but I haven't located a solution. Hoping someone can steer me in the right direction.

Thanks,
Jim

[Stefano]

the right direction is bugzilla

file a bug,  thank you

[TerryF]

Have a read here: http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/909a5f0f-73b0-4a52-a594-0d7f80f0c7df/

[bradleyj00]

Thanks everyone for the assistance! That windows registry edit did the trick. Seems to be working fine now.

I will go ahead and submit the bug however.

[purvis]

With the newest update to SME 8 suppoerting SMB 2.
There could be problems bc Microsft has had enough issues to now come out with SMB 2.2.

We are using SMB 1 only.  SME 7 used SMB 1 only.
Maybe it might be better to disable SMB 2 in the Samba service of SME .

[janet]

purvis

Maybe it might be better to disable SMB 2 in the Samba service of SME .

Posting a new feature request (NFR) in bugzilla is the correct way to achieve this.

This is already a bug that generally talks about windows 8 joining a sme server domain etc, FYI

Please create a new bug

[bradleyj00]

Again, many thanks. A bug has been created.

As an update though, even wtih SMB turned off in the windows registry, the backup eventually failed with the following error

Error while saving data: Cannot write down the archive: Error checking for presence of file /mnt/dar2/backup/sme.abc.ca/bkp/2013.02.12.33.dar : Cannot allocate memory.

Maybe physical memory is an issue? I'll experiment with adding more, but I'm fairly certain there's at least 2GB installed.

Alternatively, how would I go about disabling SMB 2 in Samba?

Jim

[TerryF]

Further reading, also added to Bugzilla

http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Seems to be a bit of an issue with large overall transfers and very large single files.

[piran]

My workstation is on W8pro but back in the days when I
had W7pro running on it my notes contain...

Code: [Select]

091029
Oct 29 21:18:06 twiggy kernel:  CIFS VFS: Send error in SessSetup = -12
Oct 29 21:18:06 twiggy kernel:  CIFS VFS: cifs_mount failed w/return code = -12

[Windows 7 registry]
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters\IRPStackSize
...increase to decimal 15 or perhaps 18.
None found.
New DWORD (32bit) with value of decimal 12.

...and the issue, what ever it was, never re-appeared;-)
YMMV

[ see also reference material ]
http://linux.derkeiler.com/Newsgroups/comp.os.linux.networking/2006-10/msg00629.html

[purvis]

also there is a samba setting "max protocol"
you can set the protocol using the line "max protocol = SMB2" in the smb.conf file

for testing, you should be able to open /etc/samba/smb.conf  and place that line in there if it is not there already and needs edititng

then run
/etc/init.d/smb restart

do your testing
to revert back easily

run
expand-templates /etc/smb.conf
/etc/init.d/smb restart

let us know how it goes for you

[CharlieBrady]

let us know how it goes for you

Please ensure that all followup is noted in http://bugs.contribs.org/show_bug.cgi?id=7341

[purvis]

bradleyj00 and others

As of today, the default samba setting in file SMB.conf is SMB version 1 (max protocol = NT1)

[CharlieBrady]

As of today, the default samba setting in file SMB.conf is SMB version 1 (max protocol = NT1)

I suspect that file is not relevant to cifs mounted file systems.

[purvis]

Charlie
I really don't know either.
I was directing the statement to a genera audience that might be reading and to the OP
Who said

Alternatively, how would I go about disabling SMB 2 in Samba?

Being that SME is just now able to use SMB2 with the newest update.
There will be likely many issues popping up connecting to a share off a windows os.
Microsoft has had many issues connecting with in their own windows NT systems.
With that last line said. I do not see how SME users could expect less.

Personally, I don't see a bugs if SME cannot connect to a share on a Windows server or workstation.  A problem for somebody. Yes. Worth knowing and collaboration. Yes

But if you don't have a system to test. Testing SMB connectivity is impossible for SME developers.

[Forman]

Further reading, also added to Bugzilla

http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

Seems to be a bit of an issue with large overall transfers and very large single files.

I know, I'm having to split up large files into smaller ones.