RE: [Iometer-user] RE: Iometer Error w/ 2004.07.30 and FibreChannel SAN Head

[Vedran D. <ve...@ya...>]

Bo,

Sorry if I missed it, but what platform is dynamo running on. And does this
reproduce on others?

Ved
--- BO MOON <bm...@an...> wrote:

> Do we have any clue or solution on this issue?
> I have a same problem.
> 
> Thanks,
> 
> Bo
> 
> -----Original Message-----
> From: iom...@li...
> [mailto:iom...@li...] On Behalf Of Gruher,
> Joseph R
> Sent: Monday, November 22, 2004 12:02 PM
> To: mi...@el...
> Cc: iometer-devel-list; iometer-user-list
> Subject: RE: [Iometer-user] RE: Iometer Error w/ 2004.07.30 and
> FibreChannel SAN Head
> 
> Possibly, but they at least coincide with the failure.  After I get the
> failure from the GUI once it will appear every time I try to initiate a
> test run, until I close and reopen Iometer/Dynamo, so I can reproduce it
> quickly.  Every time the failure occurs these messages appear in Dynamo.
> 
> -J
> 
> -----Original Message-----
> From: Ming Zhang [mailto:mi...@el...] 
> Sent: Monday, November 22, 2004 11:38 AM
> To: Gruher, Joseph R
> Cc: iometer-devel-list; iometer-user-list
> Subject: Re: [Iometer-user] RE: Iometer Error w/ 2004.07.30 and
> FibreChannel SAN Head
> 
> I think these msg are not error msg.
> 
> On Mon, 2004-11-22 at 13:45, Gruher, Joseph R wrote:
> > Update:
> > 
> >  
> > 
> > I have now also seen the test fail during a 64k workload with the
> > following message:
> > 
> >  
> > 
> > Worker 0 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 65536, returning
> > 
> > Worker 1 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 65536, returning
> > 
> > Worker 2 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 65536, returning
> > 
> > Worker 3 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 65536, returning
> > 
> > Worker 0 setting targets...
> > 
> >  
> > 
> >  
> > 
> >                                    
> > ______________________________________________________________________
> > 
> > From: Gruher, Joseph R 
> > Sent: Monday, November 22, 2004 9:25 AM
> > To: 'iom...@li...';
> > 'iom...@li...'
> > Cc: Gruher, Joseph R
> > Subject: Iometer Error w/ 2004.07.30 and Fibre Channel SAN Head
> > 
> > 
> >  
> > 
> > All-
> > 
> >  
> > 
> > I am running Iometer from four identical dual Xeon clients against a
> > SAN Head enclosure.  I have four 100 GB volumes configured on the SAN
> > Head and each client targets four workers at one volume.  When I run
> > Iometer it runs normally for a few minutes (although my maximum IO
> > response times are higher than expected) and then I get the following
> > error message in the GUI:
> > 
> >  
> > 
> > "Testing encountered an error and is unable to continue.  See Dynamo
> > output for additional error messages."
> > 
> >  
> > 
> > When I refer to the Dynamo window, I see the following output:
> > 
> >  
> > 
> > Worker 0 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 8192, returning
> > 
> > Worker 1 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 8192, returning
> > 
> > Worker 2 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 8192, returning
> > 
> > Worker 3 running Access Spec: 8k Seq Write
> > 
> > Access specifications for test defined.
> > 
> > Grunt: Grunt data buffer size 65536 >= 8192, returning
> > 
> > Worker 0 setting targets...
> > 
> >  
> > 
> > What does this error mean?  How can I address it?  I'm wondering if my
> > IO response times are so long that Iometer has moved to the next
> > workload but then gets a response from the previous workload, causing
> > an error.  The workload run prior to the one where I encountered the
> > error was a 64k workload.
> > 
> >  
> > 
> > Thanks,
> > 
> > Joe
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Iometer-user mailing list
> Iom...@li...
> https://lists.sourceforge.net/lists/listinfo/iometer-user
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Iometer-user mailing list
> Iom...@li...
> https://lists.sourceforge.net/lists/listinfo/iometer-user
> 



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250