Dear All,
We have found the answer. Starting from Lustre-2.4, the OST will stop
any update actions if we deactive it. Hence during data migration, if
we deactive the OST chome-OST0028_UUID, and copy data out via:
cp -a .tmp
mv .tmp
The "junk" still leaves in
Registration for The 17th Annual Lustre User Group Conference is NOW OPEN.
May 15-17, 2019
University of Houston Student Center
4455 University Drive
Houston, TX 77204
LUG 2019 is the industry's primary venue for discussion and seminars on the
Lustre parallel file system and other open source
Riccardo,
Since 2.12 is still a relatively new maintenance release, it would be helpful
if you could open an LU and provide more detail there - Such as what clients
were doing, if you were using any new features (like DoM or FLR), and full
dmesg from the clients and servers involved in these
Hello,
I have quite a big issue on my Lustre 2.12.0 MDS/MDT.
Clients moving data to the OSS occur into a locking problem I never met
before.
The clients are mostly 2.10.5 except for one which is 2.12.0 but
regardless the client version the problem is still there.
So these are the errors I
I think I figured out the problem.
My problem is related to Lnet Network Health feature:
https://jira.whamcloud.com/browse/LU-9120
the lustre MDS and the lsutre client having same version 2.12.0
negotiate a Multi-rail peer connection while this does not happen with
the other clients (2.10.5).
Hi Riccardo,
It's not LNet Health. It's Dynamic Discovery. What's happening is that 2.12
is discovering all the interfaces on the peer. That's why you see all the
interfaces in the peer show.
Multi-Rail doesn't enable o2ib. It just sees it. If the node doing the
discovery has only tcp, then it
Take a look at this: https://jira.whamcloud.com/browse/LU-11840
Let me know if this is the same issue you're seeing.
On Tue, 5 Mar 2019 at 14:04, Amir Shehata
wrote:
> Hi Riccardo,
>
> It's not LNet Health. It's Dynamic Discovery. What's happening is that
> 2.12 is discovering all the
it is not exactly this problem.
here is my setup
* MDS is on tcp0
* client is on tcp0 and o2ib0
* OSS is on tcp0 and o2ib0
The problem is that the MDS is discovering both the lustre client and
the OSS as well over o2ib and it should not because the MDS has only one
ethernet interface. I
