There is the ll_decode_filter_fid tool, that should be able to work on ZFS,
though I'm just traveling and unable to confirm. That should be run on the
mounted ZFS filesystem.
The format of the LMA is the same as ldiskfs - struct lustre_mdt_attrs to hold
the "self" FID on both the OST and MDT objects, and struct filter_fid to hold
the parent (MDT) FID for OST objects.
> On Sep 16, 2016, at 13:06, Alexander I Kulyavtsev <a...@fnal.gov> wrote:
> What is the simple way to find corrupted file reported in lustre error, like :
> Sep 12 19:12:29 lfs7 kernel: LustreError:
> 10704:0:(ldlm_resource.c:1188:ldlm_resource_get()) lfs-OST0012: lvbo_init
> failed for resource 0x51b94b:0x0: rc = -2
> 0x51b94b looks like objid, how to find fid or the file corresponding to it?
> I can scan underlying zfs with zdb like in zfsobj2fid.py . Where to look for
> What is format of trusted.lma in lustre zfs?
> OST reported errors like these and some objects were orphaned.
> few files were reported by user having ls error
> -????????? ? ? ? ? ? filename
> and I was able to identify file with lfs getstripe and unlink it.
> Name to objid was easy. Now I need to translate the opposite way.
> I would like to identify a dozen of other objects reported in the logs and
> trying to avoid full scan of namespace.
> Lustre 2.5.3
> Thank you in advance,
> lustre-discuss mailing list
lustre-discuss mailing list