Bug 1591180 – VDO volume is unable to growPhysical after device resize performed in previous boot [rhel-7.5.z]

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1591180 - VDO volume is unable to growPhysical after device resize performed in previous boot [rhel-7.5.z]

Summary:	VDO volume is unable to growPhysical after device resize performed in previou...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	kmod-kvdo (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	Unspecified Unspecified

Priority	high Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Matthew Sakai
QA Contact:	Jakub Krysl
Docs Contact:	Marek Suchanek

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	1582647
Blocks:
	Show dependency tree / graph

Reported:	2018-06-14 04:06 EDT by Oneata Mircea Teodor
Modified:	2018-08-16 10:19 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	6.1.0.175
Doc Type:	If docs needed, set a value
Doc Text:	Previously, VDO volumes were unable to grow if the underlying block device increased in size while the system was powered off or the VDO volume was offline. With this update, VDO correctly checks the requested size and the current size of the device, and, as a result, the described problem no longer occurs.
Story Points:	---
Clone Of:	1582647
Environment:
Last Closed:	2018-08-16 10:19:04 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:2450	None	None	None	2018-08-16 10:19 EDT

Groups: None (edit)

Description Oneata Mircea Teodor 2018-06-14 04:06:29 EDT

This bug has been copied from bug #1582647 and has been proposed to be backported to 7.5 z-stream (EUS).

Comment 3 Jakub Krysl 2018-07-23 08:49:26 EDT

kmod-kvdo-6.1.0.181-17.el7_5
kernel-3.10.0-862.10.2.el7

# vdo create --verbose --name vdo --device /dev/sdb1
Creating VDO vdo
    grep MemAvailable /proc/meminfo
    pvcreate -qq --test /dev/sdb1
    modprobe kvdo
    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdb1
    vdodumpconfig /dev/sdb1
Starting VDO vdo
    dmsetup status vdo
    grep MemAvailable /proc/meminfo
    modprobe kvdo
    vdodumpconfig /dev/sdb1
    dmsetup create vdo --uuid VDO-dd46da51-a9e4-4c3a-aacd-123c830b9fc6 --table '0 75351184 vdo /dev/sdb1 4096 disabled 0 32768 16380 on auto vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
    dmsetup status vdo
Starting compression on VDO vdo
    dmsetup message vdo 0 compression on
    dmsetup status vdo
    dmsetup status vdo
VDO instance 0 volume is ready at /dev/mapper/vdo
# vdo stop --name vdo
Stopping VDO vdo
# parted /dev/sdb resizePart 1 50GiB
Information: You may need to update /etc/fstab.
# vdo start --name vdo
Starting VDO vdo
Starting compression on VDO vdo
VDO instance 1 volume is ready at /dev/mapper/vdo
# vdo status --name vdo | grep 'Physical size'
    Physical size: 41943036K
# vdo growPhysical --name vdo --verbose
    dmsetup status vdo
    dmsetup message vdo 0 prepareToGrowPhysical
    dmsetup suspend vdo
    dmsetup message vdo 0 growPhysical
    vdodumpconfig /dev/sdb1
    dmsetup resume vdo
# vdo status --name vdo | grep 'Physical size'
    Physical size: 50G

Comment 7 errata-xmlrpc 2018-08-16 10:19:04 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2450

Note You need to log in before you can comment on or make changes to this bug.