Hello OpenSFS community,
We're excited to congratulate DataDirect Networks (DDN), an OpenSFS
Participant, on its acquisition of Intel's Lustre File System related
business and assets.
OpenSFS appreciates DDN's commitment to supporting the open source community
and continuing development moving forward according to the Lustre Community
Roadmap. <http://lustre.org/roadmap/> 
DataDirect Networks's decision to integrate the Lustre team as an autonomous
division within DDN and to ensure full and sustained support of the customer
and partner ecosystem is a welcome step.
OpenSFS and DDN will host a webinar in the coming weeks that will discuss
the transfer in more detail and provide an opportunity for community
questions and feedback.
OpenSFS thanks Intel's High Performance Data Division for their Lustre
efforts and welcomes Intel's continued activity in the Lustre community
following the transfer, including participation in OpenSFS, EOFS, and
Support for OpenSFS has continued growing over the past year as demonstrated
by increased OpenSFS membership. We encourage all Lustre users to join
OpenSFS and work with the community.
View the full press release online
This is not a critical issue but wondering if this is a possibility and if anyone has noticed anything similar. We have an installation of Lustre 2.7 with ZFS backed MDT's/OST's, and don't have any issues other than this odd behavior with some set of files.
We have run into some files that fail with an error by a python application, complaining corruption. Although when I make a copy of the same(complained by the application of being corrupt) file in the lustre scratch to a new location in the lustre scratch, and then run the application it runs successfully. This is puzzling and unsettling. Given md5sum matches of both the files one that runs and one that is complained as being corrupt, I wonder how could one explain this?
What other low level verification one can do to understand the differences in behavior? Any pointers here will be a great help.