On 12/25/12 04:04, Jorge A. Thank you Bart I enable scsi tracing and get hundreds of lines of debug, but after reviewing it, I found this. I try to understand the problem but my capacity around scsi is limited Apparently two READ with same number trigger the problem, anybody have an idea about how correct this or where find more info? Dec 26 09:50:36 stlnx01 kernel: 17829: scstcmdinitdone:354:Receiving CDB: Dec 26 09:50:36 stlnx01 kernel: (h)0123456789ABCDEF Dec 26 09:50:36 stlnx01 kernel: 0: 2a 00 62 8f d0 00 00 00 01 00 00 00 00 00 00 00.b. On 12/26/12 18:36, Jorge A. Arenas Quezada wrote: Right now I am using kernel version 3.6.11 and linux Gentoocould somebody point me in the another combination who is using and working with VMWARE 5? As far as I can see this behavior is not caused by the kernel installed on the system running SCST but it's an initiator configuration issue.

Gento Gpl-2001 Drivers For Macbook Pro

If the storage exported by SCST is used by a single initiator only it should be safe to configure VMware such that it does not send any RESERVE or RELEASE commands. These commands are the commands that trigger the block / unblock messages in the SCST log. Arenas Quezada, on 01:41 PM wrote: I was reading and old post and found something When I was following the guide to install scst on Gentoo I download the released version 2.2.0 but, this file does not include patch for kernel 3.6.11 So, I download the files from SVN Repository, patch kernel and make all modules (scst, scstadm, etc ) from the files in the SVN Well, after reading the old post found something like this ' the scstblockdev and scstunblockdev are normal, Those are the regular debug output. Build the release version and they will disappear.' Alternatively, you can disable mgmtdbg tracing via sysfs tracelevel attribute.

Gento Gpl-2001 Drivers For Mac

On 12/26/12 19:41, Jorge A. Arenas Quezada wrote: Well, after reading the old post found something like this ' the scstblockdev and scstunblockdev are normal, Those are the regular debug output. Build the release version and they will disappear.' This could be my problem? If this is the case.

Could I use the patchs from SVN for my kernel version and compile scst 2.2.0 and all the rest modules from released version? Hello Jorge, In case you didn't know this yet: building a release version means running 'make debug2release' (SCST 2.2) or 'make 2release' (trunk) before building and installing SCST.