[Lustre-discuss] detecting problematic files via mds/oss syslog messages

[Ender Güler]

Andreas and Brian,

Thank you for invaluable information you gave.

Regards,

Ender GULER

On Tue, Jul 21, 2009 at 4:51 PM, Brian J. Murrell <Brian.Murrell at sun.com>wrote:

> On Mon, 2009-07-20 at 16:06 -0600, Andreas Dilger wrote:
> > On Jul 20, 2009  13:20 +0300, Ender G�ler wrote:
> > > Are there any ways of detecting the problematic file names from the
> mds/oss
> > > syslog messages? Or to be more definite, are there any ways to find a
> map of
> > > file name to inode number or file name to object id or inode number to
> > > object id? I'm trying to understand the insights of lustre and some
> times I
> > > wonder which files are affected from a lustre error? For example, when
> I see
> > > an object id in log messages, how can I understand which file is this?
> Is
> > > there any look up table, or map for these purposes?
> >
> > If there are particularly bad error messages, you could file a bug with
> > details.
> >
> > It is also possible to manually map an OST object ID to an MDS filename.
> > For example, objid 620032 on my filesystem:
>
> This exact procedure is being added to the manual FWIW.  Details are in
> bug 19753.
>
> b.
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20090722/dacbbc4f/attachment.htm>