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.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
