[Lustre-discuss] what file(s) own multi-claimed blocks

Dilger, Andreas andreas.dilger at intel.com
Sat Apr 6 17:18:33 PDT 2013

On 2013/03/04 11:20 AM, "Andrus, Brian Contractor" <bdandrus at nps.edu>

>I am running e2fsck on one of my OSTs.
>I run into:
>File /O/0/d6/768742 (inode #22479589, mod time Fri Aug 17 11:15:51 2012)
>  has 1034 multiply-claimed block(s), shared with 4 file(s):
>        ... (inode #25579161, mod time Wed Oct  6 20:47:34 2010)
>        ... (inode #25579148, mod time Wed Oct  6 20:47:28 2010)
>        ... (inode #25579135, mod time Wed Oct  6 20:47:12 2010)
>        ... (inode #25579134, mod time Wed Oct  6 20:47:10 2010)
>It seems to imply there are only a few files affected by this issue.
>I would like to hunt down the specific file and delete/restore it, but
>how do I identify it?
>The OST is 16TB and the lustre filesystem itself is about 80TB
>I do have the OST offline and unmounted.
>Is there a quick/simple way to find the affected file(s)

Each OST object has an xattr called "fid" which contains its own object
ID, as well as the FID of the parent MDT inode of which it is a part.  If
you run debugfs on this OST you can print out this information with the
"stat" command:

debugfs -c /dev/{ost}
stat <25579161>
stat <25579148>
stat <25579135>
stat <25579134>

Cheers, Andreas
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division

More information about the lustre-discuss mailing list