I have created a cluster with 2 nodes and 6 osds each.
I would like to verify if my pgs are being placed on the correct nodes based on
my crushmap. I would like to make sure that my replication (x2, default) is not
placed on the same host. Osd.0 through 5 is on host0 and osd.6 through osd.11
is
On Sat, Jul 2, 2011 at 6:30 AM, Wilfrid Allembrand
wrote:
> Hi everyone,
>
> I'm trying to figure out what is the best OSD solution with an
> infrastructure made up of servers with a lot a disks in each. Say, for
> exemple you have 4+ nodes like Sun Fire X4500 (code-named Thumper).
> Each node is
On Mon, Jul 4, 2011 at 10:17 AM, Vasilakakos Giorgos wrote:
> Hello folks, I have a question:
> I know files get mapped to objects and those objects to OSDs but how
> exactly do we go from one to the other?
> What I mean is, given the filename I want to access how does Ceph find
> the relevant obj
On Mon, Jul 4, 2011 at 7:10 PM, Fusheng Han wrote:
> Hello, Wido
>
> I appreciate your answer.
> And some more discussion goes below.
>
> On Tue, Jul 5, 2011 at 1:54 AM, Wido den Hollander wrote:
>> Hi,
>>
>> On Tue, 2011-07-05 at 00:25 +0800, Fusheng Han wrote:
>>> Hi, all
>>>
>>> After reading
On Sun, 3 Jul 2011, Fyodor Ustinov wrote:
> Hi!
>
> mds - 0.30
>
> I can not to reproduce, sorry.
>
> mds/Locker.cc: In function 'void Locker::file_excl(ScatterLock*, bool*)', in
> thread '0x7fefc6c68700'
> mds/Locker.cc: 3982: FAILED assert(in->get_loner() >= 0 &&
> in->mds_caps_wanted.empty()
Hello, Gregory
Thank you for your explanation of the "Acting groups" mechanism. I
think it is a good solution.
But does it break the design philosophy of RADOS. In my own opinion,
monitor cluster just take the cluster map and failure detection,
failure recovery and data migration are all handled b
Applied, thanks!
On Mon, 4 Jul 2011, Alexandre Oliva wrote:
> Logrotate ignores entries after a rule that doesn't match any files.
>
> Signed-off-by: Alexandre Oliva
> ---
> src/logrotate.conf | 19 ++-
> 1 files changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/src
OK thanks, I think you've answered my question between this message
and the links you provided.
On Tue, Jul 5, 2011 at 18:29, Gregory Farnum
wrote:
> On Mon, Jul 4, 2011 at 10:17 AM, Vasilakakos Giorgos
> wrote:
>> Hello folks, I have a question:
>> I know files get mapped to objects and those
On Wed, 6 Jul 2011, Fusheng Han wrote:
> Hello, Gregory
>
> Thank you for your explanation of the "Acting groups" mechanism. I
> think it is a good solution.
> But does it break the design philosophy of RADOS. In my own opinion,
> monitor cluster just take the cluster map and failure detection,
>
HI everyone, I want to consult everybody ceph file system, whether to
support the PHP flock ()?
If that is not like NFS flock () support?
thanks!
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Linus,
Please pull the following Ceph fixes from
git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
These are all related to issues with O_DIRECT when the pointer and IO
alignments do not match, and/or when there are holes in the file.
Thanks!
sage
Sage Weil (3
On Wed, 6 Jul 2011, biyan chen wrote:
> HI everyone, I want to consult everybody ceph file system, whether to
> support the PHP flock ()?
>
> If that is not like NFS flock () support?
flock() and fcntl() locks are support with the kernel client, but not yet
with the fuse-based client.
sage
--
T
Thanks!
2011/7/6 Sage Weil :
> On Wed, 6 Jul 2011, biyan chen wrote:
>> HI everyone, I want to consult everybody ceph file system, whether to
>> support the PHP flock ()?
>>
>> If that is not like NFS flock () support?
>
> flock() and fcntl() locks are support with the kernel client, but not yet
>
Hello,
So I updated packages + the kernel (now running 3.0.0-0300rc6-generic)
but I continue to have the same error. Any idea ?
Regards,
Wilfrid
2011/7/4 Wilfrid Allembrand :
> Hello,
>
> When trying to launch gceph (gceph -v : ceph version 0.30
> (commit:64b1b2c70f0cde39c72d5d724c65ea8afaaa00b9
14 matches
Mail list logo