Mike Marshall <[email protected]> writes:
>> the current source won't build for Fedora pre-24...
>
> Hmmm... I just built userspace "trunk" on fedora 23, 4.4.6-300.fc23.x86_64...
> I know the kernel module won't compile yet on fedora 23 if it is
> yum updated to linux 4.4.x ...
Sorry, that was unclear. I meant Fedora 24-alpha, or whatever it's
currently called -- I don't pay much attention to non-EPEL development.
<https://copr-be.cloud.fedoraproject.org/results/loveshack/orangefs/fedora-23-x86_64/00166585-orangefs/>
was built against 4.4.3-300 according to the log, but I wouldn't know if
it works.
>> Do you get a useful error if they're mismatched...
>
> Yes...
>
> I just tried to use trunk userspace with the 2.9.3 kernel module
> so I could provide a not-off-the-top-of-my-head answer...
>
> In the client log I saw:
>
> Error: protocol versions do not match.
> Please check that your pvfs2 module and pvfs2-client versions are consistent.
> critical device failure: Protocol error (error class: 896)
Good!
While I'm on, I need the following to build the trunk with RHEL6's
openib. (Are these Mellanox macros? I can't see them at
openfabrics.org.)
Also, is it now OK to build with both TCP and IB support, or is that
still problematic?
--- orangefs-2.9.4/src/io/bmi/bmi_ib/openib.c~
+++ orangefs-2.9.4/src/io/bmi/bmi_ib/openib.c
@@ -751,9 +751,11 @@
CASE(IBV_EVENT_GID_CHANGE);
/* Experimental event types */
+#ifdef IBV_EXP_EVENT_DCT_KEY_VIOLATION /* assume testing one is enough */
CASE(IBV_EXP_EVENT_DCT_KEY_VIOLATION);
CASE(IBV_EXP_EVENT_DCT_ACCESS_ERR);
CASE(IBV_EXP_EVENT_DCT_REQ_ERR);
+#endif
}
return s;
}
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
