On Wed, 13 Apr 2016, Christian Balzer wrote: > > > Recently we discovered an issue with the long object name handling > > > that is not fixable without rewriting a significant chunk of > > > FileStores filename handling. (There is a limit in the amount of > > > xattr data ext4 can store in the inode, which causes problems in > > > LFNIndex.) > > We're only using cephfs so we shouldn't be affected by your discovered > > bug, right? > > > I don't use CephFS, but you should be able to tell this yourself by doing > a "rados -p <poolname> ls" on your data and metadata pools and see the > resulting name lengths. > However since you have so many objects, I'd do that on a test cluster, if > you have one. ^o^ > If CephFS is using the same/similar hashing to create object names as it > does with RBD images I'd imagine you're OK. All of CephFS's object names are short, like RBD's. For RBD, there is only one object per image that is long: rbd_id.$name. As long as your RBD image names are "short" (a max length of 256 chars is enough to make ext4 happy) you'll be fine. sage -- 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
