I also can say this procedure works fine with a little tweak to the
.spec file
for building the server packages.
It works well also with kernel 3.18.33, the latest one I tested with
Lustre/ZFS
On 24/06/16 13:15, Christopher J. Morrone wrote:
Yes, it is all a lot harder than it should be at
The error indeed does exist. It hapened to me too.
For my own Lustre server needs I just fixed it commenting out two lines
in the .spec file since I am not running Lustre in High Avilability.
On 29/06/16 11:41, Christopher J. Morrone wrote:
On 06/29/2016 10:36 AM, Martin Hecht wrote:
Hello
On 06/29/2016 10:36 AM, Martin Hecht wrote:
> Hello,
>
> I have just seen that you managed to mount with a different kernel, but
> let me come back to this error when building your own rpms for a
> specific kernel.
>
> Independent if you use it or not, I believe on lustre servers you need
> to ha
This is a bug in the RPM .spec file. While heartbeat is one option for HA on
servers, it definitely should not be required. Could you please file a Jira
ticket with details.
Cheers, Andreas
> On Jun 29, 2016, at 11:36, Martin Hecht wrote:
>
> Hello,
>
> I have just seen that you managed to
Hello,
I have just seen that you managed to mount with a different kernel, but
let me come back to this error when building your own rpms for a
specific kernel.
Independent if you use it or not, I believe on lustre servers you need
to have heartbeat installed nowadays. This is not installed by de
One caveat - the Linux VFS still serializes file creates/unlinks in a single
directory, even though the server allows them in parallel (it doesn't use the
VFS). Even lookups within a single directory are serialized on the client by
the VFS except with the very latest kernels, and Lustre hasn't
