Bug 459327 - Neither qtparted nor gparted recognize LVM2 partition as valid
Neither qtparted nor gparted recognize LVM2 partition as valid
Product: Fedora
Classification: Fedora
Component: qtparted (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Steven Pritchard
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-08-16 11:22 EDT by Robert Kochis
Modified: 2010-03-08 13:21 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 01:43:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Output from command fdisk and lvm (1.57 KB, text/plain)
2008-08-16 11:23 EDT, Robert Kochis
no flags Details
GParted screenshot (33.65 KB, image/png)
2008-08-16 11:24 EDT, Robert Kochis
no flags Details
QTparted screen shot (47.00 KB, image/png)
2008-08-16 11:24 EDT, Robert Kochis
no flags Details

  None (edit)
Description Robert Kochis 2008-08-16 11:22:16 EDT
Description of problem:
Neither qtparted nor gparted recognize LVM2 partition as valid, see attached screen shots

Version-Release number of selected component (if applicable):
gparted v0.3.7
qtparted v0.4.5-cvs
QT v3.3.8b
uname: Linux c-68-37-192-154.hsd1.nj.comcast.net #1 SMP Mon Aug 4 14:20:24 EDT 2008 i686 athlon i386 GNU/Linux

How reproducible:
I can reproduce this problem at will

Steps to Reproduce:
1.Open either qtparted or gparted 
2.Select drive /dev/sdb
Actual results:
LVM file system labeled as unknown

Expected results:
Some file system that is recognized

Additional info:
Comment 1 Robert Kochis 2008-08-16 11:23:31 EDT
Created attachment 314431 [details]
Output from command fdisk and lvm
Comment 2 Robert Kochis 2008-08-16 11:24:14 EDT
Created attachment 314432 [details]
GParted screenshot
Comment 3 Robert Kochis 2008-08-16 11:24:50 EDT
Created attachment 314433 [details]
QTparted screen shot
Comment 4 Bug Zapper 2008-11-26 06:06:13 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2009-01-09 01:43:50 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 6 nakieb 2010-03-08 13:21:29 EST
gparted in Fedora 12 does not support lvm2 , please reopen this bug ;as it still exists in a currently suporrted fedora .

Note You need to log in before you can comment on or make changes to this bug.