"ROUTER_NOTIFY" is a misnomer - this happens on all network errors.
The upcall code has actually been removed and this change is working
(or has worked) its way through to release.
Cheers,
Eric
---------------------------------------------------
|Eric Barton Barton Software |
|9 York Gardens Tel: +44 (117) 330 1575 |
|Clifton Mobile: +44 (7909) 680 356 |
|Bristol BS8 4LL Fax: call first |
|United Kingdom E-Mail: eeb@bartonsoftware.com|
---------------------------------------------------
> -----Original Message-----
> From: lustre-discuss-bounces@clusterfs.com
> [mailto:lustre-discuss-bounces@clusterfs.com] On Behalf Of
> John R. Dunning
> Sent: 24 July 2007 4:14 PM
> To: lustre-discuss@clusterfs.com
> Subject: [Lustre-discuss] lnet-upcall?
>
> Seen in my logs:
>
> [4295517.954000] Lustre:
> 23:0:(linux-debug.c:98:libcfs_run_upcall()) Invoked LNET
> upcall /usr/lib/lustre/lnet_upcall
> ROUTER_NOTIFY,192.168.100.105@tcp,down,1184577857
>
> I have no routers configured. Anybody know what that''s
> trying to tell me?
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss@clusterfs.com
> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss