Ok, like I said, most files with _long at the end are *not orphaned*.
The generation number also is *not* an indication of whether the file
is orphaned -- some of the orphaned files will have ffffffffffffffff
as the generation number and others won't. For each long filename
object in a pg you would have to:
1) Pull the long name out of the attr
2) Parse the hash out of the long name
3) Turn that into a directory path
4) Determine whether the file is at the right place in the path
5) If not, remove it (or echo it to be checked)
You probably want to wait for someone to get around to writing a
branch for ceph-objectstore-tool. Should happen in the next week or
two.
-Sam
On Wed, Mar 16, 2016 at 1:36 PM, Jeffrey McDonald <jmcdonal@xxxxxxx> wrote:
> Hi Sam,
>
> I've written a script but i'm a little leary of unleasing it until I find a
> few more cases to test. The script successfully removed the file mentioned
> above.
> I took the next pg which was marked inconsistent and ran the following
> command over those pg directory structures:
>
> find . -name "*_long" -exec xattr -p user.cephos.lfn3 {} + | grep -v
> ffffffffffffffff
>
> I didn't find any files that "orphaned" by this command. All of these
> files should have "_long" and the grep should pull out the invalid
> generation, correct?
>
> I'm looking wider but in the next pg marked inconsistent I didn't find any
> orphans.
>
> Thanks,
> Jeff
>
> --
>
> Jeffrey McDonald, PhD
> Assistant Director for HPC Operations
> Minnesota Supercomputing Institute
> University of Minnesota Twin Cities
> 599 Walter Library email: jeffrey.mcdonald@xxxxxxxxxxx
> 117 Pleasant St SE phone: +1 612 625-6905
> Minneapolis, MN 55455 fax: +1 612 624-8861
>
>
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
