* [linux-lvm] help
@ 2005-05-05 12:26 Colm G. Connolly
2005-05-05 12:33 ` Martin Eisenhardt
2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
0 siblings, 2 replies; 11+ messages in thread
From: Colm G. Connolly @ 2005-05-05 12:26 UTC (permalink / raw)
To: linux-lvm
Hi all,
I've just got a new 250G hard drive and have been trying to add it to an
exitiing lvm2 setup on my system. However, I've screwed something up
and now I can't mount the volume which is /dev/HOME_VG/HOME_LV and
contains an XFS file system.
My question is this: how I can I restore the original configuration so
that I can see the contents of the logical volume?
I've included a transcript of the commands I've run to make this mess.
I'm running
# lvm version
LVM version: 2.01.04 (2005-02-09)
Library version: 1.01.00-ioctl (2005-01-17)
Driver version: 4.4.0
on Linux 2.6.11.7 SMP i686 on a Debian/testing system
The transcript of commands I've run is as follows
461 pvcreate /dev/hdd
462 pvscan
463 mount
464 vgextend HOME_VG /dev/hdd
465 pvscan
466 man xfs_growfs
467 df -h
468 xfs_growfs /home
468 didn't work since I hadn't extended the logical volume.
469 df -h
470 pvscan
471 man pvscan
472 pvscan -v
473 pvscan -vv
474 lvscan
475 man lvextend
476 man lvextend
477 mount
478 lvextend /dev/HOME_VG/HOME_LV /dev/hdd
479 lvextend /dev/HOME_VG/HOME_LV
480 lvextend -L250G /dev/HOME_VG/HOME_LV
481 lvscan
482 mount
483 df -h
At this point I got a bit concerned that I had added 250G to the logical
volume but pvdisplay only reported a capicity of 232.88G even though hdd
is a 250G hard drive. So I started to try to remove the
484 lvreduce -L250G /dev/HOME_VG/HOME_LV
485 lvreduce -L-250G /dev/HOME_VG/HOME_LV
None of these reduction attempts worked. lvreduce complained that it was
unable to reduce below 1 extent.
486 pvdisplay
487 lvdisplay
488 lvscan
489 vgreduce /dev/HOME_VG/HOME_LV /dev/hdd
490 vgreduce /dev/HOME_VG /dev/hdd
491 ls /var/lock/lvm/
492 lvscan
493 lvdisplay
494 lvresize
495 lvresize -L-250G /dev/HOME_VG/HOME_LV
496 lvreduce -L-250G /dev/HOME_VG/HOME_LV
Neither of these commands worked either.
497 man lvmchange
498 man lvs
499 lvs
500 pvs
501 lvmdiskscan
502 lvmreduce -L -250G /dev/HOME_VG/HOME_LV
503 /sbin/lvmreduce -L -250G /dev/HOME_VG/HOME_LV
504 which lvmreduce
505 which lvm
506 ls /sbin/lvm*
507 ls -l /sbin/lvm*
508 lvreduce -L -250G /dev/HOME_VG/HOME_LV
509 lvscan
510 lvmdiskscan
511 pvdisplay
512 pvdisplay /dev/hdd
513 man pvmove
514 pvmove -v /dev/hdd
515 man lvchange
516 lvscan
517 lvscan -vv
518 lvreduce -L-250G /dev/HOME_VG/HOME_LV
519 mount -oro /home
520 mount
521 df -h
522 umount /home
523 lvscan
524 lvdisplay
525 pvdisplay
Up to this point I could mount /dev/HOME_VG/HOME_LV on /home no problem
526 lvreduce -L -232.88G /dev/HOME_VG/HOME_LV
This command worked and the volume group was reduced. But from now this
point on I can no longer mount the volume group
527 lvscan
528 lvdisplay
529 mount -oro /home
530 lvscan
531 lvmdiskscan
532 pvscan
533 man xfs_repair
534 man xfs_check
535 xfs_check /dev/HOME_VG/HOME_LV
can't seek in filesystem at bb 36633600
can't read superblock for ag 30
can't seek in filesystem at bb 37854720
can't read superblock for ag 31
536 h|grep mount
537 mount -oro /home
This command reports
mount: /dev/mapper/HOME_VG-HOME_LV: can't read superblock
538 man vgcfgrestore
539 cd /etc/lvm/
540 sl
541 cd backup/
542 ls
543 less HOME_VG
544 less HOME_VG
545 man vgcfgrestore
546 vgcfgrestore -v HOME_VG
547 mount -o ro /home/
This command reports
mount: /dev/mapper/HOME_VG-HOME_LV: can't read superblock
At this point I've stopped. I can't figure out how to undo the damage
I've done. And I really need to recover the original setup. There is
stuff on the logical volume for which I have no backup. How I wish I'd
taken my own advice and backed the important stuff up.
Right now pvscan reports
PV /dev/hdc1 VG HOME_VG lvm2 [9.32 GB / 0 free]
PV /dev/hda5 VG HOME_VG lvm2 [8.82 GB / 1.01 GB free]
PV /dev/hdd VG HOME_VG lvm2 [232.88 GB / 232.88 GB free]
Total: 3 [251.02 GB] / in use: 3 [251.02 GB] / in no VG: 0 [0 ]
and
# lvmdiskscan
/dev/hda1 [ 47.03 MB]
/dev/hdc1 [ 9.32 GB] LVM physical volume
/dev/hda2 [ 8.79 GB]
/dev/hda3 [ 1019.75 MB]
/dev/hda5 [ 8.82 GB] LVM physical volume
/dev/hdd [ 232.89 GB] LVM physical volume
/dev/hdb1 [ 6.01 GB]
0 disks
4 partitions
1 LVM physical volume whole disk
2 LVM physical volumes
root@darwin:/etc/lvm/backup# lvs
lvs lvscan
root@darwin:/etc/lvm/backup# lvscan
ACTIVE '/dev/HOME_VG/HOME_LV' [17.12 GB] inherit
root@darwin:/etc/lvm/backup# pvdisplay
--- Physical volume ---
PV Name /dev/hdc1
VG Name HOME_VG
PV Size 9.32 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 2385
Free PE 0
Allocated PE 2385
PV UUID XzBfoB-cV7O-hIzQ-3Tjn-jam0-IBXw-MJKV5W
--- Physical volume ---
PV Name /dev/hda5
VG Name HOME_VG
PV Size 8.82 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 2257
Free PE 259
Allocated PE 1998
PV UUID NIO6ey-B8gt-APxD-BEOP-cmpd-UCBf-KY2rLB
--- Physical volume ---
PV Name /dev/hdd
VG Name HOME_VG
PV Size 232.88 GB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 59618
Free PE 59618
Allocated PE 0
PV UUID 2hYdvL-9I7I-tz01-Rhza-ZLyp-tsTp-niP5pJ
Any help most gratefully appreciated.
Thanks in advance,
--
Colm G. Connolly, Tel: +353-1-716-2855
Dept. of Computer Science, Fax: +353-1-269-7262
University College Dublin, MSN: colmconn@hotmail.com
Belfield, Dublin 4, �ire. Web: http://inismor.ucd.ie/~colmconn/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] help
2005-05-05 12:26 [linux-lvm] help Colm G. Connolly
@ 2005-05-05 12:33 ` Martin Eisenhardt
2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
1 sibling, 0 replies; 11+ messages in thread
From: Martin Eisenhardt @ 2005-05-05 12:33 UTC (permalink / raw)
To: linux-lvm
Hello Colm,
On Thursday 05 May 2005 14:26, Colm G. Connolly wrote:
> I've just got a new 250G hard drive and have been trying to add it to an
> [...]
> 482 mount
> 483 df -h
>
> At this point I got a bit concerned that I had added 250G to the logical
> volume but pvdisplay only reported a capicity of 232.88G even though hdd
> is a 250G hard drive. So I started to try to remove the
I know that this is *not* your main concern but I think it worth noting that
the size of your 250G harddisk was correctly reported as being 232.88G. The
reason being that harddisk vendors use 1G = 1000^3 while computer science
defines 1G = 1024^3. (Note: I think there are some standard definition by the
IEEE(?) but I don't have a URL for that.)
So 250*1000^3 = 250.000.000.000 ~ 232.8*1024^3
Wish you all the luck for the problems remaining!
Kind regards
Martin Eisenhardt
--
Dipl.Wirtsch.Inf.(Univ.) Martin Eisenhardt
Bamberg University
Media Informatics
D - 96045 Bamberg
fon: +49 (951) 863 - 2856
fax: +49 (951) 863 - 2852
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] help
2005-05-05 12:26 [linux-lvm] help Colm G. Connolly
2005-05-05 12:33 ` Martin Eisenhardt
@ 2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
2005-05-05 15:05 ` David Mohr
1 sibling, 1 reply; 11+ messages in thread
From: Diaz Rodriguez, Eduardo @ 2005-05-05 13:16 UTC (permalink / raw)
To: LVM general discussion and development
your first error: don't made backup.
your second error:
# From LVM how to
xfs
There is no way to shrink XFS file systems.
If your are touch lvm2 you must know that about 250Gx1000 and 233x1024.
try use xfs_repair -n for see the reparis..
I use (but it is only a personal opinion, this is very dangerous)
(use again the first commands).
vgextend my_volume_group /dev/hdc1
lvextend -L250G /dev/HOME_VG/HOME_LV
lvscan
In this point use xfs_repair -n
If you see good, use xfs_repair (pray)....
if you don't have luck try xfs_repair -d (after of this reboot) (read man
xfs_repair)
try to mount. (pray again).....
good luck
On Thu, 05 May 2005 13:26:43 +0100, Colm G. Connolly wrote
> Hi all,
>
> I've just got a new 250G hard drive and have been trying to add it
> to an exitiing lvm2 setup on my system. However, I've screwed
> something up and now I can't mount the volume which is
> /dev/HOME_VG/HOME_LV and contains an XFS file system.
>
> My question is this: how I can I restore the original configuration
> so that I can see the contents of the logical volume?
>
> I've included a transcript of the commands I've run to make this mess.
>
> I'm running
>
> # lvm version
> LVM version: 2.01.04 (2005-02-09)
> Library version: 1.01.00-ioctl (2005-01-17)
> Driver version: 4.4.0
>
> on Linux 2.6.11.7 SMP i686 on a Debian/testing system
>
> The transcript of commands I've run is as follows
>
> 461 pvcreate /dev/hdd
> 462 pvscan
> 463 mount
> 464 vgextend HOME_VG /dev/hdd
> 465 pvscan
> 466 man xfs_growfs
> 467 df -h
> 468 xfs_growfs /home
>
> 468 didn't work since I hadn't extended the logical volume.
>
> 469 df -h
> 470 pvscan
> 471 man pvscan
> 472 pvscan -v
> 473 pvscan -vv
> 474 lvscan
> 475 man lvextend
> 476 man lvextend
> 477 mount
> 478 lvextend /dev/HOME_VG/HOME_LV /dev/hdd
> 479 lvextend /dev/HOME_VG/HOME_LV
> 480 lvextend -L250G /dev/HOME_VG/HOME_LV
> 481 lvscan
> 482 mount
> 483 df -h
>
> At this point I got a bit concerned that I had added 250G to the
> logical volume but pvdisplay only reported a capicity of 232.88G
> even though hdd is a 250G hard drive. So I started to try to remove the
>
> 484 lvreduce -L250G /dev/HOME_VG/HOME_LV
> 485 lvreduce -L-250G /dev/HOME_VG/HOME_LV
>
> None of these reduction attempts worked. lvreduce complained that it
> was unable to reduce below 1 extent.
>
> 486 pvdisplay
> 487 lvdisplay
> 488 lvscan
> 489 vgreduce /dev/HOME_VG/HOME_LV /dev/hdd
> 490 vgreduce /dev/HOME_VG /dev/hdd
> 491 ls /var/lock/lvm/
> 492 lvscan
> 493 lvdisplay
> 494 lvresize
> 495 lvresize -L-250G /dev/HOME_VG/HOME_LV
> 496 lvreduce -L-250G /dev/HOME_VG/HOME_LV
>
> Neither of these commands worked either.
>
> 497 man lvmchange
> 498 man lvs
> 499 lvs
> 500 pvs
> 501 lvmdiskscan
> 502 lvmreduce -L -250G /dev/HOME_VG/HOME_LV
> 503 /sbin/lvmreduce -L -250G /dev/HOME_VG/HOME_LV
> 504 which lvmreduce
> 505 which lvm
> 506 ls /sbin/lvm*
> 507 ls -l /sbin/lvm*
> 508 lvreduce -L -250G /dev/HOME_VG/HOME_LV
> 509 lvscan
> 510 lvmdiskscan
> 511 pvdisplay
> 512 pvdisplay /dev/hdd
> 513 man pvmove
> 514 pvmove -v /dev/hdd
> 515 man lvchange
> 516 lvscan
> 517 lvscan -vv
> 518 lvreduce -L-250G /dev/HOME_VG/HOME_LV
> 519 mount -oro /home
> 520 mount
> 521 df -h
> 522 umount /home
> 523 lvscan
> 524 lvdisplay
> 525 pvdisplay
>
> Up to this point I could mount /dev/HOME_VG/HOME_LV on /home no problem
>
> 526 lvreduce -L -232.88G /dev/HOME_VG/HOME_LV
>
> This command worked and the volume group was reduced. But from now
> this point on I can no longer mount the volume group
>
> 527 lvscan
> 528 lvdisplay
> 529 mount -oro /home
> 530 lvscan
> 531 lvmdiskscan
> 532 pvscan
> 533 man xfs_repair
> 534 man xfs_check
> 535 xfs_check /dev/HOME_VG/HOME_LV
>
> can't seek in filesystem at bb 36633600
> can't read superblock for ag 30
> can't seek in filesystem at bb 37854720
> can't read superblock for ag 31
>
> 536 h|grep mount
> 537 mount -oro /home
>
> This command reports
> mount: /dev/mapper/HOME_VG-HOME_LV: can't read superblock
>
> 538 man vgcfgrestore
> 539 cd /etc/lvm/
> 540 sl
> 541 cd backup/
> 542 ls
> 543 less HOME_VG
> 544 less HOME_VG
> 545 man vgcfgrestore
> 546 vgcfgrestore -v HOME_VG
> 547 mount -o ro /home/
>
> This command reports
> mount: /dev/mapper/HOME_VG-HOME_LV: can't read superblock
>
> At this point I've stopped. I can't figure out how to undo the
> damage I've done. And I really need to recover the original setup.
> There is stuff on the logical volume for which I have no backup. How
> I wish I'd taken my own advice and backed the important stuff up.
>
> Right now pvscan reports
> PV /dev/hdc1 VG HOME_VG lvm2 [9.32 GB / 0 free]
> PV /dev/hda5 VG HOME_VG lvm2 [8.82 GB / 1.01 GB free]
> PV /dev/hdd VG HOME_VG lvm2 [232.88 GB / 232.88 GB free]
> Total: 3 [251.02 GB] / in use: 3 [251.02 GB] / in no VG: 0 [0 ]
>
> and
>
> # lvmdiskscan
> /dev/hda1 [ 47.03 MB]
> /dev/hdc1 [ 9.32 GB] LVM physical volume
> /dev/hda2 [ 8.79 GB]
> /dev/hda3 [ 1019.75 MB]
> /dev/hda5 [ 8.82 GB] LVM physical volume
> /dev/hdd [ 232.89 GB] LVM physical volume
> /dev/hdb1 [ 6.01 GB]
> 0 disks
> 4 partitions
> 1 LVM physical volume whole disk
> 2 LVM physical volumes
> root@darwin:/etc/lvm/backup# lvs
> lvs lvscan
> root@darwin:/etc/lvm/backup# lvscan
> ACTIVE '/dev/HOME_VG/HOME_LV' [17.12 GB] inherit
>
> root@darwin:/etc/lvm/backup# pvdisplay
> --- Physical volume ---
> PV Name /dev/hdc1
> VG Name HOME_VG
> PV Size 9.32 GB / not usable 0
> Allocatable yes (but full)
> PE Size (KByte) 4096
> Total PE 2385
> Free PE 0
> Allocated PE 2385
> PV UUID XzBfoB-cV7O-hIzQ-3Tjn-jam0-IBXw-MJKV5W
>
> --- Physical volume ---
> PV Name /dev/hda5
> VG Name HOME_VG
> PV Size 8.82 GB / not usable 0
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 2257
> Free PE 259
> Allocated PE 1998
> PV UUID NIO6ey-B8gt-APxD-BEOP-cmpd-UCBf-KY2rLB
>
> --- Physical volume ---
> PV Name /dev/hdd
> VG Name HOME_VG
> PV Size 232.88 GB / not usable 0
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 59618
> Free PE 59618
> Allocated PE 0
> PV UUID 2hYdvL-9I7I-tz01-Rhza-ZLyp-tsTp-niP5pJ
>
> Any help most gratefully appreciated.
>
> Thanks in advance,
>
> --
> Colm G. Connolly, Tel: +353-1-716-2855
> Dept. of Computer Science, Fax: +353-1-269-7262
> University College Dublin, MSN: colmconn@hotmail.com
> Belfield, Dublin 4, �ire. Web: http://inismor.ucd.ie/~colmconn/
>
> _______________________________________________
> 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/
=======================================================================================
El otro regalo de los viejos.
=======================================================================================
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] help
2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
@ 2005-05-05 15:05 ` David Mohr
2005-05-07 14:18 ` Colm G. Connolly
0 siblings, 1 reply; 11+ messages in thread
From: David Mohr @ 2005-05-05 15:05 UTC (permalink / raw)
To: LVM general discussion and development
Hi,
On 5/5/05, Diaz Rodriguez, Eduardo <ediaz@pk25.com> wrote:
> # From LVM how to
>
> xfs
> There is no way to shrink XFS file systems.
>
> If your are touch lvm2 you must know that about 250Gx1000 and 233x1024.
>
> try use xfs_repair -n for see the reparis..
I don't think that's an issue here because the history that was posted
did not include an xfs_grow after he grew the LV. As such this should
IMO be a pure LVM issue, because XFS was not grown.
> I use (but it is only a personal opinion, this is very dangerous)
> (use again the first commands).
> vgextend my_volume_group /dev/hdc1
> lvextend -L250G /dev/HOME_VG/HOME_LV
> lvscan
Hmm, I agree that it sounds a bit "dangerous" but it might be worth a shot.
> In this point use xfs_repair -n
> If you see good, use xfs_repair (pray)....
> if you don't have luck try xfs_repair -d (after of this reboot) (read man
> xfs_repair)
> try to mount. (pray again).....
See above, should not be necessary.
~David
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] help
2005-05-05 15:05 ` David Mohr
@ 2005-05-07 14:18 ` Colm G. Connolly
0 siblings, 0 replies; 11+ messages in thread
From: Colm G. Connolly @ 2005-05-07 14:18 UTC (permalink / raw)
To: LVM general discussion and development
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
David Mohr wrote:
> Hi,
>
> On 5/5/05, Diaz Rodriguez, Eduardo <ediaz@pk25.com> wrote:
>
>># From LVM how to
>>
>>xfs
>>There is no way to shrink XFS file systems.
>>
>>If your are touch lvm2 you must know that about 250Gx1000 and 233x1024.
>>
>>try use xfs_repair -n for see the reparis..
>
>
> I don't think that's an issue here because the history that was posted
> did not include an xfs_grow after he grew the LV. As such this should
> IMO be a pure LVM issue, because XFS was not grown.
Yep. I never changed the size of teh XFS filesystem. The issue was with the
underlying LVM geometry.
>
>
>>I use (but it is only a personal opinion, this is very dangerous)
>>(use again the first commands).
>>vgextend my_volume_group /dev/hdc1
>>lvextend -L250G /dev/HOME_VG/HOME_LV
>>lvscan
>
>
> Hmm, I agree that it sounds a bit "dangerous" but it might be worth a shot.
Well it worked. I've since copied everything off the logical volume and
recreated it with the correct size.
>
>
>>In this point use xfs_repair -n
>>If you see good, use xfs_repair (pray)....
>>if you don't have luck try xfs_repair -d (after of this reboot) (read man
>>xfs_repair)
>>try to mount. (pray again).....
>
>
> See above, should not be necessary.
Thanks to all for the help.
Regards,
--
Colm G. Connolly | Tel : +353-1-716-2855
Department of Computer Science | Fax : +353-1-269-7262
University College Dublin (UCD) | Web : http://inismor.ucd.ie/~colmconn
Belfield, Dublin 4, �ire | MSN : colmconn@hotmail.com
[-- Attachment #2: Colm.Connolly.vcf --]
[-- Type: text/x-vcard, Size: 328 bytes --]
begin:vcard
fn:Colm G. Connolly
n:Connolly;Colm
org:University College Dublin;Computer Science
adr:;;Belfield;Dublin;;4;Ireland
email;internet:Colm.Connolly@ucd.ie
title:Dr
tel;work:+353-1-716-2855
tel;fax:+353-1-269-7262
tel;cell:+353-86-307-8186
x-mozilla-html:FALSE
url:http://inismor.ucd.ie/~colmconn
version:2.1
end:vcard
^ permalink raw reply [flat|nested] 11+ messages in thread
* [linux-lvm] help
@ 2001-07-26 15:42 Pierre Lamb
0 siblings, 0 replies; 11+ messages in thread
From: Pierre Lamb @ 2001-07-26 15:42 UTC (permalink / raw)
To: linux-lvm
I placed the 2 required commands in rc.sysinit (rh71)
before hte section "Mounting other file"
gave vgscan the -d option and left vgchange -ay.
During the boot process I see where vscan uodated
lvmtab and lvmtab.d and it say successfull but when I
look into lvmd.d it is empty. after I log in then do
the vgscan the correct entries are made. Ant help
would be appreciated.
Pierre
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
^ permalink raw reply [flat|nested] 11+ messages in thread
* [linux-lvm] Help.
@ 2001-07-22 4:36 Ben Konosky
2001-07-22 4:40 ` Steven Lembark
2001-07-23 7:52 ` Heinz J. Mauelshagen
0 siblings, 2 replies; 11+ messages in thread
From: Ben Konosky @ 2001-07-22 4:36 UTC (permalink / raw)
To: linux-lvm
I had a VG that had three PVs in it, one of the PVs failed, is there any
way to trick the VG into thinking it only has two PVs in it so I can
*try* to mount it and see what data I can pull off the remainder. The
file system is reiserfs, and it was the third PV in the group that died.
Thanks in advance,
Ben Konosky
bkonosky@texas.net
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Help.
2001-07-22 4:36 [linux-lvm] Help Ben Konosky
@ 2001-07-22 4:40 ` Steven Lembark
2001-07-22 5:00 ` Ben Konosky
2001-07-23 7:52 ` Heinz J. Mauelshagen
1 sibling, 1 reply; 11+ messages in thread
From: Steven Lembark @ 2001-07-22 4:40 UTC (permalink / raw)
To: linux-lvm
- Ben Konosky <bkonosky@texas.net> on 07/21/01 23:36:47 -0500:
> I had a VG that had three PVs in it, one of the PVs failed, is there any
> way to trick the VG into thinking it only has two PVs in it so I can
> *try* to mount it and see what data I can pull off the remainder. The
> file system is reiserfs, and it was the third PV in the group that died.
vgexport and import it back with the valid PV's. You'll loose whatever
was on the missing PV. If any of the LV's spanned PV's then you'll loose
those LV's.
sl
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Help.
2001-07-22 4:40 ` Steven Lembark
@ 2001-07-22 5:00 ` Ben Konosky
0 siblings, 0 replies; 11+ messages in thread
From: Ben Konosky @ 2001-07-22 5:00 UTC (permalink / raw)
To: linux-lvm
vgexport -a gives no volume groups found. vgexport myvg gives volume
group "myvg" doesn't exist.
And yes, I had one LV spanning across all three PVs.
Steven Lembark wrote:
>- Ben Konosky <bkonosky@texas.net> on 07/21/01 23:36:47 -0500:
>
>>I had a VG that had three PVs in it, one of the PVs failed, is there any
>>way to trick the VG into thinking it only has two PVs in it so I can
>>*try* to mount it and see what data I can pull off the remainder. The
>>file system is reiserfs, and it was the third PV in the group that died.
>>
>
>vgexport and import it back with the valid PV's. You'll loose whatever
>was on the missing PV. If any of the LV's spanned PV's then you'll loose
>those LV's.
>
>sl
>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Help.
2001-07-22 4:36 [linux-lvm] Help Ben Konosky
2001-07-22 4:40 ` Steven Lembark
@ 2001-07-23 7:52 ` Heinz J. Mauelshagen
2001-07-24 2:02 ` Ben Konosky
1 sibling, 1 reply; 11+ messages in thread
From: Heinz J. Mauelshagen @ 2001-07-23 7:52 UTC (permalink / raw)
To: linux-lvm
On Sat, Jul 21, 2001 at 11:36:47PM -0500, Ben Konosky wrote:
> I had a VG that had three PVs in it, one of the PVs failed, is there any
> way to trick the VG into thinking it only has two PVs in it so I can
> *try* to mount it and see what data I can pull off the remainder. The
> file system is reiserfs, and it was the third PV in the group that died.
Ben,
you mention in our other e-mail, that you had an LV spanning all 3 disks
containig a reiserfs.
If your PV is lost *and* you don't have an actual backup, you'll loose fs
data anyway :-(
If you still want to get the LV *partially* back, you need a replacement
disk/partition of the same size the gone PV had, vgcfgrestore(8) the LVM
metadata to it and run "vgscan;vgchange -ay".
>
> Thanks in advance,
> Ben Konosky
> bkonosky@texas.net
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
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] 11+ messages in thread* Re: [linux-lvm] Help.
2001-07-23 7:52 ` Heinz J. Mauelshagen
@ 2001-07-24 2:02 ` Ben Konosky
0 siblings, 0 replies; 11+ messages in thread
From: Ben Konosky @ 2001-07-24 2:02 UTC (permalink / raw)
To: linux-lvm
That didn't work :( Now that I look at it, that drive must have been the
first one in the VG/LV :( At least I had most, but not all of the data
on that LV backed up. Well, now I know better than to use a drive in a
LV that used to be in a computer that was under adverse conditions(like
my car), without keeping all the data backed up.
Thanks for all the help,
Ben Konosky
Heinz J. Mauelshagen wrote:
>On Sat, Jul 21, 2001 at 11:36:47PM -0500, Ben Konosky wrote:
>
>>I had a VG that had three PVs in it, one of the PVs failed, is there any
>>way to trick the VG into thinking it only has two PVs in it so I can
>>*try* to mount it and see what data I can pull off the remainder. The
>>file system is reiserfs, and it was the third PV in the group that died.
>>
>
>Ben,
>
>you mention in our other e-mail, that you had an LV spanning all 3 disks
>containig a reiserfs.
>If your PV is lost *and* you don't have an actual backup, you'll loose fs
>data anyway :-(
>
>If you still want to get the LV *partially* back, you need a replacement
>disk/partition of the same size the gone PV had, vgcfgrestore(8) the LVM
>metadata to it and run "vgscan;vgchange -ay".
>
>>Thanks in advance,
>>Ben Konosky
>>bkonosky@texas.net
>>
>>
>>_______________________________________________
>>linux-lvm mailing list
>>linux-lvm@sistina.com
>>http://lists.sistina.com/mailman/listinfo/linux-lvm
>>read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>>
>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2005-05-07 14:18 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-05 12:26 [linux-lvm] help Colm G. Connolly
2005-05-05 12:33 ` Martin Eisenhardt
2005-05-05 13:16 ` Diaz Rodriguez, Eduardo
2005-05-05 15:05 ` David Mohr
2005-05-07 14:18 ` Colm G. Connolly
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 15:42 Pierre Lamb
2001-07-22 4:36 [linux-lvm] Help Ben Konosky
2001-07-22 4:40 ` Steven Lembark
2001-07-22 5:00 ` Ben Konosky
2001-07-23 7:52 ` Heinz J. Mauelshagen
2001-07-24 2:02 ` Ben Konosky
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.