- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: mistake
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2003 06:38 PM
тАО06-15-2003 06:38 PM
I destroyed logical volume informations on an array. the array was seen by 2 machines. one pv was used by one machine so it was "unused" on the other. I configured the pv as a lv on the other machines. I have data backup but I cant go back to my previous settings. Any informations on how I could do this ?
The volume group is deactivated.
bash-2.03# vgremove vgapps /dev/dsk/c3t1d0
vgremove: Volume group not activated.
bash-2.03# pvremove /dev/rdsk/c3t1d0
pvremove: The physical volume "/dev/rdsk/c3t1d0" belongs to volume group "/dev/vgapps".
pvremove: Couldn't remove physical volume "/dev/rdsk/c3t1d0".
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-15-2003 07:57 PM
тАО06-15-2003 07:57 PM
Re: mistake
# vgexport /dev/vgapps
You can't use 'pvremove' if the volume belongs to a volume group. The man pages for 'pvremove' states this.
Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2003 03:44 AM
тАО06-16-2003 03:44 AM
Re: mistake
I still have troubles when trying to import the volume group since it is not activated. I dont seem to be able to do anything with it.
bash-2.03# vgimport -m vgapps.map -p -v vgapps
Beginning the import process on Volume Group "vgapps".
vgimport: Volume group "/dev/vgapps" already exists in the "/etc/lvmtab" file.
bash-2.03# vgremove /dev/vgapps
vgremove: Volume group not activated.
and if I try to activate it...the lost logical volumes info is the trouble.
bash-2.03# vgchange -a y /dev/vgapps
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c3t1d0":
Cross-device link
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c5t0d0":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c3t1d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c5t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vgapps":
Quorum not present, or some physical volume(s) are missing.
Regards,
Olivier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2003 05:24 AM
тАО06-16-2003 05:24 AM
Solutionvgchange -a y /dev/vg##
b) Verify disks
strings /etc/lvmtab
-and-
vgcfgrestore -f /etc/lvmconf/vg##.conf -l
c) Ghost disk procedure
Is 'quorum not present' when you:
vgchange -a y /dev/vg##
..then..
vgchange -a y -q n /dev/vg##
vgreduce -f /dev/vg## (* force out missing PV *)
d) Recovery of data when no vg but pv. Use -s option in vgexport and vgimport. The -s option will cause all pv's to report in.
vgexport -p -v -s -m /tmp/vg##_mapfile /dev/vg##
(* -p preview *)
mkdir /dev/vg##
mknod /dev/vg##/group c 64 0x0#0000
vgimport -s -p -m /tmp/vg##_mapfile /dev/vg##
(* -p preview *)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2003 07:16 AM
тАО06-16-2003 07:16 AM
Re: mistake
I was able to recover the data even if a fs was created over.
The procedure is a bit different than michael ( I recover directly from the pv).
# verify if configuration still there
$ vgcfgrestore -n vgapps -l
$ strings /etc/lvmtab
# restore configuration
$ vgcfgrestore -n vgapps /dev/rdsk/c3t1d0
# re-active volume group
$ vgchange -a y vgapps
# check if corrent
$ vgdisplay -v vgapps
#recreate /etc/mnttab
$ rm mnttab
$ mount -v
#remount everything that was in the lv
#fsck the affected LVs
fsck -F hfs /dev/vgapps/lvol
fsck -F vxfs /dev/vg
...