Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 10-27-2003, 09:59 AM   #1
LQ Newbie
Registered: Oct 2003
Posts: 5

Rep: Reputation: 0
Question RH9 lvm and fdisk forgetting about hdb partitions


RedHat 9
kernel 2.4.20-20.9 (received from up2date)
fdisk v2.11y

Using disk druid I've set up a LVM partition. This works with no issues.
I've added /dev/hdb and have subsequently have used fdisk to create a 2nd LVM partition. This all worked exactly as expected, fdisk -> pvcreate -> vgcreate -> lvcreate -> mke2fs -j.

[ a number of reboots happened around here ]

Today I want to create another partition to use some of the rest of the 6GB on /dev/hdb and when I run fdisk -l to check the current status I get the message below for /dev/hdb.

[fdisk -l]
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 274 2096482+ 83 Linux
/dev/hda3 275 338 514080 8e Linux LVM
/dev/hda4 339 784 3582495 5 Extended
/dev/hda5 339 402 514048+ 8e Linux LVM
/dev/hda6 403 426 192748+ 82 Linux swap

Disk /dev/hdb: 9115 MB, 9115361280 bytes <---
255 heads, 63 sectors/track, 1108 cylinders <---
Units = cylinders of 16065 * 512 = 8225280 bytes <---

Disk /dev/hdb doesn't contain a valid partition table <---***

however I have an LVM volume on hdb1 which is still active and happy even though according to fdisk it doesn't exist!

[vgdisplay -v Volume01]
--- Volume group ---
VG Name Volume01
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 256
Cur LV 1
Open LV 1
MAX LV Size 255.99 GB
Max PV 256
Cur PV 1
Act PV 1
VG Size 1.90 GB
PE Size 4 MB
Total PE 487
Alloc PE / Size 487 / 1.90 GB
Free PE / Size 0 / 0
VG UUID eKR9gV-p2Xr-cLCH-5O50-Or1D-xZXX-hnZZT9

--- Logical volume ---
LV Name /dev/Volume01/datalv2
VG Name Volume01
LV Write Access read/write
LV Status available
LV # 1
# open 1
LV Size 1.90 GB
Current LE 487
Allocated LE 487
Allocation next free
Read ahead sectors 1024
Block device 58:1

--- Physical volumes ---
PV Name (#) /dev/hdb1 (1) <---
PV Status available / allocatable
Total PE / Free PE 487 / 0

I wondered if this was something to do with VGDA corruption although this is unlikely as it is a partition rather than a whole disk so did a vgexport and vgimport. It worked, my data is intact and I can write to the filesystem.

Have I misunderstood the way the LVM works? Afaiac I would expect to see /dev/hdb# so that I won't accidentally overwrite it with standard Linux partitions.

Has anyone seen this before?

Any suggestions???

Thanks in advance



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
weird fdisk problem (Fdisk unable to see winxp partitions) khidot Slackware - Installation 5 04-07-2007 09:26 PM
Convert LVM volumes to primary partitions? MHouse Linux - Software 0 02-03-2005 10:34 PM
fdisk unable to open hdb dr_zayus69 Linux - Hardware 2 01-11-2005 08:04 PM
How do you make three partitions using fdisk? inward_eye Linux - Hardware 9 04-20-2004 03:13 PM
Partitions and LVM in a new computer Borelian Linux - General 1 10-31-2003 11:30 AM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 03:38 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration