[Lustre-discuss] Lustre error: ll_inode_revalidate_fini failure -43

[Brian J. Murrell]

On Thu, 2008-12-18 at 16:11 -0600, Hendelman, Rob wrote:
> I would have never really guessed to search for this since the error message talks about an inode.  I was searching for inode information in the lustre manual.  I wanted to at least identify the file attached to the inode that is having the problem (invalid/unknown uid/gid).

Yeah, it's not obvious where to go given the error message.  This really
boils down to good/complete initial configuration that meets your
requirements.

> from 32.5.9:
> My /proc/fs/lustre/mds/{mdtname}/group_upcall points to /usr/sbin/l_getgroups

When that proc variable is set as such (which might just be it's default
value) you are asserting that you want supplemental groups to work.  If
you don't care about supplemental groups, the easiest thing to do is set
that value to NONE.

If you want supplemental groups to work then the passwd/group databases
on the MDS(es) and clients MUST be the same.  Not just for your usual
login users, but for any (i.e. system) user that might be making any
kind of query of Lustre, as you have discovered.

> I'm guessing the correct solution is to add a local nagios user with uid/gid on the mds with the 113 uid.  Do I also need to do this for the mgs (in my case the same box, but it would be good to know for the future) and the oss's ?

Just the MDS(es) and clients need a common database.  The OSSes are not
involved in this aspect.

> Thanks for shedding some light on this.

NP.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20081218/f45df024/attachment.pgp>