Cinder with lvm should not have 16TB limit

Bug #1530243 reported by Victor Denisov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Python (Deprecated)
7.0.x
Confirmed
High
Alexey Stupnikov
8.0.x
Confirmed
Medium
Alexey Stupnikov
Future
Confirmed
Medium
Fuel Python (Deprecated)

Bug Description

This could still be a bug.

LVM on a 64-bit CPU/Kernel should NOT have a 16TB limit. It should have a 8EB limit (exabyte).

https://www.redhat.com/archives/linux-lvm/2010-March/msg00007.html

Please pass this by the development team. I think the 16T limit in /usr/lib/python2.6/site-packages/fuel_agent/drivers/ks_spaces_validator.py was based on older 32-bit CPU/kernel.

tags: added: area-linux area-provisioning area-python fuel-agent
Changed in fuel:
milestone: none → 9.0
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Fuel Python Team (fuel-python)
tags: added: area-mos
Changed in fuel:
status: Confirmed → Invalid
status: Invalid → Confirmed
Revision history for this message
Roman Rufanov (rrufanov) wrote :

customer found on MOS 7. 0 - need fix.

tags: added: customer-found support
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

could it duplicate this one https://bugs.launchpad.net/mos/+bug/1526845 ?

https://github.com/openstack/fuel-agent/blob/master/fuel_agent/drivers/ks_spaces_validator.py#L144

actually, 'Root file system must be less than 16T' is not true.

it seems that we could only resize rootfs image in 1024 times, so as was being initially made 8G it could only grows to 8T at most.

https://github.com/openstack/fuel-agent/blob/master/fuel_agent/manager.py#L97-L104

what type of fix is expected?

these are limitations of e2fsprogs package shipped with centos6.x

Revision history for this message
Alexander Gordeev (a-gordeev) wrote :

so yes, i was able to take a look into original ticket and according to fuel-agent logs it was:

2015-12-28 21:53:57 INFO fuel_agent.cmd.agent KeyError: 'mount'

therefore, it turned out to be a duplicate of https://bugs.launchpad.net/mos/+bug/1526845

however, https://bugs.launchpad.net/mos/+bug/1526845 should have been assigned to Fuel project, not MOS.

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.