All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Thompson <andrewkt@aktzero.com>
To: Tommi Virtanen <tv@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Very unbalanced storage
Date: Tue, 04 Sep 2012 12:19:07 -0400	[thread overview]
Message-ID: <504629FB.30801@aktzero.com> (raw)
In-Reply-To: <CADvuQRGGE9hcqO+NevwTdj97hmUe2eCPCO6mBT5B-oon0zaODw@mail.gmail.com>

On 9/4/2012 11:59 AM, Tommi Virtanen wrote:
> On Fri, Aug 31, 2012 at 11:58 PM, Andrew Thompson <andrewkt@aktzero.com> wrote:
>> Looking at old archives, I found this thread which shows that to mount a
>> pool as cephfs, it needs to be added to mds:
>>
>> http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/5685
>>
>> I started a `rados cppool data tempstore` a couple hours ago. When it
>> finishes, will I need to remove the current pool from mds somehow(other than
>> just deleting the pool)?
>>
>> Is `ceph mds add_data_pool <poolname>` still required? (It's not listed in
>> `ceph --help`.)
> If the pool you are trying to grow pg_num for really is a CephFS data
> pool, I fear a "rados cppool" is nowhere near enough to perform a
> migration. My understanding is that each of the inodes stored in
> cephfs/on ceph-mds'es knows what pool the file data resides in; you
> shoveling the objects into another pool with "rados cppool" doesn't
> change these pointers, removing the old pool will just break the
> filesystem.
>
> Before we go too far down this road: is your problem pool *really*
> being use as a cephfs data pool? Based on how it's not named "data"
> and you're just now asking about "ceph mds add_data_pool", it seems
> that's not likely..

Well, I guess it's time to wipe this cluster and start over.

Yes, it was my `data` pool I was trying to grow. After renaming and 
removing the original data pool, I can `ls` my folders/files, but not 
access them.

I attempted a tar backup beforehand, so unless it flaked out, I should 
be able to recover data.

I was concerned the small number of PGs created by default by mkcephfs 
would be an issue, so I was trying to up it a bit. I'm not going to have 
100+ OSDs or petabytes of data. I just want a relatively safe place to 
store my files that I can easily extend as needed.

So far, I'm 0 and 5... I keep blowing up the filesystem, one way or another.

-- 
Andrew Thompson
http://aktzero.com/


  reply	other threads:[~2012-09-04 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31 11:11 Very unbalanced storage Xiaopong Tran
2012-08-31 15:00 ` Andrew Thompson
2012-08-31 16:10   ` Sage Weil
2012-08-31 16:24     ` Andrew Thompson
2012-08-31 16:39       ` Gregory Farnum
2012-09-01  2:33         ` Xiaopong Tran
2012-09-01  3:07           ` Sage Weil
2012-08-31 16:43       ` Sage Weil
2012-08-31 16:05 ` Sage Weil
2012-09-01  2:52   ` Xiaopong Tran
2012-09-01  3:05     ` Sage Weil
2012-09-01  3:15       ` Xiaopong Tran
2012-09-01  6:58       ` Andrew Thompson
2012-09-04 15:59         ` Tommi Virtanen
2012-09-04 16:19           ` Andrew Thompson [this message]
2012-09-04 16:43             ` Sage Weil
2012-09-04 16:48             ` Tommi Virtanen

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=504629FB.30801@aktzero.com \
    --to=andrewkt@aktzero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tv@inktank.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.