[lustre-discuss] missing lustre version in /proc/fs/lustre/version

[Dilger, Andreas]

On Jun 21, 2017, at 19:39, Riccardo Veraldi <Riccardo.Veraldi at cnaf.infn.it> wrote:
> 
> I noticed as well that now "lustre check osts" does not work anymore
> with normal user privileges:
> 
> error: check: osts status failed
> 
> while it works with root privileges.
> Looking with strace turns out that a normal user has no privileges to
> look into /sys/fs/lnet/devices   /sys/kernel/debug/lnet/devices  and so
> on...

There are no files /sys/fs/lnet/devices or /sys/kernel/debug/lnet/devices, only
/sys/kernel/debug/lustre/devices which itself appears to be world readable..

Hmm, it appears that the /sys/kernel/debug is restricted to root users only,
even though there are subdirectories and files that are world readable.

> so basically to run "lustre check" from the lustre client is not
> possible as a normal user, while it was possible before.
> Is there a workaround or is it intended to be like that ?

This change is unintentional.  Can you please file a ticket in Jira with details.

Cheers, Andreas

> On 6/20/17 3:34 PM, Dilger, Andreas wrote:
>> On Jun 20, 2017, at 15:36, Riccardo Veraldi <Riccardo.Veraldi at cnaf.infn.it> wrote:
>>> Hello,
>>> 
>>> I built lustre-client 2.9.59 from source as dkms package.
>>> Everything work fine but /proc/fs/lustre/version  disappeared while it
>>> was there with Lustre client 2.9.0
>>> is this normal ?
>> We've had to move a lot of Lustre parameters out of /proc/fs/lustre and into /sys/fs/lustre
>> for most parameter values, or /sys/kernel/debug/lustre (via debugfs) for large statistics
>> due to rules imposed by the upstream kernel developers.  This change has already been done
>> for the Lustre upstream client over a year ago.
>> 
>> If you use, for example, "lctl get_param version" to access this parameter and others then
>> the change is handled transparently.  If you are using direct access to /proc then you will
>> need to special-case this by version, or use a wildcard path like:
>> 
>>     /{proc,sys}/{fs,sys,kernel/debug}/{lustre,lnet}/
>> or
>>     {/sys/{fs,kernel/debug}/{lnet,lustre}/,/proc/{fs,sys}/{lnet,lustre}/}
>> 
>> Not all combinations of the above path are actually valid for all parameters, but this is a
>> catch-all combination that will find the various parameters.  The actual valid paths are
>> /proc/sys/lustre, /proc/fs/lustre, /sys/fs/lustre, /sys/kernel/debug/lustre, and similar for
>> lnet parameters.
>> 
>> Cheers, Andreas
>> --
>> Andreas Dilger
>> Lustre Principal Architect
>> Intel Corporation
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 

Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Intel Corporation