I tried testing version 1.3.2 and also the latest from CVS to resolve this and other issues. I found a separate problem which did not exist in pre1.3.1 version. When I kill pvfs2-client-core process, it automatically remounted the file system, but with version 1.3.2 and also the latest version from CVS, it fails to do so. The error messages in pvfs2-client log are as follows:
[E 16:32:19.109677] PVFS_sys_fs_add: Failed to initialize any appropriate BMI methods. [E 16:32:19.109911] Failed to mount via host defaultuark:3334 [E 16:32:19.109988] Mount failed: Protocol not available [E 16:32:19.110136] *** Failed to remount filesystems! The hostname specified in the pvfs2tab and fstab is "quark". The pvfs2-client-core has somehow replaced the "q" with "default" in the host string. This behavior was consistent when I changed the hostname entry in pvfs2tab. Thanks, uday -----Original Message----- From: Phil Carns [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 07, 2005 9:21 AM To: Uday Shingwekar Cc: [email protected] Subject: Re: [PVFS2-users] pvfs2-client-core memory usage keeps increasing, pvfs2-server runs out of open file descriptors etc. > [E 23:31:07.186802] *** msgpairarray_completion_fn: msgpair failed, no > retry: Connection reset by peer > [E 23:31:07.186856] Error: state machine using an invalid termination > path. I don't know what caused the first error message in your case, but the second one (invalid termination path) is fixed now in pvfs2 1.3.2. -Phil _______________________________________________ PVFS2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
