> If it's safe to defrag xfs while it's mounted in general, it's safe to > do it when an OSD is running. Xfs either keeps its promises as a > filesystem, or doesn't. That was my expectation. Thanks for the feedback. Just wanted to confirm. Also, I will report back on -o allocsize. Probably some time next week. Got a few other things to take care of first. Thanks again! - Travis On Fri, Sep 14, 2012 at 1:15 PM, Nick Couchman <Nick.Couchman@xxxxxxxxx> wrote: >> >>> While I'm talking about XFS... I know that RBD's use a default object >>> size of 4MB. I've stuck with that so far.. Would it be beneficial to >>> mount XFS with -o allocsize=4M ? What is the object size that gets >>> used for non-RBD cases -- i.e. just dumping objects into data pool? >> >> Don't know about -o allocsize -- benchmark it! > > ...and let us know what you come up with! I'm also using XFS for the underlying filesystem on which CEPH runs (and using RBD), and would be really interested to know if changing the alloc size improves performance! > > -Nick > > > > > -------- > > This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. -- 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
