All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] lvm problem
@ 2002-01-14  8:22 Matthias Stoll
  2002-01-15  5:56 ` Heinz J . Mauelshagen
  0 siblings, 1 reply; 5+ messages in thread
From: Matthias Stoll @ 2002-01-14  8:22 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]

Hi !

I'm not so firm in linux but:

We had a LG "smbdata" which went away somehow? ;-)

Searched all threads and followed your instructions on recovering 
configuration of LV. Didn't work ;-(

Here is the output of vgcfgrestore -ll -f /etc/lvmconf/smbdata.conf.7.old 
-n smbdata /dev/sda

--- Volume group ---
VG Name               smbdata
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                4
Act PV                4
VG Size               15.86 GB
PE Size               4 MB
Total PE              4060
Alloc PE / Size       4060 / 15.86 GB
Free  PE / Size       0 / 0
VG UUID               zwceZi-TCXm-Ew3a-A5yc-H49M-R1NP-y4qg4T

--- Logical volume ---
LV Name                /dev/smbdata/all
VG Name                smbdata
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 0
LV Size                15.86 GB
Current LE             4060
Allocated LE           4060
Allocation             next free
Read ahead sectors     120
Block device           58:0


--- Physical volume ---
PV Name               /dev/sda1
VG Name               smbdata
PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
PV#                   1
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              1015
Free PE               0
Allocated PE          1015
PV UUID               tFA0qy-8u7r-8oBv-MwYS-SUVM-1W7h-P3hHED

--- Physical volume ---
PV Name               /dev/sdb1
VG Name               smbdata
PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
PV#                   2
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              1015
Free PE               0
Allocated PE          1015
PV UUID               cVeBuv-1i2C-hkOO-mUA1-lNrj-Vh8l-vrr6Am

--- Physical volume ---
PV Name               /dev/sdc1
VG Name               smbdata
PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
PV#                   3
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              1015
Free PE               0
Allocated PE          1015
PV UUID               Rtuhx3-0HR9-V0hN-iLuZ-dkFL-hyih-cEwEII

--- Physical volume ---
PV Name               /dev/sdd1
VG Name               smbdata
PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
PV#                   4
PV Status             NOT available
Allocatable           yes (but full)
Cur LV                1
PE Size (KByte)       4096
Total PE              1015
Free PE               0
Allocated PE          1015
PV UUID               HNkTzu-Ok46-4vqM-CJCu-Iqd1-JmQ4-c5yzea


Could anyone provide me some help?

Thanx

Matthias

[-- Attachment #2: Type: text/html, Size: 9525 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] lvm problem
  2002-01-14  8:22 [linux-lvm] lvm problem Matthias Stoll
@ 2002-01-15  5:56 ` Heinz J . Mauelshagen
  0 siblings, 0 replies; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-01-15  5:56 UTC (permalink / raw)
  To: linux-lvm

On Mon, Jan 14, 2002 at 03:21:39PM +0100, Matthias Stoll wrote:
> Hi !
> 
> I'm not so firm in linux but:
> 
> We had a LG "smbdata" which went away somehow? ;-)

Hi Matthias.

What does 'somehow' mean? ;-)

LVM/Operator error? I know: in case of an operator error I wouldn't tell
anybody either ;-)

> 
> Searched all threads and followed your instructions on recovering 
> configuration of LV. Didn't work ;-(
> 
> Here is the output of vgcfgrestore -ll -f /etc/lvmconf/smbdata.conf.7.old 
> -n smbdata /dev/sda
> 
> --- Volume group ---
> VG Name               smbdata
> VG Access             read/write
> VG Status             NOT available/resizable
> VG #                  0
> MAX LV                256
> Cur LV                1
> Open LV               0
> MAX LV Size           255.99 GB
> Max PV                256
> Cur PV                4
> Act PV                4
> VG Size               15.86 GB
> PE Size               4 MB
> Total PE              4060
> Alloc PE / Size       4060 / 15.86 GB
> Free  PE / Size       0 / 0
> VG UUID               zwceZi-TCXm-Ew3a-A5yc-H49M-R1NP-y4qg4T
> 
> --- Logical volume ---
> LV Name                /dev/smbdata/all
> VG Name                smbdata
> LV Write Access        read/write
> LV Status              available
> LV #                   1
> # open                 0
> LV Size                15.86 GB
> Current LE             4060
> Allocated LE           4060
> Allocation             next free
> Read ahead sectors     120
> Block device           58:0
> 
> 
> --- Physical volume ---
> PV Name               /dev/sda1
> VG Name               smbdata
> PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV#                   1
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              1015
> Free PE               0
> Allocated PE          1015
> PV UUID               tFA0qy-8u7r-8oBv-MwYS-SUVM-1W7h-P3hHED
> 
> --- Physical volume ---
> PV Name               /dev/sdb1
> VG Name               smbdata
> PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV#                   2
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              1015
> Free PE               0
> Allocated PE          1015
> PV UUID               cVeBuv-1i2C-hkOO-mUA1-lNrj-Vh8l-vrr6Am
> 
> --- Physical volume ---
> PV Name               /dev/sdc1
> VG Name               smbdata
> PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV#                   3
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              1015
> Free PE               0
> Allocated PE          1015
> PV UUID               Rtuhx3-0HR9-V0hN-iLuZ-dkFL-hyih-cEwEII
> 
> --- Physical volume ---
> PV Name               /dev/sdd1
> VG Name               smbdata
> PV Size               3.97 GB / NOT usable 3.28 MB [LVM: 124 KB]
> PV#                   4
> PV Status             NOT available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              1015
> Free PE               0
> Allocated PE          1015
> PV UUID               HNkTzu-Ok46-4vqM-CJCu-Iqd1-JmQ4-c5yzea
> 
> 
> Could anyone provide me some help?

Please run:


# save your LVM metadata for later use
for d in /dev/sd[a-d]1; do
   dd if=$d of=$d.VGDA count=512 bs=1k
done

# to recreate your PVs because vgcfgrestore needs that
pvcreate -ff /dev/sd[a-d]1

# restore the metadata from backup
for d in /dev/sd[a-d]1; do
   vgcfgrestore -n smbdata -f /etc/lvmconf/smbdata.conf.7.old /dev/$d
done

# scan in the metadata
vgscan

# activate the VG
vgchange -ay smbdata

> 
> Thanx
> 
> Matthias
-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [linux-lvm] lvm problem..
@ 2004-07-06 10:06 Sachin Sant
  2004-07-08 10:30 ` Sachin Sant
  0 siblings, 1 reply; 5+ messages in thread
From: Sachin Sant @ 2004-07-06 10:06 UTC (permalink / raw)
  To: linux-lvm

Steps to Reproduce:
   configure logical volume 
vgscan
pvcreate /dev/hdc1
vgcreate vg1 /dev/hdc1
lvcreate -n lv001 -L 1000G vg1

After a reboot  when the machine comes up i see these messages 

Remounting root filesystem in read-write mode:  [  OK  ]
Setting up Logical Volume Management: modprobe: modprobe: Can't locate
module 
block-major-43
modprobe: modprobe: Can't locate module block-major-43
modprobe: modprobe: Can't locate module block-major-43
modprobe: modprobe: Can't locate module block-major-43

After adding the line " alias block-major-43 off" i can turn off these
messages.
 
Question :
   Why is lvm looking for this block major 43 device [ nbd ]. Does it
scan all the block major devices to locate pv's.

I am using LVM 1.0.8 on RHEL 3.

-- 
Thanks
-Sachin
-----------------------------------
Sachin Sant
Linux Technology Center
IBM Software Lab
Bangalore, INDIA.

sachinp@in.ibm.com
Ph: 91-80-5044647
-----------------------------------

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] lvm problem..
  2004-07-06 10:06 Sachin Sant
@ 2004-07-08 10:30 ` Sachin Sant
  0 siblings, 0 replies; 5+ messages in thread
From: Sachin Sant @ 2004-07-08 10:30 UTC (permalink / raw)
  To: linux-lvm


Never mind .. i got it...

Sachin Sant wrote:
> 
> Steps to Reproduce:
>    configure logical volume
> vgscan
> pvcreate /dev/hdc1
> vgcreate vg1 /dev/hdc1
> lvcreate -n lv001 -L 1000G vg1
> 
> After a reboot  when the machine comes up i see these messages
> 
> Remounting root filesystem in read-write mode:  [  OK  ]
> Setting up Logical Volume Management: modprobe: modprobe: Can't locate
> module
> block-major-43
> modprobe: modprobe: Can't locate module block-major-43
> modprobe: modprobe: Can't locate module block-major-43
> modprobe: modprobe: Can't locate module block-major-43
> 
> After adding the line " alias block-major-43 off" i can turn off these
> messages.
> 
> Question :
>    Why is lvm looking for this block major 43 device [ nbd ]. Does it
> scan all the block major devices to locate pv's.
> 
> I am using LVM 1.0.8 on RHEL 3.
> 
> --
> Thanks
> -Sachin
> -----------------------------------
> Sachin Sant
> Linux Technology Center
> IBM Software Lab
> Bangalore, INDIA.
> 
> sachinp@in.ibm.com
> Ph: 91-80-5044647
> -----------------------------------
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 
Thanks
-Sachin
-----------------------------------
Sachin Sant
Linux Technology Center
IBM Software Lab
Bangalore, INDIA.

sachinp@in.ibm.com
Ph: 91-80-5044647
-----------------------------------

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [linux-lvm] LVM problem
@ 2008-04-30 23:05 Subzwari, Junaid
  0 siblings, 0 replies; 5+ messages in thread
From: Subzwari, Junaid @ 2008-04-30 23:05 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

 

Hi there, 

 

I'm ruing RedHat enterprise Linux WS and when my system boots up it
stops right after Setting up Logical Management.  From there nothing
happens and hangs.  I'm hoping this doesn't mean my filesystem is
trashed.  Can you anybody please help?  Many thanks. 

 

best regards,

Junaid H. Subzwari 
Technical Staff, DSP Applications 
Texas Instruments Semiconductor Group 
Work: 303-651-5916  
Mobile: 970-988-1808 

 


[-- Attachment #2: Type: text/html, Size: 4712 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2008-04-30 23:05 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-14  8:22 [linux-lvm] lvm problem Matthias Stoll
2002-01-15  5:56 ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2004-07-06 10:06 Sachin Sant
2004-07-08 10:30 ` Sachin Sant
2008-04-30 23:05 [linux-lvm] LVM problem Subzwari, Junaid

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.