Repository navigation
DRBD Volume above 4TB not working #312
Description
Activity
- added this to the milestone
on Jun 22, 2017 Same issue on Ganeti 2.6.x on Gentoo Linux. This issue could have a solution if we have a way to tell ganeti to use drbd with internal meetadata. That shoud remove this 4TB limitation at disk creation time.Originally added on 2013-02-02 14:18:33 +0000 UTC.
The problem with internal metadata is that it makes disk resizes and conversion impossible, since now the drbd volume is not a "raw" image. This is the reason why we did not implement internal metadata so far. It could be possible to use internal metadata, but then this would have to be tracked, and all the above operation disallowed. Hmm…Originally added on 2013-02-04 08:42:00 +0000 UTC.
Which would be possible if we used a disk parameter and documented that enabling it loses support for resize and conversion operations. (of course code-wise this shouldn't be hardcoded then, but asked by cmdlib to each drbd device, to avoid a layering violation). I think if someone would contribute this patch we could accept it, what do you think? Thanks, GuidoOriginally added on 2013-02-15 14:48:46 +0000 UTC.
Yes, sure. But I don't think it'll be a trivial patch…Originally added on 2013-02-15 14:54:46 +0000 UTC.
As discussed yesterday on IRC an alternative would be to use flexible external metadata, which allows a metadata size proportional to the data size, instead of exactly 128M, and thus scalable over 4T. What do you think?Originally added on 2013-03-23 07:29:02 +0000 UTC.
-- Empty comment --Originally added on 2013-05-03 09:27:54 +0000 UTC.
Changed State: Accepted
Added to Milestone: Release2.9Ganeti uses for DRBD 8.4 (supported as of 2.9) flexible external metadata per default. It does not, however, compute the metadata size based on the actual disk size. So there is still work to do in order to support disks > 4TB. I'm unassigning myself from this bug, as I'm not actively working on it.Originally added on 2013-06-28 11:47:48 +0000 UTC.
Move non-critical bugs scheduled for 2.8 or 2.9 to 2.11, as in those versions only critical bug fixes will be integrated.Originally added on 2013-10-30 09:48:16 +0000 UTC.
Added to Milestone: Release2.11
Removed from Milestone: Release2.9is there any current workaround for this? i ran into this issue today. :)Originally added on 2014-02-06 07:36:12 +0000 UTC.
A quick and dirty workaround is to change the value of the DRBD_META_SIZE constant in constants.py (or _constants.py on newer Ganeti versions) to something above 128MB (double it for 8TB, for example). Make sure to change it to the same value on all nodes in your cluster. While this would allow you to create disks bigger than 4TB, I'm not quite sure which problems you could run into with existing disks. Make sure to test such a workaround before using it in production.Originally added on 2014-02-06 09:12:44 +0000 UTC.
Another dirty work-around we use is to create several virtual disks of 4TB each for the same instance and merge them in the instance with LVM. It's been working great so far with 12TB+ devices without any modification in the Ganeti code. We are still waiting for this issue to be handled as >4TB devices are getting more and more common those days.Originally added on 2014-02-06 09:18:30 +0000 UTC.
I'm changing the DRBD_META_SIZE value of /usr/share/ganeti/2.11/ganeti/constants.py each time I need a volume > 4TB and reverse the change after. It's really annoying. I think the simple way is to calculate DRBD_META_SIZE based on the disk size to be created with a minimum of 128 MB like actually fixed. if DRBD_DISK_SIZE > 4TB then DRBD_META_SIZE = DRBD_DISK_SIZE/32 This way we could have any size of volume. I wonder even if we can use DRBD_DISK_SIZE/32 for any size of drbd disk to get a low space overhead in case of little volume usage.Originally added on 2014-12-03 17:48:30 +0000 UTC.
I've searched what is the good size to have for metadata disk and it's really well explained on linbit drbd documentation: http://drbd.linbit.com/users-guide-8.4/ch-internals.html#s-meta-data-size So their estimation calcul is really corrrect even if we could use the exact calcul. The maximum overrate by estimation is < 1Mb. So their estimation is that a volume of X megabytes need a medata disk size of Y megabytes like Y=X/32768+1 Some results as example (with 1Mb minimum due by estimation) 1 Gb => 1 Mb 10 Gb => 1Mb 100 Go => 4Mb 1To => 33Mb 4To => 129Mb 10 To => 321 Mb 16 To => 513 Mb So actually ganeti use a 128Mb metadata disk size that limit disk size to ~4 Tb and waste a lot of medata for little disk size that are really common in real usage. So a great patch would be to use this formula to calculate the metadata disk size instead the 128Mb fixed size that waste disk storage and limit disk size to ~4To.Originally added on 2015-02-13 14:54:18 +0000 UTC.
I agree that we need to do the change in a way that doesn't require altering all existing disks, or it will be a huge burden to upgrade. The other issue is: how does this formula work when increasing disk sizes? We'll need to make sure to enlarge metadata disks as well, then, so that it works. (or not to even try if the requested new disk size would exceed the current metadata allowed size). As long as these two issues are contemplated, we'd be happy to accept patches in the directions proposed in this thread. Thanks, GuidoOriginally added on 2015-04-15 13:03:05 +0000 UTC.
Linbit DRBD documentation speaks about growth operation: https://drbd.linbit.com/users-guide/s-resizing.html So it's more complex in case of internal metadata (need to move the metadata to the new volume end). In case of external metadata, extend it offline seems trivial: "When the backing block devices on both nodes are grown while DRBD is inactive, and the DRBD resource is using external meta data, then the new size is recognized automatically. No administrative intervention is necessary. The DRBD device will have the new size after the next activation of DRBD on both nodes and a successful establishment of a network connection." Extend it online, a simple drbd resize seems to do it so not so complex.Originally added on 2015-05-22 17:06:46 +0000 UTC.
Find as attachment a bash script that we use on a 2 node production server to use DRBD disks > 4 TB. usage: gnt-drbd-meta-disk-size get | set SIZE[MGT] get or set ganeti DRBD meta disk size computed from DRBD disk size - SIZE is the DRBD disk size expressed in MiB by default - M/G/T suffixes can be used for MiB/GiB/TiB - DRBD meta disk size < 128 MiB use the 128MiB default of ganeti This script can be used to set temporay DRBD meta disk size for: - instance creation using only disks > 4064 GB - adding a disk > 4064 GB to an instance using already ganeti default DRBD meta size that won't be relocated away from initial nodes WARNING: - both DRBD nodes involved need to use the same DRBD meta disk size for disk creation/addition - all DRBD nodes involved in DRBD instance relocation need to use the same DRBD meta disk size - This script can't handle instance relocation with instance using several DRBD disk using different DRBD meta disk size - Doesn't have been tested with backup/exportOriginally added on 2015-09-18 11:49:55 +0000 UTC.
Attachments:
gnt-drbd-meta-disk-sizefeature: storage/drbd
Originally reported of Google Code with ID 256.
Originally added on 2012-08-09 09:18:29 +0000 UTC.