Bug 431474
| Summary: | pv*, vg*, and lv* commands can't handle special chars in LUN names | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Issue Tracker <tao> |
| Component: | lvm2 | Assignee: | Milan Broz <mbroz> |
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.6 | CC: | agk, dwysocha, edamato, heinzm, james.brown, jbrassow, mbroz, prockai, pvrabec |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2008-0776 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-07-24 20:07:54 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 391511 | ||
|
Comment 6
RHEL Program Management
2008-03-10 11:08:32 UTC
Description of problem: sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%"000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%&000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%*000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%.000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%<000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%@000' sudo /usr/sbin/pvcreate '/dev/mapper/SEMC_____SYMMETRIX______102623%%J000' - started to create the VG sudo /usr/sbin/vgcreate vgdgZGENES2 '/dev/mapper/SEMC_____SYMMETRIX______102623%%"000' - if I remember correctly the creation of the VG did not produce any error msg, but when I went to vgextend it I started seeing problems. sudo /usr/sbin/vgextend vgdgZGENES2 '/dev/mapper/SEMC_____SYMMETRIX______102623%%&000' sudo /usr/sbin/vgextend vgdgZGENES2 '/dev/mapper/SEMC_____SYMMETRIX______102623%%&000' - output from vgs -a showed lots of warnings/errors. I tried to disable, export, vgreduce --all, etc. but none of the commands would touch the VG sudo /usr/sbin/vgs -a sudo /usr/sbin/vgchange -a n vgdgZGENES2 - vgs -a shows issues with the VG, i.e. vgdgZGENES2, .. sudo /usr/sbin/vgs -a | more Parse error at line 15: unexpected token Couldn't read volume group metadata. Parse error at line 15: unexpected token Couldn't read volume group metadata. Volume group vgdgZGENES2 not found VG #PV #LV #SN Attr VSize VFree for_hrms_bckp 4 0 0 wz--n 272.31G 272.31G hrms_cnv_admin 1 1 0 wz--n 34.04G 14.04G etc... - pvs -a doesn't recognize that the VG is there either... $ sudo /usr/sbin/pvs -a | more Parse error at line 15: unexpected token Couldn't read volume group metadata. Parse error at line 15: unexpected token Couldn't read volume group metadata. get_pv_from_vg_by_id: vg_read failed to read VG vgdgZGENES2 PV VG Fmt Attr PSize PFree /dev/mapper/SEMC_____SYMMETRIX______102623%%"000 lvm2 -- 68.08G 68.08G etc ...... Fixed in upstream CVS, will be in next rebase (RHEL 4.7), status set to POST. fix verified in lvm2-2.02.37-3.el4. /dev/sdc#_%($" taft lvm2 a- 135.66G 134.66G 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 therefore 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-2008-0776.html |