Hi Oleg, The numbers that came after LustreError varies, they're never the same. I'll dig more based on your suggestions, really appreciate that.
Thanks, Murshid. On Wed, Aug 27, 2014 at 11:49 AM, Drokin, Oleg <[email protected]> wrote: > Hello! > > I guess I don't have any smart ideas about what's goinf on. > Is the number after "LustreError" the same most of the time? that's > pid, so you can chek what's the process doing it. > Also I imagine you can add a dump_stack() call to that condition in the > source so that a backtrace is printed and we know what is the call path. > > Bye, > Oleg > On Aug 26, 2014, at 12:28 AM, Murshid Azman wrote: > > > Hello Oleg, > > > > Thanks for your response. > > > > The kernel I'm using is 2.6.32-279.19.1.el6.x86_64 > > > > This client mounts NFS shares from another server. They're not mounted > directly onto Lustre filesystem, but rather onto a tmpfs filesystem > residing in the memory. > > > > [root@node01 ~]# df -h / > > Filesystem Size Used Avail Use% Mounted on > > tmpfs 50M 484K 50M 1% / > > > > I've removed the NFS mounts but can still see the same error. This > client does not share NFS to others. > > > > Thank you. > > > > Murshid Azman. > > > > > > > > On Fri, Aug 22, 2014 at 9:12 PM, Drokin, Oleg <[email protected]> > wrote: > > Hello! > > > > On Aug 22, 2014, at 3:28 AM, Murshid Azman wrote: > > > We're trying to run a cluster image on Lustre filesystem version 2.5.2 > and repeatedly seeing the following message. Haven't seen anything bizarre > on this machine other than this: > > > > > > 2014-08-22T13:52:01+07:00 node01 kernel: LustreError: > 4271:0:(namei.c:530:ll_lookup_ > > > it()) Tell Peter, lookup on mtpt, it open > > > 2014-08-22T13:52:01+07:00 node01 kernel: LustreError: > 4271:0:(namei.c:530:ll_lookup_it()) Skipped 128 previous similar messages > > > > > > This doesn't happen to our desktop Lustre clients. > > > > > > I'm wondering if anyone has any idea what this means. > > > > This is one of those "impossible condition has been met" messages. > Essentially it means that we got a lookup call for a mountpount, > > which should not happen because it's a mountpoint, so it's always valid > and pinned in memory at the very least. > > > > What kernel do you use? anything else interesting about this client - > e.g. NFS rexport? > > > > Bye, > > Oleg > > > >
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
