From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicholas Henke <nic@cray.com>
Date: Thu, 16 Jul 2009 16:20:25 -0500
Subject: [Lustre-devel] Testing LNET
In-Reply-To: <9A79889B-CA4B-43E7-9824-79A1F7949AFE@myri.com>
References: <9A79889B-CA4B-43E7-9824-79A1F7949AFE@myri.com>
Message-ID: <4A5F9999.2040302@cray.com>
List-Id: <lustre-devel-lustre.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lustre-devel@lists.lustre.org

Scott Atchley wrote:
> Hi all,
>
> I have implemented handling of hosts with different PAGE_SIZE in  
> MXLND. I am running tests to make sure that I did not accidentally  
> break something else. So far, I have been using lctl and pinging back  
> and forth as well as with obdecho (using loadgen).
>
> When running loadgen tests or lctl test_brw with loadgen's echosrv  
> running, if I kill a host (either client or server) and bring it back  
> up, LNET seems happy (MXLND reconnects normally), but loadgen does not  
> resume. When using lctl test_brw and I restart a server, the client  
> reconnects but then fails an assertion when it connects to a new  
> server with:
>
> LustreError: 6295:0:(echo_client.c:1341:echo_client_cleanup())  
> ASSERTION(eco->eco_refcount == 0) failed
>
> If this the proper way to test a LND? What other methods can you  
> suggest?
>   

I've been using LNet SelfTest for my LND development and testing.  It is 
ok once you get things working - but it is painful to script around and 
to trace LST errors back to LND transactions.

Nic