Andreas and Brian,<br><br>Thank you for invaluable information you gave. <br><br>Regards,<br><br>Ender GULER<br><br><div class="gmail_quote">On Tue, Jul 21, 2009 at 4:51 PM, Brian J. Murrell <span dir="ltr"><<a href="mailto:Brian.Murrell@sun.com">Brian.Murrell@sun.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Mon, 2009-07-20 at 16:06 -0600, Andreas Dilger wrote:<br>
> On Jul 20, 2009 13:20 +0300, Ender G\ufffdler wrote:<br>
> > Are there any ways of detecting the problematic file names from the mds/oss<br>
> > syslog messages? Or to be more definite, are there any ways to find a map of<br>
> > file name to inode number or file name to object id or inode number to<br>
> > object id? I'm trying to understand the insights of lustre and some times I<br>
> > wonder which files are affected from a lustre error? For example, when I see<br>
> > an object id in log messages, how can I understand which file is this? Is<br>
> > there any look up table, or map for these purposes?<br>
><br>
> If there are particularly bad error messages, you could file a bug with<br>
> details.<br>
><br>
> It is also possible to manually map an OST object ID to an MDS filename.<br>
> For example, objid 620032 on my filesystem:<br>
<br>
</div>This exact procedure is being added to the manual FWIW. Details are in<br>
bug 19753.<br>
<font color="#888888"><br>
b.<br>
<br>
</font><br>_______________________________________________<br>
Lustre-discuss mailing list<br>
<a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>
<a href="http://lists.lustre.org/mailman/listinfo/lustre-discuss" target="_blank">http://lists.lustre.org/mailman/listinfo/lustre-discuss</a><br>
<br></blockquote></div><br>