Mudit,
Those are the journal objects you're seeing touched. Write some data
to the file, and do a "rados -p ls" to check the
objects for the inode number you're expecting.
Cheers,
Johnn
On Tue, Feb 3, 2015 at 10:53 AM, Mudit Verma wrote:
> Hi Sage,
>
> Following are the greps through inotify,
Thanks a lot Sage.
On Tue, Feb 3, 2015 at 3:34 PM, Sage Weil 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
>
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/10003
Great, I found the file which contains the data
root@ceph-osd1:/var/local/osd1/current# grep "hello3" * -r
1.0_head/10003fb.__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 f
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
10003fb
The object names will be something like 10003fb.0001. The
filenames once they hit disk w
Hi Sage,
Following are the greps through inotify, I created a file name cris at
client end
>From stats the ino number is 1099511628795
but it does not match to the hex *06E5F474*
On ODS:
/var/local/osd1/current/2.0_head/ OPEN *200.0001__head_06E5F474__2*
/var/local/osd1/current/2.0_head
Hi Sage,
Are there some methods to prevent the file from being stripped to
multiple objects? eg, the file will be mapped to only one object in
the client side with ceph FS interface...
On Mon, Feb 2, 2015 at 1:05 AM, Sage Weil wrote:
> It's inode number (in hex), then ".", then block number (in
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
wrote:
>Hi All,
>
>CEPHFS - Given a file name, how can one determine the exact location
>and
>the name of the objects on OSDs.
Hi Verma
All lauout questions are detailed here for CephFS.
http://docs.ceph.com/docs/master/cephfs/file-layouts/
Hope this is what you are looking for
Cheers
JC
While moving. Excuse unintended typos.
> On Feb 1, 2015, at 08:08, Mudit Verma wrote:
>
> Hi All,
>
> CEPHFS - Given a file na
