Bug 202232
| Summary: | vgchange -p isn't implemented | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Issue Tracker <tao> |
| Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.0 | CC: | dwysocha, mbroz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2007-0287 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-05-08 00:03:44 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: | |||
|
Description
Issue Tracker
2006-08-11 18:04:34 UTC
man page for vgcreate states:
-p, --maxphysicalvolumes MaxPhysicalVolumes
Sets the maximum number of physical volumes that can belong to this volume group. The setting can be changed with vgchange.
man page for vgchange and 'vgchange --help' clearly doesn't have an option for it. The only way I could find to alter this setting is to start over and recreate your VG from scratch.
This event sent from IssueTracker by jwhiter [Support Engineering Group]
issue 99611
File uploaded: lvm_manpage.patch This event sent from IssueTracker by jwhiter [Support Engineering Group] issue 99611 it_file 67396 Patch to fix the manpage. This event sent from IssueTracker by jwhiter [Support Engineering Group] issue 99611 vgchange -p ought to work committed upstream BTW comment #1 - you could have used vgcfgbackup - edited max_pv to the new value - then vgcfgrestore comment #5 was ambiguous: the patch I've committed is to implement vgchange -p Re: latest bug 202232 comment- Interesting, so is "vgchange -p" something that could happen in a later RHEL4 update as a feature, or should we not hold our breath? unless objections are raised, it should get picked up in the next update This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. lvm2-2.02.14-1 built fix verified in lvm2-2.02.17-1. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0287.html |