[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssag::ask_ssag

Title:Ask the Storage Architecture Group
Notice:Check out our web page at http://www-starch.shr.dec.com
Moderator:SSAG::TERZAN
Created:Wed Oct 15 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6756
Total number of notes:25276

5827.0. "RZ28D problem on HSJ40 subsystem 'Target shall not report GOOD status on write cmds until data is written'" by MOOZY::HAVERFIELDP (Paul Haverfield@CAO) Wed Jul 24 1996 01:10

T.RTitleUserPersonal
Name
DateLines
5827.1hmmm,,,BABAGI::VIDIOT::PATENAUDEAsk your boss for ARRAY's...Wed Jul 24 1996 11:0710
5827.2Let's rephrase the questionGIDDAY::BENBROOKBrisbane ruLesMon Feb 17 1997 20:1135
	  I think the real question is in the title of this note.  I have
	re-asked the question in Note 6402 - look there for (hopefully) an
	answer if you are having this symptom.

	  The answer (.1) was quite correct as the samples given all said
	"RECOVERED ERROR" - and we certainly should not be changing disks.

	  But the title says "Target shall not report GOOD status ... "
	and the unanswered question (perhaps UN-ASKED too) is "Just what
	meaning is conveyed with that line in Errorlog ?"    Is it an error,
	or is it simply Informational ?

	  Because, in English, it CAN be mis-interpreted !!!!   

It could mean:-

	1.  Target shall (SHOULD) not report good status until data is written

		This infers that we have a problem

	2.  Target shall (WILL) not report good status until data is written

		This infers that it is simply the way the disk is set up,
		and is NOT a problem.


	  I'm hopeful that .1's author (or someone equally knowledgeable)
	will clarify this for others who have customers reading "problem"
	when they see this in Errorlog.

	Look in Note 6402 - ...... fingers crossed !!!

Les Benbrook

5827.3notes collision.SUBSYS::VIDIOT::PATENAUDEAsk your boss for ARRAY's...Tue Feb 18 1997 07:411
I replied in 6402.1