On Tuesday, May 22, 2012 at 2:31 PM, Grant Ashman wrote: > Greg Farnum <greg <at> inktank.com (http://inktank.com)> writes: > > Oh, I got this conversation confused with another one. > > You also need to specify the pool as a valid pool to > > store filesystem data in, if you haven't done that already: > > "ceph mds add_data_pool <poolname>" > > > > Thanks Greg, > > However, I still get the same error :( > When I specify the add data pool I get the following: > (with or without the additional values) > > root@dsan-test:~# ceph mds add_data_pool backup > added data pool 0 to mdsmap Okay, that's not right — it should say pool 3. According to the docs I found you ran that correctly, but let's try running "ceph mds add_data_pool 3" and see if that resolves correctly. *goes to look at code* Argh, yep, it's expecting a pool ID, not a pool name. Gah. > root@dsan-test:~# cephfs /mnt/ceph-backup set_layout -p 3 > Error setting layout: Invalid argument > > Seems to be pointing at pool 0 instead of pool 3 like it should? > > Sorry if this has all been covered before, I've not found any > resolution and the ability to mount specific pools I.E "data" > for production data and "backup" for 1N backup data is a huge > priority to begin using Ceph. No problem — we haven't generated docs for this yet and obviously we need to at some point. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
