[linux-lvm] pvmove problem

[linux-lvm] pvmove problem

[B. Dobalina]

I am trying to remove an old harddrive from one of my volumes using:
  pvmove -v /dev/hdh3
It was chugging along just find until about half way through when it froze. 
Linux was not "frozen", but I do not think it would allow any io to the 
block devices (logins, ls's, etc would stall). I waited about an hour, at 
which point it was still stuck on the same extent, and had no other option 
but to hard reboot. When the system was booted, the volume to which hdh3 
belonged, would no longer mount:

$ vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "vol1"
vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get 
data of volume group "vol2" from physical volume(s)
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
groups


Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore on 
/dev/hdh3: same result. Then I ran it on all the PVs in vol2: same result. 
Does anybody have a solution to get this volume mounted? There is a bunch of 
data on vol2, but not all that much in /dev/hdh3, so a partial restore would 
be ok.

Thanks,
Skip


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [linux-lvm] pvmove problem

[Heinz J . Mauelshagen]

Which LVM and Linux  version is this ?
Does everything else irt LVM with the exception of pvmove ru fine
(i.e. creating/removing LVs etc.) ?

Regards,
Heinz    -- The LVM Guy --


On Thu, Feb 06, 2003 at 11:26:44PM +0000, B. Dobalina wrote:
> I am trying to remove an old harddrive from one of my volumes using:
>   pvmove -v /dev/hdh3
> It was chugging along just find until about half way through when it froze. 
> Linux was not "frozen", but I do not think it would allow any io to the 
> block devices (logins, ls's, etc would stall). I waited about an hour, at 
> which point it was still stuck on the same extent, and had no other option 
> but to hard reboot. When the system was booted, the volume to which hdh3 
> belonged, would no longer mount:
> 
> $ vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- found active volume group "vol1"
> vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
> vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get 
> data of volume group "vol2" from physical volume(s)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> groups
> 
> 
> Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore on 
> /dev/hdh3: same result. Then I ran it on all the PVs in vol2: same result. 
> Does anybody have a solution to get this volume mounted? There is a bunch of 
> data on vol2, but not all that much in /dev/hdh3, so a partial restore would 
> be ok.
> 
> Thanks,
> Skip
> 
> 
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] pvmove problem

[B. Dobalina]

Its linux 2.4.19 (with the sgi xfs patch) and lvm 1.0.6. I have two volumes, 
the other volume (vol1) is unaffected. All lvm operations seem to be working 
on vol1. For vol2 (the one that I executed a pvmove on), I cannot get lvm to 
recognize it so I cannot perform any lvm operations.

-skip




Which LVM and Linux  version is this ?
Does everything else irt LVM with the exception of pvmove ru fine
(i.e. creating/removing LVs etc.) ?

Regards,
Heinz    -- The LVM Guy --


On Thu, Feb 06, 2003 at 11:26:44PM +0000, B. Dobalina wrote:
>I am trying to remove an old harddrive from one of my volumes using:
>   pvmove -v /dev/hdh3
>It was chugging along just find until about half way through when it froze. 
>Linux was not "frozen", but I do not think it would allow any io to the 
>block devices (logins, ls's, etc would stall). I waited about an hour, at 
>which point it was still stuck on the same extent, and had no other option 
>but to hard reboot. When the system was booted, the volume to which hdh3 
>belonged, would no longer mount:
>
>$ vgscan
>vgscan -- reading all physical volumes (this may take a while...)
>vgscan -- found active volume group "vol1"
>vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
>vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get 
>data of volume group "vol2" from physical volume(s)
>vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
>vgscan -- WARNING: This program does not do a VGDA backup of your volume 
>groups
>
>
>Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore on 
>/dev/hdh3: same result. Then I ran it on all the PVs in vol2: same result. 
>Does anybody have a solution to get this volume mounted? There is a bunch 
>of data on vol2, but not all that much in /dev/hdh3, so a partial restore 
>would be ok.
>
>Thanks,
>Skip
>
>
>_________________________________________________________________
>Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
>http://join.msn.com/?page=features/junkmail
>
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. 
http://join.msn.com/?page=features/junkmail

Re: [linux-lvm] pvmove problem

[Heinz J . Mauelshagen]

On Fri, Feb 07, 2003 at 05:50:21PM +0000, B. Dobalina wrote:
> Its linux 2.4.19 (with the sgi xfs patch) and lvm 1.0.6. I have two volumes, 
> the other volume (vol1) is unaffected. All lvm operations seem to be working 
> on vol1. For vol2 (the one that I executed a pvmove on), I cannot get lvm to 
> recognize it so I cannot perform any lvm operations.

You've got the actual LVM software. Let's try to approach the problem
a bit more...

Have there been any syslog messages spotting some light on this ?
Are you still able to use vol2's content ?

Before changing anything, don't forget to keep recent backups!

Regards,
Heinz    -- The LVM Guy --

> 
> -skip
> 
> 
> 
> 
> Which LVM and Linux  version is this ?
> Does everything else irt LVM with the exception of pvmove ru fine
> (i.e. creating/removing LVs etc.) ?
> 
> Regards,
> Heinz    -- The LVM Guy --
> 
> 
> On Thu, Feb 06, 2003 at 11:26:44PM +0000, B. Dobalina wrote:
> >I am trying to remove an old harddrive from one of my volumes using:
> >   pvmove -v /dev/hdh3
> >It was chugging along just find until about half way through when it froze. 
> >Linux was not "frozen", but I do not think it would allow any io to the 
> >block devices (logins, ls's, etc would stall). I waited about an hour, at 
> >which point it was still stuck on the same extent, and had no other option 
> >but to hard reboot. When the system was booted, the volume to which hdh3 
> >belonged, would no longer mount:
> >
> >$ vgscan
> >vgscan -- reading all physical volumes (this may take a while...)
> >vgscan -- found active volume group "vol1"
> >vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
> >vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't get 
> >data of volume group "vol2" from physical volume(s)
> >vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> >vgscan -- WARNING: This program does not do a VGDA backup of your volume 
> >groups
> >
> >
> >Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore on 
> >/dev/hdh3: same result. Then I ran it on all the PVs in vol2: same result. 
> >Does anybody have a solution to get this volume mounted? There is a bunch 
> >of data on vol2, but not all that much in /dev/hdh3, so a partial restore 
> >would be ok.
> >
> >Thanks,
> >Skip
> >
> >
> >_________________________________________________________________
> >Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
> >http://join.msn.com/?page=features/junkmail
> >
> >
> >_______________________________________________
> >linux-lvm mailing list
> >linux-lvm@sistina.com
> >http://lists.sistina.com/mailman/listinfo/linux-lvm
> >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] pvmove problem

[B. Dobalina]

Luckily I have some backups of all but one LV (which is just too big to 
backup) on vol2. But it would be nice to recover that volume.

As far as syslog messages, I did not see anything out of the ordinary before 
the pvmove. Now of course I get the error message produced by vgscan which I 
pasted in the first message.

Not quite sure what you mean about "using vol2's content". I cannot get LVM 
to recognize vol2, so of course it will not activate it. So I cannot mount 
any of the volumes in vol2.

It is only complaining about /dev/vol2/software volume. If there was someway 
I could delete this volume without having to have vol2 activated, that might 
solve the problem--unless other volumes' metadata is corrupted as well. I 
seem to remember reading about LVM2's ability to do a partial activation 
(missing 1 or more PVs from a VG). Would it be worthwhile to try and mount 
vol2 under LVM2 with hdh3 removed?

Thanks,
Skip


>From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
>Reply-To: linux-lvm@sistina.com
>To: linux-lvm@sistina.com
>Subject: Re: [linux-lvm] pvmove problem
>Date: Mon, 10 Feb 2003 14:53:49 +0100
>
>On Fri, Feb 07, 2003 at 05:50:21PM +0000, B. Dobalina wrote:
> > Its linux 2.4.19 (with the sgi xfs patch) and lvm 1.0.6. I have two 
>volumes,
> > the other volume (vol1) is unaffected. All lvm operations seem to be 
>working
> > on vol1. For vol2 (the one that I executed a pvmove on), I cannot get 
>lvm to
> > recognize it so I cannot perform any lvm operations.
>
>You've got the actual LVM software. Let's try to approach the problem
>a bit more...
>
>Have there been any syslog messages spotting some light on this ?
>Are you still able to use vol2's content ?
>
>Before changing anything, don't forget to keep recent backups!
>
>Regards,
>Heinz    -- The LVM Guy --
>
> >
> > -skip
> >
> >
> >
> >
> > Which LVM and Linux  version is this ?
> > Does everything else irt LVM with the exception of pvmove ru fine
> > (i.e. creating/removing LVs etc.) ?
> >
> > Regards,
> > Heinz    -- The LVM Guy --
> >
> >
> > On Thu, Feb 06, 2003 at 11:26:44PM +0000, B. Dobalina wrote:
> > >I am trying to remove an old harddrive from one of my volumes using:
> > >   pvmove -v /dev/hdh3
> > >It was chugging along just find until about half way through when it 
>froze.
> > >Linux was not "frozen", but I do not think it would allow any io to the
> > >block devices (logins, ls's, etc would stall). I waited about an hour, 
>at
> > >which point it was still stuck on the same extent, and had no other 
>option
> > >but to hard reboot. When the system was booted, the volume to which 
>hdh3
> > >belonged, would no longer mount:
> > >
> > >$ vgscan
> > >vgscan -- reading all physical volumes (this may take a while...)
> > >vgscan -- found active volume group "vol1"
> > >vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
> > >vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't 
>get
> > >data of volume group "vol2" from physical volume(s)
> > >vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> > >vgscan -- WARNING: This program does not do a VGDA backup of your 
>volume
> > >groups
> > >
> > >
> > >Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore 
>on
> > >/dev/hdh3: same result. Then I ran it on all the PVs in vol2: same 
>result.
> > >Does anybody have a solution to get this volume mounted? There is a 
>bunch
> > >of data on vol2, but not all that much in /dev/hdh3, so a partial 
>restore
> > >would be ok.
> > >
> > >Thanks,
> > >Skip
> > >
> > >
> > >_________________________________________________________________
> > >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > >http://join.msn.com/?page=features/junkmail
> > >
> > >
> > >_______________________________________________
> > >linux-lvm mailing list
> > >linux-lvm@sistina.com
> > >http://lists.sistina.com/mailman/listinfo/linux-lvm
> > >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >
>
>*** 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
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [linux-lvm] pvmove problem

[Heinz J . Mauelshagen]

On Mon, Feb 10, 2003 at 06:28:31PM +0000, B. Dobalina wrote:
> Luckily I have some backups of all but one LV (which is just too big to 
> backup) on vol2. But it would be nice to recover that volume.
> 
> As far as syslog messages, I did not see anything out of the ordinary before 
> the pvmove. Now of course I get the error message produced by vgscan which I 
> pasted in the first message.
> 
> Not quite sure what you mean about "using vol2's content". I cannot get LVM 
> to recognize vol2, so of course it will not activate it. So I cannot mount 
> any of the volumes in vol2.

Got it.

> 
> It is only complaining about /dev/vol2/software volume. If there was someway 
> I could delete this volume without having to have vol2 activated, that might 
> solve the problem--unless other volumes' metadata is corrupted as well. I 
> seem to remember reading about LVM2's ability to do a partial activation 
> (missing 1 or more PVs from a VG). Would it be worthwhile to try and mount 
> vol2 under LVM2 with hdh3 removed?

That's probably the way to go.
LVM2 is LVM1 metadata compatible.
Run "vgscan ; vgchange -P -ay" once you've installed it.
Please remember that LVM2 doesn't have pvmove so far (we are working on it).

> 
> Thanks,
> Skip
> 
> 
> >From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> >Reply-To: linux-lvm@sistina.com
> >To: linux-lvm@sistina.com
> >Subject: Re: [linux-lvm] pvmove problem
> >Date: Mon, 10 Feb 2003 14:53:49 +0100
> >
> >On Fri, Feb 07, 2003 at 05:50:21PM +0000, B. Dobalina wrote:
> > > Its linux 2.4.19 (with the sgi xfs patch) and lvm 1.0.6. I have two 
> >volumes,
> > > the other volume (vol1) is unaffected. All lvm operations seem to be 
> >working
> > > on vol1. For vol2 (the one that I executed a pvmove on), I cannot get 
> >lvm to
> > > recognize it so I cannot perform any lvm operations.
> >
> >You've got the actual LVM software. Let's try to approach the problem
> >a bit more...
> >
> >Have there been any syslog messages spotting some light on this ?
> >Are you still able to use vol2's content ?
> >
> >Before changing anything, don't forget to keep recent backups!
> >
> >Regards,
> >Heinz    -- The LVM Guy --
> >
> > >
> > > -skip
> > >
> > >
> > >
> > >
> > > Which LVM and Linux  version is this ?
> > > Does everything else irt LVM with the exception of pvmove ru fine
> > > (i.e. creating/removing LVs etc.) ?
> > >
> > > Regards,
> > > Heinz    -- The LVM Guy --
> > >
> > >
> > > On Thu, Feb 06, 2003 at 11:26:44PM +0000, B. Dobalina wrote:
> > > >I am trying to remove an old harddrive from one of my volumes using:
> > > >   pvmove -v /dev/hdh3
> > > >It was chugging along just find until about half way through when it 
> >froze.
> > > >Linux was not "frozen", but I do not think it would allow any io to the
> > > >block devices (logins, ls's, etc would stall). I waited about an hour, 
> >at
> > > >which point it was still stuck on the same extent, and had no other 
> >option
> > > >but to hard reboot. When the system was booted, the volume to which 
> >hdh3
> > > >belonged, would no longer mount:
> > > >
> > > >$ vgscan
> > > >vgscan -- reading all physical volumes (this may take a while...)
> > > >vgscan -- found active volume group "vol1"
> > > >vgscan -- only found 2523 of 768 LEs for LV /dev/vol2/software (1)
> > > >vgscan -- ERROR "vg_read_with_pv_and_lv(): allocated LE of LV" can't 
> >get
> > > >data of volume group "vol2" from physical volume(s)
> > > >vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> > > >vgscan -- WARNING: This program does not do a VGDA backup of your 
> >volume
> > > >groups
> > > >
> > > >
> > > >Looks like some lvm metadata has been corrupted. So I ran vgcfgrestore 
> >on
> > > >/dev/hdh3: same result. Then I ran it on all the PVs in vol2: same 
> >result.
> > > >Does anybody have a solution to get this volume mounted? There is a 
> >bunch
> > > >of data on vol2, but not all that much in /dev/hdh3, so a partial 
> >restore
> > > >would be ok.
> > > >
> > > >Thanks,
> > > >Skip
> > > >
> > > >
> > > >_________________________________________________________________
> > > >Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > > >http://join.msn.com/?page=features/junkmail
> > > >
> > > >
> > > >_______________________________________________
> > > >linux-lvm mailing list
> > > >linux-lvm@sistina.com
> > > >http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> > >
> >
> >*** 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
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >_______________________________________________
> >linux-lvm mailing list
> >linux-lvm@sistina.com
> >http://lists.sistina.com/mailman/listinfo/linux-lvm
> >read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
> 
> _________________________________________________________________
> The new MSN 8: advanced junk mail protection and 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[linux-lvm] problem in /proc/lvm/global help please..

[abbireddy venkatram reddy]

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

Hi all,


 I am reading information of lvms from the /proc/lvm directory.

 but the snapshot size is shown as same size as lv if I create with lesses size of lv also.

 can anybody help me please.

 thanks in advance.
 eg.

file information: /proc/lvm/global

VG:  vg01  [2 PV, 2 LV/2 open]  PE Size: 65536 KB
  Usage [KB/PE]: 52232192 /797 total  3866624 /59 used  48365568 /738 free
  PVs: [AA] rd/c0d0p5             41091072 /627      3080192 /47      38010880 /580
       [AA] rd/c0d0p6             11141120 /170            0 /0       11141120 /170
    LVs: [AWDL  ] lv01                       3080192 /47       1x open
         [ARDL  ] lv01_snap0217_1550         3080192 /47       1x open


 output from the lvscan :

lvscan -- ACTIVE   Original "/dev/vg01/lv01" [2.94 GB]
lvscan -- ACTIVE   Snapshot "/dev/vg01/lv01_snap0217_1550" [767.25 MB] of /dev/vg01/lv01

Please help me. what is the reason?. is kernel problem?

with regards
venkat.



 

 

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

Re: [linux-lvm] problem in /proc/lvm/global help please..

[abbireddy venkatram reddy]

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

Hi all,


 I am reading information of lvms from the /proc/lvm directory.

 but the snapshot size is shown as same size as lv if I create with lesses size of lv also.

 can anybody help me please.

 thanks in advance.
 eg.

file information: /proc/lvm/global

VG:  vg01  [2 PV, 2 LV/2 open]  PE Size: 65536 KB
  Usage [KB/PE]: 52232192 /797 total  3866624 /59 used  48365568 /738 free
  PVs: [AA] rd/c0d0p5             41091072 /627      3080192 /47      38010880 /580
       [AA] rd/c0d0p6             11141120 /170            0 /0       11141120 /170
    LVs: [AWDL  ] lv01                       3080192 /47       1x open
         [ARDL  ] lv01_snap0217_1550         3080192 /47       1x open


 output from the lvscan :

lvscan -- ACTIVE   Original "/dev/vg01/lv01" [2.94 GB]
lvscan -- ACTIVE   Snapshot "/dev/vg01/lv01_snap0217_1550" [767.25 MB] of /dev/vg01/lv01

Please help me. what is the reason?. is kernel problem?

with regards
venkat.

  ----- Original Message ----- 
  From: abbireddy venkatram reddy 
  To: linux-lvm@sistina.com 
  Sent: Monday, February 17, 2003 3:56 PM
  Subject: [linux-lvm] problem in /proc/lvm/global help please..


  Hi all,


   I am reading information of lvms from the /proc/lvm directory.

   but the snapshot size is shown as same size as lv if I create with lesses size of lv also.

   can anybody help me please.

   thanks in advance.
   eg.

  file information: /proc/lvm/global

  VG:  vg01  [2 PV, 2 LV/2 open]  PE Size: 65536 KB
    Usage [KB/PE]: 52232192 /797 total  3866624 /59 used  48365568 /738 free
    PVs: [AA] rd/c0d0p5             41091072 /627      3080192 /47      38010880 /580
         [AA] rd/c0d0p6             11141120 /170            0 /0       11141120 /170
      LVs: [AWDL  ] lv01                       3080192 /47       1x open
           [ARDL  ] lv01_snap0217_1550         3080192 /47       1x open


   output from the lvscan :

  lvscan -- ACTIVE   Original "/dev/vg01/lv01" [2.94 GB]
  lvscan -- ACTIVE   Snapshot "/dev/vg01/lv01_snap0217_1550" [767.25 MB] of /dev/vg01/lv01

  Please help me. what is the reason?. is kernel problem?

  with regards
  venkat.






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

Re: [linux-lvm] problem in /proc/lvm/global help please..

[Heinz J . Mauelshagen]

You can retrieve the information about the physical size of the snapshot
using the tools only.

Regards,
Heinz    -- The LVM Guy --

On Fri, Feb 21, 2003 at 10:07:12AM +0900, abbireddy venkatram reddy wrote:
> Hi all,
> 
> 
>  I am reading information of lvms from the /proc/lvm directory.
> 
>  but the snapshot size is shown as same size as lv if I create with lesses size of lv also.
> 
>  can anybody help me please.
> 
>  thanks in advance.
>  eg.
> 
> file information: /proc/lvm/global
> 
> VG:  vg01  [2 PV, 2 LV/2 open]  PE Size: 65536 KB
>   Usage [KB/PE]: 52232192 /797 total  3866624 /59 used  48365568 /738 free
>   PVs: [AA] rd/c0d0p5             41091072 /627      3080192 /47      38010880 /580
>        [AA] rd/c0d0p6             11141120 /170            0 /0       11141120 /170
>     LVs: [AWDL  ] lv01                       3080192 /47       1x open
>          [ARDL  ] lv01_snap0217_1550         3080192 /47       1x open
> 
> 
>  output from the lvscan :
> 
> lvscan -- ACTIVE   Original "/dev/vg01/lv01" [2.94 GB]
> lvscan -- ACTIVE   Snapshot "/dev/vg01/lv01_snap0217_1550" [767.25 MB] of /dev/vg01/lv01
> 
> Please help me. what is the reason?. is kernel problem?
> 
> with regards
> venkat.
> 
>   ----- Original Message ----- 
>   From: abbireddy venkatram reddy 
>   To: linux-lvm@sistina.com 
>   Sent: Monday, February 17, 2003 3:56 PM
>   Subject: [linux-lvm] problem in /proc/lvm/global help please..
> 
> 
>   Hi all,
> 
> 
>    I am reading information of lvms from the /proc/lvm directory.
> 
>    but the snapshot size is shown as same size as lv if I create with lesses size of lv also.
> 
>    can anybody help me please.
> 
>    thanks in advance.
>    eg.
> 
>   file information: /proc/lvm/global
> 
>   VG:  vg01  [2 PV, 2 LV/2 open]  PE Size: 65536 KB
>     Usage [KB/PE]: 52232192 /797 total  3866624 /59 used  48365568 /738 free
>     PVs: [AA] rd/c0d0p5             41091072 /627      3080192 /47      38010880 /580
>          [AA] rd/c0d0p6             11141120 /170            0 /0       11141120 /170
>       LVs: [AWDL  ] lv01                       3080192 /47       1x open
>            [ARDL  ] lv01_snap0217_1550         3080192 /47       1x open
> 
> 
>    output from the lvscan :
> 
>   lvscan -- ACTIVE   Original "/dev/vg01/lv01" [2.94 GB]
>   lvscan -- ACTIVE   Snapshot "/dev/vg01/lv01_snap0217_1550" [767.25 MB] of /dev/vg01/lv01
> 
>   Please help me. what is the reason?. is kernel problem?
> 
>   with regards
>   venkat.
> 
> 
> 
> 
> 

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[linux-lvm] pvmove problem

[Tim Randles]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm trying to pvmove from a dying disk to a new disk.  I'm using version 1.0.7 
of the LVM tools.  I know that the source disk has bad sectors on it.  I 
figured one of two things would happen with the pvmove:
1)  pvmove would work fine up to the bad sectors, where it would error with 
I/O read errors.  I would then restart the pvmove with PEs that are past the 
bad sectors on the source disk and things would finish.
2)  pvmove would work fine up to the bad sectors, where it would encounter I/O 
read errors.  pvmove would report the errors and say the data is 
lost/corrupt, but continue reading valid/skipping bad sectors until it 
finished.
I fear that I'm being naive about how pvmove will handle bad sectors...  At 
any rate, the error I'm getting is:

[root@mills tools]# ./pvmove -vv /dev/sdb1
pvmove -- checking name of source physical volume "/dev/sdb1"
pvmove -- locking logical volume manager
pvmove -- reading data of source physical volume from "/dev/sdb1"
pvmove -- checking volume group existence
pvmove -- reading data of volume group "vg1" from lvmtab
pvmove -- checking volume group consistency of "vg1"
pvmove -- searching for source physical volume "/dev/sdb1" in volume group 
"vg1"
pvmove -- building list of possible destination physical volumes
pvmove -- checking volume group activity
pvmove -- moving physical extents in active volume group "vg1"
pvmove -- WARNING: if you lose power during the move you may need
        to restore your LVM metadata from backup!
pvmove -- do you want to continue? [y/n] y
pvmove -- starting to move extents away from physical volume "/dev/sdb1"
pvmove -- checking for enough free physical extents in "vg1"
lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector: 4186488  
new_pe_sector: 4186488
pvmove -- opening output physical volume "/dev/sdc1"
pvmove -- llseeking input physical volume "/dev/sdb1"
pvmove -- llseeking output physical volume "/dev/sdc1"
pvmove -- /dev/sdb1 [PE 510 [lv7 [LE 5650]] -> /dev/sdc1 [PE 510] [1/4590]
pvmove -- locking physical extent 510 of "/dev/sdb1" in kernel
pvmove -- about to read input physical volume "/dev/sdb1" and to write output 
physical volume "/dev/sdc1"
pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 131072 bytes 
to read)
pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents


When I try to specify any random PE > 510 I get:


[root@mills tools]# ./pvmove -vv /dev/sdb1:530 /dev/sdc1
pvmove -- checking name of source physical volume "/dev/sdb1"
pvmove -- locking logical volume manager
pvmove -- reading data of source physical volume from "/dev/sdb1"
pvmove -- checking volume group existence
pvmove -- reading data of volume group "vg1" from lvmtab
pvmove -- checking volume group consistency of "vg1"
pvmove -- searching for source physical volume "/dev/sdb1" in volume group 
"vg1"
pvmove -- building list of possible destination physical volumes
pvmove -- checking destination physical volume names in command line
pvmove -- checking volume group activity
pvmove -- moving physical extents in active volume group "vg1"
pvmove -- WARNING: if you lose power during the move you may need
        to restore your LVM metadata from backup!
pvmove -- do you want to continue? [y/n] y
pvmove -- starting to move extents away from physical volume "/dev/sdb1"
pvmove -- checking for enough free physical extents in "vg1"
lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector: 4350328  
new_pe_sector: 4186488
pvmove -- opening output physical volume "/dev/sdc1"
pvmove -- llseeking input physical volume "/dev/sdb1"
pvmove -- llseeking output physical volume "/dev/sdc1"
pvmove -- /dev/sdb1 [PE 530 [lv7 [LE 5670]] -> /dev/sdc1 [PE 510] [1/1]
pvmove -- locking physical extent 530 of "/dev/sdb1" in kernel
pvmove -- about to read input physical volume "/dev/sdb1" and to write output 
physical volume "/dev/sdc1"
pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 4194304 bytes 
to read)
pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents


Is there anything I can do to get the pvmove to finish?

Thanks,
Tim

- -- 
Tim Randles
Unix Administrator and Webmaster
The Ohio State University
Department of Physics Computing Facility
Phone: 292-2630
Email: tcr@pacific.mps.ohio-state.edu
PGP key: http://www.physics.ohio-state.edu/~tcr/pgp.txt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+3hb5NMldGYWjmgoRAvG9AKDW6YmXjFOxj77lxwV3PNeO4VWbnwCfbjh0
cpfrctuKsARxpsPImzopeoQ=
=IyrK
-----END PGP SIGNATURE-----

Re: [linux-lvm] pvmove problem

[Heinz J . Mauelshagen]

Tim,

have you tried 'pvmove -i ...' yet ?
That tries to work arround read errors on flaky devices and read as much
data as possible.


Regards,
Heinz    -- The LVM Guy --


On Wed, Jun 04, 2003 at 11:57:45AM -0400, Tim Randles wrote:
> Hello,
> 
> I'm trying to pvmove from a dying disk to a new disk.  I'm using version 1.0.7 
> of the LVM tools.  I know that the source disk has bad sectors on it.  I 
> figured one of two things would happen with the pvmove:
> 1)  pvmove would work fine up to the bad sectors, where it would error with 
> I/O read errors.  I would then restart the pvmove with PEs that are past the 
> bad sectors on the source disk and things would finish.
> 2)  pvmove would work fine up to the bad sectors, where it would encounter I/O 
> read errors.  pvmove would report the errors and say the data is 
> lost/corrupt, but continue reading valid/skipping bad sectors until it 
> finished.
> I fear that I'm being naive about how pvmove will handle bad sectors...  At 
> any rate, the error I'm getting is:
> 
> [root@mills tools]# ./pvmove -vv /dev/sdb1
> pvmove -- checking name of source physical volume "/dev/sdb1"
> pvmove -- locking logical volume manager
> pvmove -- reading data of source physical volume from "/dev/sdb1"
> pvmove -- checking volume group existence
> pvmove -- reading data of volume group "vg1" from lvmtab
> pvmove -- checking volume group consistency of "vg1"
> pvmove -- searching for source physical volume "/dev/sdb1" in volume group 
> "vg1"
> pvmove -- building list of possible destination physical volumes
> pvmove -- checking volume group activity
> pvmove -- moving physical extents in active volume group "vg1"
> pvmove -- WARNING: if you lose power during the move you may need
>         to restore your LVM metadata from backup!
> pvmove -- do you want to continue? [y/n] y
> pvmove -- starting to move extents away from physical volume "/dev/sdb1"
> pvmove -- checking for enough free physical extents in "vg1"
> lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector: 4186488  
> new_pe_sector: 4186488
> pvmove -- opening output physical volume "/dev/sdc1"
> pvmove -- llseeking input physical volume "/dev/sdb1"
> pvmove -- llseeking output physical volume "/dev/sdc1"
> pvmove -- /dev/sdb1 [PE 510 [lv7 [LE 5650]] -> /dev/sdc1 [PE 510] [1/4590]
> pvmove -- locking physical extent 510 of "/dev/sdb1" in kernel
> pvmove -- about to read input physical volume "/dev/sdb1" and to write output 
> physical volume "/dev/sdc1"
> pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 131072 bytes 
> to read)
> pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> 
> 
> When I try to specify any random PE > 510 I get:
> 
> 
> [root@mills tools]# ./pvmove -vv /dev/sdb1:530 /dev/sdc1
> pvmove -- checking name of source physical volume "/dev/sdb1"
> pvmove -- locking logical volume manager
> pvmove -- reading data of source physical volume from "/dev/sdb1"
> pvmove -- checking volume group existence
> pvmove -- reading data of volume group "vg1" from lvmtab
> pvmove -- checking volume group consistency of "vg1"
> pvmove -- searching for source physical volume "/dev/sdb1" in volume group 
> "vg1"
> pvmove -- building list of possible destination physical volumes
> pvmove -- checking destination physical volume names in command line
> pvmove -- checking volume group activity
> pvmove -- moving physical extents in active volume group "vg1"
> pvmove -- WARNING: if you lose power during the move you may need
>         to restore your LVM metadata from backup!
> pvmove -- do you want to continue? [y/n] y
> pvmove -- starting to move extents away from physical volume "/dev/sdb1"
> pvmove -- checking for enough free physical extents in "vg1"
> lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector: 4350328  
> new_pe_sector: 4186488
> pvmove -- opening output physical volume "/dev/sdc1"
> pvmove -- llseeking input physical volume "/dev/sdb1"
> pvmove -- llseeking output physical volume "/dev/sdc1"
> pvmove -- /dev/sdb1 [PE 530 [lv7 [LE 5670]] -> /dev/sdc1 [PE 510] [1/1]
> pvmove -- locking physical extent 530 of "/dev/sdb1" in kernel
> pvmove -- about to read input physical volume "/dev/sdb1" and to write output 
> physical volume "/dev/sdc1"
> pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 4194304 bytes 
> to read)
> pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> 
> 
> Is there anything I can do to get the pvmove to finish?
> 
> Thanks,
> Tim
> 
> -- 
> Tim Randles
> Unix Administrator and Webmaster
> The Ohio State University
> Department of Physics Computing Facility
> Phone: 292-2630
> Email: tcr@pacific.mps.ohio-state.edu
> PGP key: http://www.physics.ohio-state.edu/~tcr/pgp.txt
> 
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: [linux-lvm] pvmove problem

[Tim Randles]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Heinz,

The disk failure was on a production webserver.  I had hoped to leave things 
offline until I heard back from someone on the list, but was pressured into 
recovering things sooner.  I removed the failing disk from service and 
restored from backup...didn't get a chance to try "pvmove -i" again.  The one 
time I tried it the command failed but I may have screwed up something else.  
Thanks for the response though.

Tim

On Thursday 05 June 2003 06:35 am, Heinz J . Mauelshagen wrote:
> Tim,
>
> have you tried 'pvmove -i ...' yet ?
> That tries to work arround read errors on flaky devices and read as much
> data as possible.
>
>
> Regards,
> Heinz    -- The LVM Guy --
>
> On Wed, Jun 04, 2003 at 11:57:45AM -0400, Tim Randles wrote:
> > Hello,
> >
> > I'm trying to pvmove from a dying disk to a new disk.  I'm using version
> > 1.0.7 of the LVM tools.  I know that the source disk has bad sectors on
> > it.  I figured one of two things would happen with the pvmove:
> > 1)  pvmove would work fine up to the bad sectors, where it would error
> > with I/O read errors.  I would then restart the pvmove with PEs that are
> > past the bad sectors on the source disk and things would finish.
> > 2)  pvmove would work fine up to the bad sectors, where it would
> > encounter I/O read errors.  pvmove would report the errors and say the
> > data is lost/corrupt, but continue reading valid/skipping bad sectors
> > until it finished.
> > I fear that I'm being naive about how pvmove will handle bad sectors... 
> > At any rate, the error I'm getting is:
> >
> > [root@mills tools]# ./pvmove -vv /dev/sdb1
> > pvmove -- checking name of source physical volume "/dev/sdb1"
> > pvmove -- locking logical volume manager
> > pvmove -- reading data of source physical volume from "/dev/sdb1"
> > pvmove -- checking volume group existence
> > pvmove -- reading data of volume group "vg1" from lvmtab
> > pvmove -- checking volume group consistency of "vg1"
> > pvmove -- searching for source physical volume "/dev/sdb1" in volume
> > group "vg1"
> > pvmove -- building list of possible destination physical volumes
> > pvmove -- checking volume group activity
> > pvmove -- moving physical extents in active volume group "vg1"
> > pvmove -- WARNING: if you lose power during the move you may need
> >         to restore your LVM metadata from backup!
> > pvmove -- do you want to continue? [y/n] y
> > pvmove -- starting to move extents away from physical volume "/dev/sdb1"
> > pvmove -- checking for enough free physical extents in "vg1"
> > lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector:
> > 4186488 new_pe_sector: 4186488
> > pvmove -- opening output physical volume "/dev/sdc1"
> > pvmove -- llseeking input physical volume "/dev/sdb1"
> > pvmove -- llseeking output physical volume "/dev/sdc1"
> > pvmove -- /dev/sdb1 [PE 510 [lv7 [LE 5650]] -> /dev/sdc1 [PE 510]
> > [1/4590] pvmove -- locking physical extent 510 of "/dev/sdb1" in kernel
> > pvmove -- about to read input physical volume "/dev/sdb1" and to write
> > output physical volume "/dev/sdc1"
> > pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 131072
> > bytes to read)
> > pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> >
> >
> > When I try to specify any random PE > 510 I get:
> >
> >
> > [root@mills tools]# ./pvmove -vv /dev/sdb1:530 /dev/sdc1
> > pvmove -- checking name of source physical volume "/dev/sdb1"
> > pvmove -- locking logical volume manager
> > pvmove -- reading data of source physical volume from "/dev/sdb1"
> > pvmove -- checking volume group existence
> > pvmove -- reading data of volume group "vg1" from lvmtab
> > pvmove -- checking volume group consistency of "vg1"
> > pvmove -- searching for source physical volume "/dev/sdb1" in volume
> > group "vg1"
> > pvmove -- building list of possible destination physical volumes
> > pvmove -- checking destination physical volume names in command line
> > pvmove -- checking volume group activity
> > pvmove -- moving physical extents in active volume group "vg1"
> > pvmove -- WARNING: if you lose power during the move you may need
> >         to restore your LVM metadata from backup!
> > pvmove -- do you want to continue? [y/n] y
> > pvmove -- starting to move extents away from physical volume "/dev/sdb1"
> > pvmove -- checking for enough free physical extents in "vg1"
> > lv: /dev/vg1/lv7[7]  old_dev: 08:17  new_dev: 08:33  old_pe_sector:
> > 4350328 new_pe_sector: 4186488
> > pvmove -- opening output physical volume "/dev/sdc1"
> > pvmove -- llseeking input physical volume "/dev/sdb1"
> > pvmove -- llseeking output physical volume "/dev/sdc1"
> > pvmove -- /dev/sdb1 [PE 530 [lv7 [LE 5670]] -> /dev/sdc1 [PE 510] [1/1]
> > pvmove -- locking physical extent 530 of "/dev/sdb1" in kernel
> > pvmove -- about to read input physical volume "/dev/sdb1" and to write
> > output physical volume "/dev/sdc1"
> > pvmove -- ERROR reading input physical volume "/dev/sdb1" (still 4194304
> > bytes to read)
> > pvmove -- ERROR "pv_move_pe(): read input PV" moving physical extents
> >
> >
> > Is there anything I can do to get the pvmove to finish?
> >
> > Thanks,
> > Tim
> >
> > --
> > Tim Randles
> > Unix Administrator and Webmaster
> > The Ohio State University
> > Department of Physics Computing Facility
> > Phone: 292-2630
> > Email: tcr@pacific.mps.ohio-state.edu
> > PGP key: http://www.physics.ohio-state.edu/~tcr/pgp.txt
> >
> >
> >
> >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
> *** 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>-=-
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

- -- 
Tim Randles
Unix Administrator and Webmaster
The Ohio State University
Department of Physics Computing Facility
Phone: 292-2630
Email: tcr@pacific.mps.ohio-state.edu
PGP key: http://www.physics.ohio-state.edu/~tcr/pgp.txt


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+6HnLNMldGYWjmgoRAnuRAKCM//b5DVBq+1jUlal0M7Oh+lUgpgCfWX30
2uXcO6Cn2FJ45ETbvqFoHHM=
=IU4w
-----END PGP SIGNATURE-----

[linux-lvm] pvmove problem

[BK Box]

Ok, I've been searching for an answer for a long time now... hopefully
someone here can help me.

I have a pretty lengthy explanation.. so i'll just post the link to it.

http://forums.gentoo.org/viewtopic.php?t=206391


Please help.. I don't feel like doing it the manual cp way :-/

BK

Re: [linux-lvm] pvmove problem

[Alasdair G Kergon]

On Sat, Aug 07, 2004 at 11:21:12AM -0500, BK Box wrote:
> I have a pretty lengthy explanation.. so i'll just post the link to it.
> http://forums.gentoo.org/viewtopic.php?t=206391

Summary: How do I pvmove data with LVM2 if contiguous runs of
PEs in the source LVs will have to be split up to make them fit?
 
Quick answer:
LVM2 doesn't support this directly yet: it's being worked on.
Until it's done you need to edit the metadata [using vgcfg*]
to split the segments into smaller ones before running pvmove.
[Might also need to recompile disabling section merging code
which would undo your splitting.]

Alasdair
-- 
agk@redhat.com

Re: [linux-lvm] pvmove problem

[BK Box]

On Sat, 7 Aug 2004 11:54:31 -0500, Alasdair G Kergon <agk@redhat.com> wrote:
> On Sat, Aug 07, 2004 at 11:21:12AM -0500, BK Box wrote:
> > I have a pretty lengthy explanation.. so i'll just post the link to it.
> > http://forums.gentoo.org/viewtopic.php?t=206391
> 
> Summary: How do I pvmove data with LVM2 if contiguous runs of
> PEs in the source LVs will have to be split up to make them fit?
> 
> Quick answer:
> LVM2 doesn't support this directly yet: it's being worked on.
> Until it's done you need to edit the metadata [using vgcfg*]
> to split the segments into smaller ones before running pvmove.
> [Might also need to recompile disabling section merging code
> which would undo your splitting.]
> 
> Alasdair
> --
> agk@redhat.com
> _______________________________________________
> 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/
> 

Thank you very much, I'm glad I finally got an answer.

I have another question for you now...

All I seem to have is vgcfgrestore and vgcfgbackup.. but by reading
the man pages I don't see how they edit the metadata.  Is there
another vgcfg that I am missing?

Thank you

Re: [linux-lvm] pvmove problem

[Alasdair G Kergon]

On Sat, Aug 07, 2004 at 11:54:31AM -0500, Alasdair G Kergon wrote:
> Summary: How do I pvmove data with LVM2 if contiguous runs of
> PEs in the source LVs will have to be split up to make them fit?
  
> Quick answer:
> LVM2 doesn't support this directly yet: it's being worked on.

This code is now in CVS for testing.

It lets you restrict the PEs you want to move. 
Can only move off one PV at once (ie. only one cmdline arg).

And of course you can still restrict the PEs available for allocation
by listing them afterwards, and/or use -n to restrict the PEs
moved to those belonging to a specific LV.

pvmove /dev/sda2:1000-1999 /dev/sdb1:1000-1499:2000- /dev/sdc1:500-1000

Alasdair
-- 
agk@redhat.com