from:"Thomas Roth via lustre\-discuss"

[lustre-discuss] default Nodemap: ll_close_inode_openhandle errors

2024-04-23 Thread Thomas Roth via lustre-discuss


Hi all,

as described before, I have a test cluster with the nodemap feature activated, and managed to get a bunch of clients to mount (by deactivating 
selinux), while these clients are in the "default" nodemap.

I left the "default"s property `admin=0` and set `trusted=1`, and everything 
seemed to work.

Now I ran a compile+install benchmark on these nodes, which finished 
successfully everywhere and with the expected performance.

However, the client logs all show a large number of the following errors:

> LustreError: 2967:0:(mdc_locks.c:1388:mdc_intent_getattr_async_interpret()) mdstest-MDT-mdc-9a0bc355f000: ldlm_cli_enqueue_fini() failed: 
rc = -13


> LustreError: 53842:0:(file.c:241:ll_close_inode_openhandle()) mdstest-clilmv-9a0bc355f000: inode [0x20429:0x9d8d:0x0] mdc close failed: rc 
= -13



Error code 13 is /* Permission denied */

Therefore I repeated the benchmark on one of the "Admin" nodes - the nodemap with both `admin=1` and `trusted=1` - and this client does not show these 
errors.


More than coincidence?

Given that the benchmark seems to have finished successfully, I would ignore these errors. On the other hand, if inodes cannot be handled - that 
sounds severe?


Regards,
Thomas
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] default Nodemap : clients cannot mount

2024-04-22 Thread Thomas Roth via lustre-discuss

OK - my bad: selinux was on.

It's a bunch of test hosts = sloppy configuration = default selinux settings.

With selinux=disabled, one of these hosts mounts, and if I give it trusted=1, the users are enabled,
root is squashed - all fine.

Cheers
Thomas

On 4/22/24 16:50, Thomas Roth via lustre-discuss wrote:

Hi all,

- Lustre 2.15.4 test system with MDS + 2 OSS + 2 administrative clients.

I activated nodemapping and put all these hosts into an "Admin" nodemap, which has the properties
`admin=1` and `trusted=1` - all works fine.

Now there are a couple of other hosts which should not become administrative clients, but just
standard clients => they should be / remain in the "default" nodemap.

The "default" nodemap has `admin=0` and `trusted=0`, as verified by
`lctl get_param nodemap.default`

- and these hosts cannot mount.
Error message is "l_getidentity: no such user 99"

I verified that these hosts actually are seen as "default" nodes by setting `admin=1` for one of them
- mounts.

Umount, lustre_rmmod, set `admin=0` again - does not mount anymore.

Atm I do not see what I overlooked, but I am certain this has worked before, where "before" would mean
other hardware and perhaps Lustre 2.15.1

*Switching* is still ok:
- Put client X into "Admin" nodemap, mount Lustre, remove client X from "Admin" nodemap, wait, try to
`ls` as root - fails.

Set the property `trusted=1` on the "default" nodemap, wait, try to `ls` as a
user - works.

However, this defeats the purpose of having a usable default...

Regards,
Thomas

Thomas Roth
Department: Informationstechnologie
Location: SB3 2.291

GSI Helmholtzzentrum für Schwerionenforschung GmbH
Planckstraße 1, 64291 Darmstadt, Germany, www.gsi.de

Commercial Register / Handelsregister: Amtsgericht Darmstadt, HRB 1528
Managing Directors / Geschäftsführung:
Professor Dr. Paolo Giubellino, Jörg Blaurock
Chairman of the Supervisory Board / Vorsitzender des GSI-Aufsichtsrats:
Ministerialdirigent Dr. Volkmar Dietz

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

[lustre-discuss] default Nodemap : clients cannot mount