MKCEPHFS Use __authentication

creating a new file system

The ' MKCEPHFS ' script is used to create a new cluster file system. The basic syntax is

/USR/SBIN/MKCEPHFS [-C ceph.conf] [-a|--allhosts] [--mkbtrfs] [k-admin.keyring]

Be VERY VERY careful. Minimal CHECKS ARE MADE to avoid the old DATA.

the-a or--allhosts flag specifies that mkfs-related steps is should on taken hosts the _all_. This would use SSH to set up remote hosts. If you don ' t want for this, and the Mkcephfs man page.

The --mkbtrfs option would create a new Btrfs file system for each OSD and mount it for you. It requires the ' btrfs devs ' and ' btrfs path ' (when it differs from the ' OSD Data ' directory) are specified. Note that NO SAFETY CHECKS ARE MADE yet; Be careful with the ' Btrfs devs ' option!

To use EXT4 instead of btrfs, comment out "Btrfs devs" in ceph.conf, point "OSD data" to a already mounted EXT4 partition and use MKCEPHFS without--mkbtrfs. The EXT4 partition must be mounted with-o user_xattr or else mkcephfs'll fail. Also using noatime,nodiratime boosts performance at no cost. When using EXT4, you should disable the EXT4 journal, because Ceph the does of its own. This is the'll boost performance.

Creating a new file system on a EXT4 partition that already contains data, would invoke RM-RF to delete the data. If There is a lot to it, it might seem as if MKCEPHFS is hanging when it actually isn't.

If for any reason your are re-creating the file system on a pre-existing cluster, recreating the journals too save Yo U some grief.

the-k admin.keyring option lets you specify where MKCEPHFS puts your Master admin key file, which is necessary To administer the cluster the have authentication enabled. Note this various keys are generated even if authentication is disabled, so this it can be enabled later. SSH Keys

You'll need to set up SSH keys and so this machine you are running MKCEPHFS on (master) can ssh into to other nodes (Slav e) as root. The usual way to does this (assuming you don ' t already have any keys or Authorized_keys set up):

ssh-keygen-d




Generating Public/private DSA key pair.
Enter file in which to save the key (/ROOT/.SSH/ID_DSA): 
Enter passphrase (empty for no passphrase): 
enter same PA Ssphrase again: 
Your identification has been saved.
Your public key has been saved in/root/.ssh/id_dsa.pub.

Then for each other host,

# Ssh-copy-id Root@slave

Example

Mkcephfs-c/etc/ceph/ceph.conf-a--mkbtrfs-k/etc/ceph/keyring.bin