Bug 2096493

Summary: [DDF] According to https://bugzilla.redhat.com/show_bug.cgi?id=1649086#c25, it appears to me that the option is no
Product: Red Hat Enterprise Linux 8 Reporter: Direct Docs Feedback <ddf-bot>
Component: DocumentationAssignee: Steven J. Levine <slevine>
Documentation sub component: DDF QA Contact:
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: unspecified    
Priority: medium CC: rhel-docs, takashi.nagata, teigland
Version: 8.0Keywords: Documentation
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-14 20:34:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 3 David Teigland 2022-06-14 16:15:31 UTC
My recollection is that the original procedure (8.0) was:
1. lvextend --lockopt skiplv LV (on one node)
2. lvchange --refresh LV (on all nodes)
3. gfs2_grow (on one node)

Then the more automated procedure (8.1+) became:
1. lvextend LV (on one node)
2. gfs2_grow (on one node)

For the new procedure, --lockopt skiplv should be removed.  The document seems to want to keep some info about the original procedure, though (see step 4.)

Comment 4 Steven J. Levine 2022-06-14 17:04:11 UTC
Dave:  Yes, I left in the 8.0 steps when we did the 8.1 update because not everybody upgrades and the one manual has to cover both procedures. That's been my practice since we stopped having separate manuals for every point release (which was many many years ago), and to the extent I've gotten feedback people seem to want me to keep doing that (it's not, technically, my department's policy -- but support seems to appreciate this).

At this point it might be safe to remove the "for 8.0" versions, but to be consistent I'd like to leave it in.  I'll remove the --lockopt skiplv option from the main procedure, noting this as 8.1 and later (the way we do for the refresh part), and note that the 8.0 command as we do for refresh.

Comment 8 Steven J. Levine 2022-06-14 20:34:40 UTC
The procedure for growing a GFS2 file system has now been updated on the Red Hat Customer Portal to indicate that for RHEL 8.1 and later you no longer need to specify the skiplv lock option:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_gfs2_file_systems/index#proc_growing-gfs2-filesystem-creating-mounting-gfs2

The RHEL 9 version of the manual has also been updated so that it no longer includes the skiplv lock option in the example lvextend command.

Thanks for pointing this out.