I should add that I not using the kernel module on the client. I am
simply using pvfs2-ls, pvfs2-cp, pvfs2-rm several times in a row,
then ^C the server.
For each command line tool, the client does a connect to the server.
The server cleans up the old client state and resets it. I assume it
is related to multiple calls to bmi_method_addr_reg_callback() on the
server.
Scott
On Jan 18, 2007, at 5:03 PM, Pete Wyckoff wrote:
[EMAIL PROTECTED] wrote on Thu, 18 Jan 2007 15:36 -0600:
I'm a little skeptical that this is a bug outside of mx or ib. Scott
do you get the same behavior from valgrind if you use tcp? Or even
get the same hang on sighup if you use tcp?
Valgrind on the server with IB works fine for me, FYI. That may be
a recent event, though. We're using up-to-date FC6. And I've not
seen the same bug Scott is running into yet.
-- Pete
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
