From: Brad Hubbard <bhubbard@redhat.com>
To: Elita Lobo <loboelita@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Query regarding storage of objects in ceph
Date: Tue, 6 Sep 2016 15:05:32 +1000 [thread overview]
Message-ID: <CAF-wwdE0bg7vQ=HfMqzWqv5W5ZKB+3tCf2mCt6os_Jpf_tX8Ug@mail.gmail.com> (raw)
In-Reply-To: <CAA8xDw2jFn_C-Cj1mZ5w9UUxNpe3Z4SeM-2=xcUPJGOg=v4R9w@mail.gmail.com>
On Tue, Sep 6, 2016 at 2:31 PM, Elita Lobo <loboelita@gmail.com> wrote:
> Hello,
>
> I am using Ceph in my research project and hence need to know a bit
> about how it works internally. I would be grateful if someone would
> answer my queries.
>
> When chunks of 2 objects have to be stored on an osd, are they put
> into the same file or are these chunks stored in separate file. Is
> there any way I could see this data using some command? And in which
> folder of the osd are they stored in?
Working your way through this may help.
http://cephnotes.ksperis.com/blog/2013/08/20/ceph-osd-where-is-my-data
>
> Also, is there a way I can see the whole flow of function calls made
> when a node repair is going on?
>
> Lastly, could someone please suggest some resources ( other than docs)
> which would help me understand the internal implementation and give me
> an idea how to debug in ceph. (Attaching gdb to ceph daemons running
> in the background etc)
>
> Thanking you,
> Yours sincerely,
> Elita Lobo
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Cheers,
Brad
next prev parent reply other threads:[~2016-09-06 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 4:31 Query regarding storage of objects in ceph Elita Lobo
2016-09-06 5:05 ` Brad Hubbard [this message]
2016-09-07 5:44 ` Elita Lobo
2016-09-07 6:18 ` Brad Hubbard
[not found] ` <CAA8xDw0mVqDLHuKHZU+x3uFnQf5WJ9NsXTJa_zMbRnvB=SB9Hw@mail.gmail.com>
2016-09-11 16:13 ` Elita Lobo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF-wwdE0bg7vQ=HfMqzWqv5W5ZKB+3tCf2mCt6os_Jpf_tX8Ug@mail.gmail.com' \
--to=bhubbard@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loboelita@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.