11-04-2013 02:48 AM
I built a BL860c I2 with VMS 8.4 and the latest patch release of Samba/CIFS last week. Customer is using the blade as storage for a code management system (Borland StarTeam) which has been using an existing Alpha cluster for years.
For code checkout they are using the 'use last modified date for files' which on Alpha VMS 7.1 sets both the created and modified date to be the last modified date of the file. On V8.4 it does 2 things wrong - firstly it only sets the modified date and more importantly it crashes with an I/O error on every 102nd file and logs 'sys$get_security failed'
This is on Win7. XP is fine!
This is 100% reproduceable, anyone else seen it before?
Solved! Go to Solution.
11-05-2013 08:41 AM
No I haven't seen this particular crash and I like to think we are a moderate to heavy CIFS/Samba usage site, however, all using Windows XP. Could you reproduce the crash with regular DOS commands or do you need StarTeam? Can you describe exactly how?
We have seen other problems, of course.
When we do see something, we log a call and get great support from HP, invariably, from Paul Nunez at HP. Do you have a support contract? I suggest logging a call.
A new patch kit just came out (10-OCT-2013), are you at the very latest version (from $ SMBVER - V1.2-010-PS2_11) ?
I've noticed various differences if the "backing store" of the share is hosted on a ODS-2 versus ODS-5 disk. You may want to try an ODS-5 disk and see if the date issue behaves differently.
Did you mean to say that both issues don't occur if the client is Win XP but does if the PC is running Windows 7? We haven't done very extensive testing with Windows 7 but did discover we needed to add the "server signing = auto" to the SMB.CONF to even allow Windows 7 clients to connect...
11-05-2013 09:01 AM
Yes, it's only Win7 that has the problem - XP is happy and will quite happily change the modified date on 1000+ files. Win7 will get an I/O error every time at 102 files so I guess I could write a batch file to do similar to rule out StarTeam as a possible cause.
I did wonder if it was an ODS/2 issue so I changed all shared drives to be ODS/5, still no difference.
Fairly sure it is that latest patch level. In searching for answers to another problem I had during install I found a link to ftp.hp.com which had everything CIFS in it, pretty sure that was after 10th Oct.
11-06-2013 05:40 AM
$ ftp ftp.usa.hp.com
Unzip the zip file and refer to the instructions in the txt file.
Note: You only need to reboot if you have to increase the SYSGEN CHANNELCNT parameter.