Bug 145764

Summary: "lvm2" displays messages including wrong.
Product: Red Hat Enterprise Linux 4 Reporter: L3support <linux-sid>
Component: lvm2Assignee: Alasdair Kergon <agk>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 4.0CC: halligan, nagahama, ntachino
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-01-26 21:46:16 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: 180763    

Description L3support 2005-01-21 10:39:34 UTC
Description of problem:

"lvm2" displays messages including success,
when we do "pvremove" to ext3 filesystem.
-----------------------------------------------
# /usr/sbin/pvremove /dev/sdc1
No physical volume label read from /dev/sdc1
Labels on physical volume "/dev/sdc1" successfully wiped
-----------------------------------------------

Could you remove the success mesages ?  


Version-Release number of selected component (if applicable):
lvm2-2.00.25-1

How reproducible:
Always

Steps to Reproduce:
1.create ext3 filesystem
2.do pvremove to the filesystem created
3.
  
Actual results:
It displays success messages.

Expected results:
It does not display successs messages.

Additional info:

# parted /dev/sdc1
  :
(snip)
  :
Using /dev/sdc1
(parted) p
Disk geometry for /dev/sdc1: 0.000-99.983 megabytes
Disk label type: loop
Minor    Start       End     Filesystem  Flags
1          0.000     99.983  ext3

# /usr/sbin/pvremove /dev/sdc1
No physical volume label read from /dev/sdc1
Labels on physical volume "/dev/sdc1" successfully wiped

Comment 3 JoAnne K. Halligan 2005-01-26 21:46:16 UTC
This is currently normal and correct operation, so this bug report is being
closed as 'not a bug'. 

If this is a needed feature, please open a new feature request in Issue Tracker
using the new feature template. Be sure to provide all the required information. 

This request could then be reviewed for possible inclusion in RHEL4 U2 or later,
as that would also depend on when the feature request is received, the priority
of this request vs. other feature requests and based on LVM feature status at
that time. 

.