On Wed, Aug 22, 2012 at 12:12 PM, Dieter Kasper (KD) <d.kasper@xxxxxxxxxxxx> wrote: >> Your journal is a file on a btrfs partition. That is probably a bad >> idea for performance. I'd recommend partitioning the drive and using >> partitions as journals directly. > can you please teach me how to use the right parameter(s) to realize 'journal on block-dev' ? Replacing the example paths, use "sudo parted /dev/sdg" or "gksu gparted /dev/sdg", create partitions, set osd journal to point to a block device for a partition. [osd.42] osd journal = /dev/sdg4 > It looks like something is not OK during 'mkcephfs -a -c /etc/ceph/ceph.conf --mkbtrfs' > (see below) Try running it with -x for any chance of extracting debuggable information from the monster. > Scanning for Btrfs filesystems > HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device > 2012-08-22 21:04:01.519073 7fb475e8b780 -1 journal check: ondisk fsid 8b18c558-8b40-4b07-aa66-61fecb4dd89d doesn't match expected ee0b8bf1-dd4a-459e-a218-3f590f9a8c16, invalid (someone else's?) journal Based on that, my best guess would be that you're seeing a journal from an old run -- perhaps you need to explicitly clear out the block device contents.. Frankly, you should not use btrfs devs. Any convenience you may gain is more than doubly offset by pains exactly like these. -- 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
