Yes, all these "personality tests" are a bit twisted, but I thought this computer-based one would be good for a laugh. It turns out I'm Palm OS; I don't know whether to think it's an insult or not, I'm just glad I didn't get Windows ME!
src="http://www.bbspot.com/Images/News_Features/2003/01/os_quiz/palm.jpg" width="300" height="90"
border="0" alt="You are Palm OS. Punctual, straightforward and very useful. Your mother wants you to do more with your life like your cousin Wince, but you're happy with who you are.">
Which OS are You?
Wednesday, May 31, 2006
Monday, May 08, 2006
LVM woes
Anyone have any ideas about the following?
I'm having a bit of trouble getting a second hard drive to be
mapped by LVM. I think I've got things to the point that I'm just
missing a minor step. Here's the skinny:
1) Initially someone imaged a 120GB hard drive with a 60GB image. I
created a 60GB image and joined it to the other 60GB image.
Everything was cool... I had about 106GB for /home.
2) I just added a second drive, an 80GB drive that I also want mapped to home.
Below is the mess I've created:
--[snip]------------------------------------------
--- Physical volume ---
PV Name /dev/hda5
VG Name VolGroup01
PV Size 52.66 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 1685
Free PE 0
Allocated PE 1685
PV UUID 57X3AO-NXrE-1Hs1-b2eF-3asW-LtX5-mjRlns
--- Physical volume ---
PV Name /dev/hda6
VG Name VolGroup01
PV Size 54.50 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 1744
Free PE 0
Allocated PE 1744
PV UUID vYcDST-5ZkY-6TU3-NtvY-nFNN-dywA-O3OrZC
--- Physical volume ---
PV Name /dev/hdb1
VG Name VolGroup01
PV Size 76.31 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 2442
Free PE 10
Allocated PE 2432
PV UUID fkslom-Pf5T-tOUc-mPOq-WSXF-U5B6-YaDuN2
--- NEW Physical volume ---
PV Name /dev/hdb
VG Name
PV Size 76.34 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID lRvY0d-5lgb-ZfCy-lwIu-Nkwt-LI1p-1FsrBX
--- Logical volume ---
LV Name /dev/VolGroup01/LogVol01
VG Name VolGroup01
LV UUID dPPB8b-ASXB-3Ha4-mSlj-l648-UTQG-P7Fiz8
LV Write Access read/write
LV Status available
# open 1
LV Size 183.16 GB
Current LE 5861
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:0
--- Volume group ---
VG Name VolGroup01
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 3
Act PV 3
VG Size 183.47 GB
PE Size 32.00 MB
Total PE 5871
Alloc PE / Size 5861 / 183.16 GB
Free PE / Size 10 / 320.00 MB
VG UUID IzgtV1-R5AB-PuhB-jp5F-xVPy-l8Pj-qcz0Bo
Filesystem Size Used Avail Use% Mounted on
/dev/hda2 4.0G 1.5G 2.4G 38% /
/dev/hda1 99M 8.3M 86M 9% /boot
none 126M 0 126M 0% /dev/shm
/dev/mapper/VolGroup01-LogVol01
106G 86G 16G 85% /home
--[/snip]------------------------------------------
As you can see, /dev/mapper/VolGroup01-LogVol01 as /home is only
showing a size of 106GB when I do a df -h, but lvdisplay shows
/dev/VolGroup01/LogVol01 as 183.16 GB. It seems to be a matter of
mapping that info so that it gets recognized... just not sure how to
do that. When I did it the first time it was about a year ago. Now I
can't find the docs I used to do the job.
I'm having a bit of trouble getting a second hard drive to be
mapped by LVM. I think I've got things to the point that I'm just
missing a minor step. Here's the skinny:
1) Initially someone imaged a 120GB hard drive with a 60GB image. I
created a 60GB image and joined it to the other 60GB image.
Everything was cool... I had about 106GB for /home.
2) I just added a second drive, an 80GB drive that I also want mapped to home.
Below is the mess I've created:
--[snip]------------------------------------------
--- Physical volume ---
PV Name /dev/hda5
VG Name VolGroup01
PV Size 52.66 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 1685
Free PE 0
Allocated PE 1685
PV UUID 57X3AO-NXrE-1Hs1-b2eF-3asW-LtX5-mjRlns
--- Physical volume ---
PV Name /dev/hda6
VG Name VolGroup01
PV Size 54.50 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 1744
Free PE 0
Allocated PE 1744
PV UUID vYcDST-5ZkY-6TU3-NtvY-nFNN-dywA-O3OrZC
--- Physical volume ---
PV Name /dev/hdb1
VG Name VolGroup01
PV Size 76.31 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 2442
Free PE 10
Allocated PE 2432
PV UUID fkslom-Pf5T-tOUc-mPOq-WSXF-U5B6-YaDuN2
--- NEW Physical volume ---
PV Name /dev/hdb
VG Name
PV Size 76.34 GB
Allocatable NO
PE Size (KByte) 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID lRvY0d-5lgb-ZfCy-lwIu-Nkwt-LI1p-1FsrBX
--- Logical volume ---
LV Name /dev/VolGroup01/LogVol01
VG Name VolGroup01
LV UUID dPPB8b-ASXB-3Ha4-mSlj-l648-UTQG-P7Fiz8
LV Write Access read/write
LV Status available
# open 1
LV Size 183.16 GB
Current LE 5861
Segments 3
Allocation inherit
Read ahead sectors 0
Block device 253:0
--- Volume group ---
VG Name VolGroup01
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 3
Act PV 3
VG Size 183.47 GB
PE Size 32.00 MB
Total PE 5871
Alloc PE / Size 5861 / 183.16 GB
Free PE / Size 10 / 320.00 MB
VG UUID IzgtV1-R5AB-PuhB-jp5F-xVPy-l8Pj-qcz0Bo
Filesystem Size Used Avail Use% Mounted on
/dev/hda2 4.0G 1.5G 2.4G 38% /
/dev/hda1 99M 8.3M 86M 9% /boot
none 126M 0 126M 0% /dev/shm
/dev/mapper/VolGroup01-LogVol01
106G 86G 16G 85% /home
--[/snip]------------------------------------------
As you can see, /dev/mapper/VolGroup01-LogVol01 as /home is only
showing a size of 106GB when I do a df -h, but lvdisplay shows
/dev/VolGroup01/LogVol01 as 183.16 GB. It seems to be a matter of
mapping that info so that it gets recognized... just not sure how to
do that. When I did it the first time it was about a year ago. Now I
can't find the docs I used to do the job.
Subscribe to:
Posts (Atom)