On Wed, 11 Sep 2013, Ugis wrote: > Hi, > > I wonder is ocfs2 suitable for hosting OSD data? > In ceph documentation only XFS, ext4 and btrfs are discussed, but > looking at ocfs2 feature list it theoretically also could host OSDs: > > Some of the notable features of the file system are: > Optimized Allocations (extents, reservations, sparse, unwritten > extents, punch holes) > REFLINKs (inode-based writeable snapshots) This is the one item on this list I see that the ceph-osds could take real advantage of; it would make object clones triggered by things like RBD snapshots faster. What is missing from this list that would be similarly (or more) useful is a volume/fs snapshot feature. Of course, ocfs2 only makes sense when run in a single-node mode underneath ceph-osds. sage > Indexed Directories > Metadata Checksums > Extended Attributes (unlimited number of attributes per inode) > Advanced Security (POSIX ACLs and SELinux) > User and Group Quotas > Variable Block and Cluster sizes > Journaling (Ordered and Writeback data journaling modes) > Endian and Architecture Neutral (x86, x86_64, ia64 and ppc64) > Buffered, Direct, Asynchronous, Splice and Memory Mapped I/Os > In-built Clusterstack with a Distributed Lock Manager > Cluster-aware Tools (mkfs, fsck, tunefs, etc.) > > ocfs2 can work in cluster mode but it can also work for single node. > > Just wondering would OSD work on ocfs2 and what would performance > characteristics be. > Any thoughts/experience? > > BR, > Ugis Racko > -- > 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 > > -- 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
