The formula for objects in a file is <ino in hex>.<object in sequence>. So you'll have noticed they all look something like 12345.00000001, 12345.00000002, 12345.00000003, ... So if you've got a particular inode and file size, you can generate a list of all the possible objects in it. To find the object->OSD mapping you'd need to run crush, by making use of the crushtool or similar. -Greg On Tue, Sep 29, 2015 at 6:29 AM, Andras Pataki <apataki@xxxxxxxxxxxxxxxxxxxx> wrote: > Thanks, that worked. Is there a mapping in the other direction easily > available, I.e. To find where all the 4MB pieces of a file are? > > On 9/28/15, 4:56 PM, "John Spray" <jspray@xxxxxxxxxx> wrote: > >>On Mon, Sep 28, 2015 at 9:46 PM, Andras Pataki >><apataki@xxxxxxxxxxxxxxxxxxxx> wrote: >>> Hi, >>> >>> Is there a way to find out which radios objects a file in cephfs is >>>mapped >>> to from the command line? Or vice versa, which file a particular radios >>> object belongs to? >> >>The part of the object name before the period is the inode number (in >>hex). >> >>John >> >>> Our ceph cluster has some inconsistencies/corruptions and I am trying to >>> find out which files are impacted in cephfs. >>> >>> Thanks, >>> >>> Andras >>> >>> >>> >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@xxxxxxxxxxxxxx >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>> > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |