All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: ceph-devel@vger.kernel.org
Subject: Available space shrinks to zero after upgrading cluster
Date: Mon, 09 Jan 2012 12:23:53 +0100	[thread overview]
Message-ID: <2223940.SkCGeMiCNa@pc10> (raw)

Hi,

I just upgraded my cluster to the current git version (from 0.39, using 
https://github.com/NewDreamNetwork/ceph.git), and now ceph -s reports the 
total available space in the the cluster as 0 and all of the clients using the 
cluster are blocking:

# ceph -s
2012-01-09 12:12:39.433576    pg v313084: 396 pgs: 396 active+clean; 79166 MB 
data, 0 KB used, 0 KB / 0 KB avail
2012-01-09 12:12:39.434269   mds e11: 1/1/1 up {0=alpha=up:replay}
2012-01-09 12:12:39.434289   osd e293: 6 osds: 6 up, 6 in
2012-01-09 12:12:39.434338   log 2012-01-09 12:12:26.600575 mon.0 
10.3.1.33:6789/0 6 : [INF] osd.1 10.3.1.33:6804/22161 boot
2012-01-09 12:12:39.434389   mon e5: 3 mons at 
{ceph1=10.3.1.33:6789/0,ceph2=10.3.1.34:6789/0,ceph3=10.3.1.35:6789/0}

I have a cluster with three machines, each with two OSDs and one mon. 
Additionally, the first one also has a single mds.

I did the upgrade by cloning the latest git sources onto each machine, doing 
the usual ./autgen.sh, ./configure, make && make install and then restarting 
ceph on one machine after the other using /etc/init.d/ceph restart, starting 
with the last one.

So... what's happening here and how do I get my cluster working again?

	Guido

             reply	other threads:[~2012-01-09 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 11:23 Guido Winkelmann [this message]
2012-01-09 11:28 ` Available space shrinks to zero after upgrading cluster Guido Winkelmann
2012-01-09 23:40   ` Samuel Just
2012-01-11 15:10     ` Guido Winkelmann

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=2223940.SkCGeMiCNa@pc10 \
    --to=guido-ceph@thisisnotatest.de \
    --cc=ceph-devel@vger.kernel.org \
    /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.