Re: disaster please help
From: Clifton, Pablo (Pablo.Clifton_at_BCBSFL.COM)
Date: 06/24/05
- Previous message: Mark Schlechte: "Re: SSA configuration question"
- Maybe in reply to: Gerard M. MAMOU: "disaster please help"
- Next in thread: Clifton, Pablo: "Re: disaster please help"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 24 Jun 2005 10:45:02 -0400 To: aix-l@Princeton.EDU
How about trying:
lspv (list disks)
lqueryvg -Atp hdiskXX (query what is on the disks-
from the lv names you should get an idea
which vg the disk belonged to)
importvg -y <vgname> hdiskXX
varyonvg <vgname>
for i in `lsvgfs <vgname>`
do
mount $i
done
-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
Gerard M. MAMOU
Sent: Thursday, June 23, 2005 2:44 AM
To: aix-l@Princeton.EDU
Subject: Re: disaster please help
Hello
question:
how do you force the vary on ?
question2:
I understand that the name of the uservg imported should not be rootvg.
For myself it is uservg.
My old config:
rootvg:
hdisk0
hdisk1
uservg:
hdisk2
hdisk3
My after crash config:
rootvg:
new disk of 18.2Go hdisk0
uservg:
not tested yet, I am afraid.
but probably
hdisk1
hdisk2
because the old hdisk1 is unpluged.
do you mean that I should do
importvg -y uservg hdisk1
--quoted from RM (thank you)--
If you had rootvg (on hdisk0/hdisk1), oraclevg (on hdisk2/hdisk3) and
datavg (on hdisk4) for example:
importvg -y oraclevg hdisk2 # (imports oraclevg which is on hdisk2
and hdisk3)
importvg -y datavg hdisk4
I usually use whatever disk shows up first in the hdisk list for the VG
to do the import, but I don't think it'd matter if you used hdisk3 in
that case...
Keep in mind you will still need to varyonvg each VG that you import,
and mount the filesystems...
--rm
</quoted>
even thought in the previous config the disk was labeled hdisk2 and
hdisk3 or should I plus another scsi disk in between as a new hdisk1?
question3:
what could I do with my old hdisk1, part of my old rootvg?
what will hapens if I do
importvg -y rootvg hdisk1?
could I get some LV in it back?
is it preferable to do
importvg -y oldrootvg hdisk1?
question4:
Please help on the command fsck?
and how do I get the LV in the imported VG?
with smitty?
Thank you
Gerard Mamou
.
On Wed, Jun 22, 2005 at 04:59:44PM -0400, Drew T wrote:
> Excellent explanation Simon.
>
> One question for clarification. What are the most common flags you
> normally run with fsck?
>
>
>
>
>
>
> "Green, Simon"
> <Simon.Green@EU.A To:
aix-l@Princeton.EDU
> LTRIA.COM> cc:
> Sent by: IBM AIX Subject: Re: disaster
please help
> Discussion List
> <aix-l@Princeton.
> EDU>
>
>
> 06/22/2005 05:03
> AM
> Please respond to
> IBM AIX
> Discussion List
>
>
>
>
>
> The importvg command will pick up the volume group information from
> the VGDA, which is present on every disk, (and nothing to do with
exportvg).
> You only need to do the importvg for one disk, and it doesn't matter
> which one. This will add all of the filesystems back: everything just
> the way it was.
>
> The name you use doesn't matter: whatever you like. Probably best to
> use the old one.
>
> Some of the filesystems may be damaged, if the system crashed whilst
> they were open. You can fix them with fsck.
>
> You *might* be able to do an importvg for hdisk1. You mustn't call it
> "rootvg", and you'll get error messages that it's got a missing
> volume, and duplicate LV/filesystem names. When you try to vary it on
> you'll have to force it, (probably: depends on the original Quorum).
>
> Also, if any of the filesystems were spread across both hdisk0 and
> hdisk1 they'll be damaged. An fsck should get them mountable, but
> you'll have lost data and you'll be lucky to get anything useful out
> of it. Unless there's something of vital importance there, I wouldn't
> bother.
>
> --
> Simon Green
>
> Altria ITSC Europe s.a.r.l.
>
> AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
> New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX
>
> N.B. Unsolicited email from vendors will not be appreciated.
> Please post all follow-ups to the list.
>
>
> -----Original Message-----
> From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
> Of Gerard M. MAMOU
> Sent: 22 June 2005 06:59
> To: aix-l@Princeton.EDU
> Subject: Re: disaster please help
>
>
> Hello
> thank you for your answer.
> question continued:
> if these old disks previously known as
> hdisk2 and hdisk3
> are also know (because I have also two disks for my new rootvg) should
> I type importvg -y uservg -P hdisk2 importvg -y uservg -P hdisk3
> meaning:
> should the vg_name uservg of these commands be the SAME as the old
> configuration how the new system knows that there is two disks in the
> uservg if I type only one time importvg -y uservg -P hdisk2
>
> will the system know about the LV in these two disks? how?
> Thank you
> Gerard Mamou
> .
>
>
> On Tue, Jun 21, 2005 at 01:46:06PM -0700, Patrick B. O'Brien wrote:
> > Get the pvid's of these hdisks;
> > lspv.
> >
> > Now do the following;
> > importvg -y vg_name -P pvid
> >
> >
> >
> >
> > -----Original Message-----
> > From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf
> > Of Gerard M. MAMOU
> > Sent: Tuesday, June 21, 2005 1:26 PM
> > To: aix-l@Princeton.EDU
> > Subject: disaster please help
> >
> > Hello
> > I have a rs6000 43p with rootvg(hdisk0 and hdisk1) and uservg(hdisk2
> > and hdisk3)
> >
> > The root vg hdisk0 does not boot.
> >
> > I tried to reinstall a mksysb on a new disk.
> > It worked fine.
> >
> > How do I get back my datas of hdisk2 and hdisk3 I did not backup
> > them, I did not exportvg them.
> >
> > What can I do with the hdisk1? Could I get the datas on it?
> >
> > Could I use linux with jfs support to mount the hdisk2 and hdisk3?
How?
> > Please help
> > Gerard Mamou
Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc. The information contained in this document may be confidential and intended solely for the use of the individual or entity to whom it is addressed. This document may contain material that is privileged or protected from disclosure under applicable law. If you are not the intended recipient or the individual responsible for delivering to the intended recipient, please (1) be advised that any use, dissemination, forwarding, or copying of this document IS STRICTLY PROHIBITED; and (2) notify sender immediately by telephone and destroy the document. THANK YOU.
- Previous message: Mark Schlechte: "Re: SSA configuration question"
- Maybe in reply to: Gerard M. MAMOU: "disaster please help"
- Next in thread: Clifton, Pablo: "Re: disaster please help"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
