RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1535127 - vdo growLogical changes write policy to the same
Summary: vdo growLogical changes write policy to the same
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Sweet Tea Dorminy
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-16 16:35 UTC by Jakub Krysl
Modified: 2019-03-06 02:06 UTC (History)
5 users (show)

Fixed In Version: 6.1.0.144
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 15:49:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0871 0 None None None 2018-04-10 15:49:49 UTC

Description Jakub Krysl 2018-01-16 16:35:05 UTC 
Description of problem:
When increasing logical size of vdo using command 'vdo growLogical', there is a message in /var/log/messages about changing the write policy.

[ 6083.403997] kvdo134:dmsetup: Preparing to resize logical to 107374182400                              
[ 6083.433140] kvdo134:dmsetup: Done preparing to resize logical                                         
[ 6083.442024] kvdo134:dmsetup: suspending device 'vdo'                                                  
[ 6083.562637] kvdo134:dmsetup: device 'vdo' suspended                                                                       
[ 6083.572911] kvdo134:dmsetup: modifying device 'vdo' (ti=ffffbc26dfffe040) write policy async          
[ 6083.581383] kvdo134:dmsetup: Resizing logical to 107374182400                                                      
[ 6083.587632] kvdo134:dmsetup: Logical blocks now 107374182400                                          
[ 6083.596133] kvdo134:dmsetup: resuming device 'vdo'                                                    
[ 6083.600952] kvdo134:dmsetup: device 'vdo' resumed    

This write policy is the same as the one specified when vdo is create (so either 'auto' or the one used with --writePolicy), so the impact appears to be none and this change appears to be pointless and completely irrelevant to changing logical size.

Version-Release number of selected component (if applicable):
vdo-6.1.0.114-14

How reproducible:
100%

Steps to Reproduce:
1. vdo create --name vdo --device /dev/sdc
2. vdo growLogical --name vdo --vdoLogicalSize 1P
3. check /war/log/messages

Actual results:
write policy is modified to the same

Expected results:
no write policy modification (unless necessary)

Additional info:
Comment 2 Andy Walsh 2018-01-16 16:47:47 UTC 
My initial thought here is that it's not changing the write policy.  I think the message is just indicating facts.

"I am modifying device vdo"
"device vdo has write policy async"

I think it could be more clear, like saying "modifying device 'vdo' (ti=...) (write policy: async)"

Or we leave off the write policy on this message (and introduce a new message if we perform a 'changeWritePolicy' operatoin?
Comment 5 Jakub Krysl 2018-02-09 10:59:58 UTC 
vdo-6.1.0.146-16:
# vdo growLogical --name vdo --vdoLogicalSize 1P
[ 5410.210297] kvdo12:dmsetup: Preparing to resize logical to 274877906944
[ 5410.570064] kvdo12:dmsetup: Done preparing to resize logical
[ 5410.603461] kvdo12:dmsetup: suspending device 'vdo'
[ 5410.739481] kvdo12:dmsetup: device 'vdo' suspended
[ 5410.770707] kvdo12:dmsetup: modifying device 'vdo'
[ 5410.793140] kvdo12:dmsetup: Using mode sync automatically.
[ 5410.818824] kvdo12:dmsetup: Resizing logical to 274877906944
[ 5410.862248] kvdo12:dmsetup: Logical blocks now 274877906944
[ 5410.892681] kvdo12:dmsetup: resuming device 'vdo'
[ 5410.914549] kvdo12:dmsetup: device 'vdo' resumed

# vdo changeWritePolicy --name vdo --writePolicy sync
[ 5495.639679] kvdo12:dmsetup: device 'vdo' suspended
[ 5495.673215] kvdo12:dmsetup: modifying device 'vdo'
[ 5495.697259] kvdo12:dmsetup: Modifying device 'vdo' write policy from async to sync
[ 5495.741212] kvdo12:dmsetup: resuming device 'vdo'
[ 5495.763077] kvdo12:dmsetup: device 'vdo' resumed
Comment 8 errata-xmlrpc 2018-04-10 15:49:25 UTC 
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/RHEA-2018:0871
Note You need to log in before you can comment on or make changes to this bug.