<div dir="ltr"><div><div>Hi Oleg,<br><br></div>The numbers that came after LustreError varies, they're never the same. I'll dig more based on your suggestions, really appreciate that.<br><br></div>Thanks,<br>Murshid.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 11:49 AM, Drokin, Oleg <span dir="ltr"><<a href="mailto:oleg.drokin@intel.com" target="_blank">oleg.drokin@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello!<br>
<br>
I guess I don't have any smart ideas about what's goinf on.<br>
Is the number after "LustreError" the same most of the time? that's pid, so you can chek what's the process doing it.<br>
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.<br>
<br>
Bye,<br>
Oleg<br>
<div class="HOEnZb"><div class="h5">On Aug 26, 2014, at 12:28 AM, Murshid Azman wrote:<br>
<br>
> Hello Oleg,<br>
><br>
> Thanks for your response.<br>
><br>
> The kernel I'm using is 2.6.32-279.19.1.el6.x86_64<br>
><br>
> 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.<br>
><br>
> [root@node01 ~]# df -h /<br>
> Filesystem Size Used Avail Use% Mounted on<br>
> tmpfs 50M 484K 50M 1% /<br>
><br>
> I've removed the NFS mounts but can still see the same error. This client does not share NFS to others.<br>
><br>
> Thank you.<br>
><br>
> Murshid Azman.<br>
><br>
><br>
><br>
> On Fri, Aug 22, 2014 at 9:12 PM, Drokin, Oleg <<a href="mailto:oleg.drokin@intel.com">oleg.drokin@intel.com</a>> wrote:<br>
> Hello!<br>
><br>
> On Aug 22, 2014, at 3:28 AM, Murshid Azman wrote:<br>
> > 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:<br>
> ><br>
> > 2014-08-22T13:52:01+07:00 node01 kernel: LustreError: 4271:0:(namei.c:530:ll_lookup_<br>
> > it()) Tell Peter, lookup on mtpt, it open<br>
> > 2014-08-22T13:52:01+07:00 node01 kernel: LustreError: 4271:0:(namei.c:530:ll_lookup_it()) Skipped 128 previous similar messages<br>
> ><br>
> > This doesn't happen to our desktop Lustre clients.<br>
> ><br>
> > I'm wondering if anyone has any idea what this means.<br>
><br>
> This is one of those "impossible condition has been met" messages. Essentially it means that we got a lookup call for a mountpount,<br>
> which should not happen because it's a mountpoint, so it's always valid and pinned in memory at the very least.<br>
><br>
> What kernel do you use? anything else interesting about this client - e.g. NFS rexport?<br>
><br>
> Bye,<br>
> Oleg<br>
><br>
<br>
</div></div></blockquote></div><br></div>