[Lustre-discuss] Future of lustre 1.8.3+

[Bernd Schubert]

On Wednesday 26 May 2010, Guy Coates wrote:
> On 26/05/10 17:25, Ramiro Alba Queipo wrote:
> > On Wed, 2010-05-26 at 16:48 +0100, Guy Coates wrote:
> >>>> One thing to watch out for in your kernel configs is to make sure
> >>>> that:
> >>>>
> >>>> CONFIG_SECURITY_FILE_CAPABILITIES=N
> >>>
> >>> OK. But the question is if this issue still applies for lustre-1.8.3
> >>> and SLES kernel linux-2.6.27.39-0.3.1.tar.bz2. I mean, is quite
> >>> surprising that if this problems persist, Oracle is offering lustre
> >>> packages for SLES11 with CONFIG_SECURITY_FILE_CAPABILITIES=y ???????
> >>> I am just about to start testing, so I'd like to clarify this.
> >>
> >> The binary SLES packages are fine; it is the source packages that may be
> >> problematic, depending on your config. There is a bug filed against this
> >
> > Sorry Guy. May be there is something I am missing, but SLES11 rpm kernel
> > server packages for lustre-1.8.3 are created using a config with
> > ONFIG_SECURITY_FILE_CAPABILITIES=y (See yourself on the attachement
> 
> You are entirely correct.

To be clear here, this is a CLIENT side issue. So whatever you do set on the 
server side is irrelevant. Oracle cannot set kernel options for clients, as 
those are upstream kernels and lustre is compiled patchless against it.

Applying  this Lustre patch from bugzilla#15587 should solve the issue without 
the need to recompile the kernel:

https://bugzilla.lustre.org/attachment.cgi?id=29116


Cheers,
Bernd

-- 
Bernd Schubert
DataDirect Networks