Hello list,
i've created a new ceph fs with:
mkcephfs -a -c /etc/ceph/ceph.conf -k /etc/ceph/client.admin.keyring
I've then connected to ceph with ceph -w and got pretty immediatly this
crash:
012-06-14 11:48:23.965577 7f548365c700 0 monclient: hunting for new mon
ceph: mon/PGMap.cc:137:
On Thu, Jun 14, 2012 at 1:41 AM, Greg Farnum g...@inktank.com wrote:
On Wednesday, June 13, 2012 at 1:37 PM, Florian Haas wrote:
Greg,
My understanding of Ceph code internals is far too limited to comment on
your specific points, but allow me to ask a naive question.
Couldn't you be
Hi,
Am 08.05.2012 00:58, schrieb Tommi Virtanen:
[...]
The current work is in a branch called ceph-1, and will be improved
upon, but it is now at a stage where others should start looking at
it.
[...]
And where can I find this branch? I've checked the git repo at:
The current osd capabilities do a few things that, in retrospect, are more
complex than is necessary or desired. In particular, the current
implementation allows
allow rwx, deny pool blah rwx
The deny stuff is confusing to understand (it's ordering dependent), and
not used by
On Wed, Jun 13, 2012 at 10:40 AM, Gregory Farnum g...@inktank.com wrote:
2) Client fencing. See http://tracker.newdream.net/issues/2531. There
is an existing blacklist functionality in the OSDs/OSDMap, where you
So I just managed to put into words another reason I like the key
rotation more
On Thu, 14 Jun 2012, Stefan Priebe - Profihost AG wrote:
I got this fixed by deleting all content in /srv/osd.X. But now i get with the
next branch this one:
=== osd.32 ===
pushing conf and monmap to ssdstor002:/tmp/mkfs.ceph.4885
2012-06-14 14:02:09.09 7f815cd26780 -1 journal
Hi everyone,
it occurred to me this afternoon that admin/build-doc unconditionally
tries to fetch some updates from GitHub, which breaks building docs when
you don't have a network connection. Would there be any reasonably
simple way to make it support offline build, provided the various pip
bits
Am 14.06.2012 22:17, schrieb Sage Weil:
On Thu, 14 Jun 2012, Stefan Priebe - Profihost AG wrote:
Is it possible that the osd journal you configured is a file in the osd
data directory that doesn't already exist
Sure is this wrong?
[osd]
osd journal = /journal/osd.$id.journal
osd
Hello list,
i read somewhere that the mon has special disk access patterns - even
though it does not write much data.
I'm using a patched debian squeeze with syncfs support (thanks to amon).
Are there any recommandations where to put the mon data? (SSD? Raid?
Which FS?)
Greets,
Stefan
--
