Inode size is not configurable

Bug #1826552 reported by Tytus Kurek
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Swift Storage Charm
Fix Released
Wishlist
Tytus Kurek

Bug Description

It looks like at the moment the XFS inode size is not configurable, as it's hard-coded in charmhelpers:

https://github.com/juju/charm-helpers/blob/master/charmhelpers/contrib/storage/linux/utils.py#L113

As a result it is not possible to set the desired inode size when initializing the block devices for Swift.

It has been observed that with the default inode size of 1024 it is not possible to store 20M of containers on a cluster consisting of 6 storage nodes, each with 2 * 200 GB SSDs. The replication factor used was 4.

Changed in charm-swift-storage:
status: New → Triaged
importance: Undecided → Wishlist
assignee: nobody → Sahid Orentino (sahid-ferdjaoui)
Revision history for this message
Sahid Orentino (sahid-ferdjaoui) wrote :

A PR has been proposed in charm-helpers, let see how it goes:

  https://github.com/juju/charm-helpers/pull/314

Revision history for this message
Tytus Kurek (tkurek) wrote :

There is already another PR in place:

https://github.com/juju/charm-helpers/pull/313

Plus there is a patch for the swift-storage charm:

https://review.opendev.org/#/c/656265/

Revision history for this message
Sahid Orentino (sahid-ferdjaoui) wrote :

Tytus, there is a field which is indicating who is working on an issue "Assigned to". That one is used to avoid any waste of time by having several people working on it.

If in the future you want to report a bug and in addition work on it (which is great) please consider to mark yourself on it, or if you find somebody who has already indicated that is is going to work on it, don't compete with him, please communicate to him that you also plan to work on it or just avoid that, there are plenty of bugs not addressed :-)

Thanks,
s.

Changed in charm-swift-storage:
assignee: Sahid Orentino (sahid-ferdjaoui) → Tytus Kurek (tkurek)
Revision history for this message
Tytus Kurek (tkurek) wrote :

Sahid,

Thank you very much for your work on that. Apologies for not marking myself as an assignee.

Regards

Tytus

Tytus Kurek (tkurek)
tags: removed: field-medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-swift-storage (master)

Fix proposed to branch: master
Review: https://review.opendev.org/665652

Changed in charm-swift-storage:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-swift-storage (master)

Reviewed: https://review.opendev.org/665652
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=04a0fc47b0a66adcaba34df0c50ccc956cd95922
Submitter: Zuul
Branch: master

commit 04a0fc47b0a66adcaba34df0c50ccc956cd95922
Author: Tytus Kurek <email address hidden>
Date: Mon Jun 17 12:11:35 2019 +0000

    Sync charm-helpers for lp1826552

    Ensure that charmhelpers directory is up to date.

    Change-Id: Ib1c419a0c9710b4489777471226ccd680408f8fe
    Needed-By: If621587a02746876ee6c35d7af2e878dbc2ac8ef
    Partial-Bug: 1826552

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.opendev.org/656265
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=dfc0e8bfe2707b5654f84a45de4ad7fb7075ddc6
Submitter: Zuul
Branch: master

commit dfc0e8bfe2707b5654f84a45de4ad7fb7075ddc6
Author: Tytus Kurek <email address hidden>
Date: Mon Jul 1 07:41:39 2019 +0000

    Make XFS inode size configurable

    Make XFS inode size configurable, so that it could be set to the
    desired value, if different than default 1024.

    Change-Id: If621587a02746876ee6c35d7af2e878dbc2ac8ef
    Closes-Bug: 1826552

Changed in charm-swift-storage:
status: In Progress → Fix Committed
James Page (james-page)
Changed in charm-swift-storage:
milestone: none → 19.07
David Ames (thedac)
Changed in charm-swift-storage:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.