queue design • Memory zero copy design • Cloud native supportCloud native for CurveBS • CSI plugin for CurveBS • Deploy CurveBS as container service (in Plan) • Config CurveBS by (Cluster and data consistency • POSIX-compatiable • Cloud native supportCloud native plan for CurveFS • CSI plugin for CurveFS (in Plan) • Deploy CurveFS as container service (in Plan) • Config CurveFS by (cluster POSIX-compatible and mountable • Cache support on CurveFS • CurveFS cloud native support • csi plugin for CurveFS • support operator capability level 2: automated application provisioning and configuration

and ETCD server • Replication between CurveFS configured with CRDsFeature list for CurveBS • CSI plugin for CurveBS • CurveBS (Cluster and Pool CRDs) • chunk server pods can run on arbitrary PVs(local chunkserver on PVCs to automatically grow when the cluster is nearly fullFeature list for CurveFS • CSI plugin for CurveFS • CurveFS (cluster and storage pools) CRDs • Dynamic Volume Provisioning for CurveFS

这种情况下，就会存在nlink未被减1的情况，当所有硬链接都被删除后，就会出现孤儿inode。 moosefs由于只有一个mds节点看，所以不存在这个问题。 chubaofs的解决方案是： 在Delete_ll（api.go） 函数中，在delete dentry后有一段注释如下: // dentry is deleted successfully but inode is not, still returns success

netease.com/team/km_curve/article/27909 性能对比 并对以上文件系统在相同环境进行了元数据节点性能测试： 。测试结果c开发的moosefs和fastcfs元数据性能远优于go开发的chubaofs和c开发的cephfs，理论上分析这个结果是合理的，分布式的元数据设 调研测试 计会涉及到多次rpc的交互。这里需要确认的一点是：我们需要怎样的元数据节点的性能？ 可行性分析

partition管理的元数据，data partition管理数据。meta partition管理inode和dentry信息。 创建一个文件系统时，如何初始化meta partition？ master\cluster.go， chubaofs的文件系统使用volume的来表示，在创建一个文件系统的时候，会创建3个meta partition和10个data partition。chubaofs的data partit