Hello,
I am building lustre-client from src rpm on RHL73.
it fails with this error during the install process:
+ echo /etc/init.d/lnet
+ echo /etc/init.d/lsvcgss
+ find /root/rpmbuild/BUILDROOT/lustre-client-2.9.0-1.el7.x86_64 -name
'*.so' -type f -exec chmod +x '{}' ';'
+ '[' -d
/root/rpmbuild/
On Apr 27, 2017, at 05:43, E.S. Rosenberg wrote:
>
> A user just rm'd a big archive of theirs on lustre, any way to recover it
> before it gets destroyed by other writes?
Just noticed this email.
In some cases, an immediate power-off followed by some ext4 recovery tools
(e.g. ext3grep) might
> On May 3, 2017, at 12:23 PM, Patrick Farrell wrote:
>
> That reasoning is sound, but this is a special case. -11 (-EAGAIN) on
> ldlm_enqueue is generally OK...
>
> LU-8658 explains the situation (it's POSIX flocks), so I'm going to reference
> that rather than repeat it here.
>
> https://
Rick, Lydia,
That reasoning is sound, but this is a special case. -11 (-EAGAIN) on
ldlm_enqueue is generally OK...
LU-8658 explains the situation (it's POSIX flocks), so I'm going to reference
that rather than repeat it here.
https://jira.hpdd.intel.com/browse/LU-8658
- Patrick
I think that -11 is EAGAIN, but I don’t know how to interpret what that means
in the context of Lustre locking. I assume these messages are from the clients
and the changing “x” portion is just the fact that each client has a
different identifier. So if you have multiple clients complainin
Dear,
I have setup the Lustre-git(2.9.55_45) on CentOS 7.3, but the
client(on the same multi-host IB) can't mount lustre. Can you help
me? Thank you very much.
The server:
mkfs.lustre --fsname=lxfs --mgs --mdt --index=0 --reformat
/dev/sda
