Re: cephfs: from a file name determine the objects name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks a lot Sage. 

On Tue, Feb 3, 2015 at 3:34 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote:
The hash of the filename is ($inode.$block) is 4BC00833, and the pg id is
a slightly weird function of those bits.

sage


On Tue, 3 Feb 2015, Mudit Verma wrote:

> Great, I found the file which contains the data 
> root@ceph-osd1:/var/local/osd1/current# grep "hello3" * -r
>
> 1.0_head/100000003fb.00000000__head_4BC00833__1:hello3
>
> And it does indeed match to the hex ino. 
>
> How does it determined that the data will go to 1.0_head and what does
> head_4BC00833 stand for. 
>
>
>
> Thanks again for your prompt response. 
>
>
> Regards
> Mudit
>
>
> On Tue, Feb 3, 2015 at 3:26 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote:
>       On Tue, 3 Feb 2015, Mudit Verma wrote:
>       > Hi Sage, 
>       > Following are the greps through inotify,  I created a file
>       name cris at
>       > client end 
>       >
>       > From stats the ino number is 1099511628795
>
>       100000003fb
>
>       The object names will be something like 100000003fb.00000001. 
>       The
>       filenames once they hit disk will get the __head_$hash type
>       suffix based
>       on a hash of the name and some other random stuff.  I think the
>       __2 is
>       the pool id.
>
>       sage
>
>
>
>
>       >
>       > but it does not match to the hex 06E5F474
>       >
>       >
>       > On ODS:
>       >
>       > /var/local/osd1/current/2.0_head/ OPEN
>       200.00000001__head_06E5F474__2
>       >
>       > /var/local/osd1/current/2.0_head/ MODIFY
>       200.00000001__head_06E5F474__2
>       >
>       > /var/local/osd1/current/2.0_head/ CLOSE_WRITE,CLOSE
>       > 200.00000001__head_06E5F474__2
>       >
>       >
>       > May you please help me understand this
>       name 200.00000001__head_06E5F474__2
>       >
>       >
>       > Thanks
>       >
>       > Mudit
>       >
>       >
>       > On Sun, Feb 1, 2015 at 10:35 PM, Sage Weil <sage@xxxxxxxxxxxx>
>       wrote:
>       >
>       >       It's inode number (in hex), then ".", then block number
>       (in
>       >       hex).  You can get the ino of a file with stat.
>       >
>       >       sage
>       >
>       >
>       >
>       >       On February 1, 2015 5:08:18 PM GMT+01:00, Mudit Verma
>       >       <mudit.f2004912@xxxxxxxxx> wrote:
>       >       Hi All, 
>       > CEPHFS - Given a file name, how can one determine the exact
>       > location and the name of the objects on OSDs. 
>       >
>       > So far I could understand that the objects data is stored in
>       > .../current dir in OSDs, but what naming convention do they
>       > use? 
>       >
>       > Many thanks in advance 
>       >
>       > Thanks
>       > Mudit
>       >
>       >___________________________________________________________________________
>       _
>       > ceph-users mailing list
>       > ceph-users@xxxxxxxxxxxxxx
>       > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>       >
>       >
>       > --
>       > Sent from Kaiten Mail. Please excuse my brevity.
>       >
>       >
>       >
>       >
>
>
>
>

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux