sslug-teknik team mailing list archive

[Palle Arentoft <pa@xxxxxxxxxxx>]

På IBMs hjemmeside kan man finde følgende:
Symptom 
Operating System hangs or traps running with ServeRAID 3L 
Affected configurations 
The following combination of ServeRAID options must be present: 64k block
size with Write Back Cache enabled on the Logical Drive. 

The system is any of the following IBM Netfinity or PC servers: 
*	a Netfinity 7000-M10 server, Type 8680, any Model. 
*	a Netfinity 7000 server, Type 8651, any Model. 
*	a Netfinity 5500-M20 server, Type 8662, any Model. 
*	a Netfinity 5500-M10 server, Type 8661, any Model. 
*	a Netfinity 5500 server, Type 8660, any Model. 
*	a Netfinity 5000 server, Type 8659, any Model. 
*	a Netfinity 3500 server, Type 8644, any Model. 
*	a Netfinity 3500-M10 server, Type 8655, any Model. 
*	a Netfinity 3000 server, Type 8476, any Model. 
*	a Netfinity 1000 server, Type 8477, any Model. 
*	a PC Server 704, Type 8650, any Model. 
*	a PC Server 330, Type 8640, any Model. 
*	a PC Server 325, Type 8639, any Model. 

The Firmware level affected is ServeRAID package 3.50 

NOS affected: 
*	Banyan 
*	Citrix 
*	Linux 
*	OS/2 
*	NetWare 
*	Windows NT 
*	UnixWare 
*	OpenServer 
Solution 
A fix will be forthcoming in the next ServeRAID code release. This will
occur in 4th quarter 99. 
If you are running a ServeRAID 3L with Write Back enabled and 64k Logical
Block Size, change the cache setting to Write Through. Otherwise, do not
create logical drives with a block size of 64k. 
Details 
Once the block size is set with the creation of the array, it cannot be
changed without losing data. If customers need to run in Write Back mode,
they will need to back up data, recreate arrays and logical drives, and then
restore the data. 

Mvh

Palle