LVreduce error HELP!!!!

[Pete Randall]

Thanks, S.K. - I missed the -f in my hurry to suppress the -R.

If it does come back and tell us to deactivate first, then we'll go for LVM maintenance mode.

Pete

[Babs_1]

Ok got myself all phsyced up entered the commands....
bash-2.05# vgcfgrestore -n /dev/vg00 /etc/lvmconf/vg00.conf.old /dev/dsk/c1t2d0
Usage: vgcfgrestore
[-R]
[-F]
{ -n vgname |
-f VGConfPath }
{ -l |
{[-o OldPVPath] PVPath}}
OldPVPath and PVPath : character special files
"/dev/dsk/c1t2d0": Too many arguments

What am I doing wrong :(

[Babs_1]

I added the -f

bash-2.05# vgcfgrestore -n /dev/vg00 -f /etc/lvmconf/vg00.conf.old /dev/dsk/c1t2d0
Usage: vgcfgrestore
[-R]
[-F]
{ -n vgname |
-f VGConfPath }
{ -l |
{[-o OldPVPath] PVPath}}
OldPVPath and PVPath : character special files
Illegal combination of options

any ideas?

[Pete Randall]

-f

[S.K. Chan]

.. I totally overlooked the char device file .. this would work ..
# vgcfgrestore -n /dev/vg00 -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c1t2d0

[Pete Randall]

Sorry, not doing too well here.

use the raw device /dev/rdsk/c1t2d0


Pete

[Marco Santerre]

From what I can see, it's either use the -n option OR the -f option.. so in this case use the -f only

[Babs_1]

bash-2.05# vgcfgrestore -n /dev/vg00 -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c1t2d0
Usage: vgcfgrestore
[-R]
[-F]
{ -n vgname |
-f VGConfPath }
{ -l |
{[-o OldPVPath] PVPath}}
OldPVPath and PVPath : character special files
Illegal combination of options

still not working ?
Thanks for all your help again everyone :)

[Marco Santerre]

one more thing I forgot.. use the /dev/rdsk also

[S.K. Chan]

Oh boy !! I just realized ..
this should be it !!
# vgcfgrestore -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c1t2d0

Sorry for the confusion !

[Babs_1]

bash-2.05# vgcfgrestore /dev/vg00 -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c1t2d0
Usage: vgcfgrestore
[-R]
[-F]
{ -n vgname |
-f VGConfPath }
{ -l |
{[-o OldPVPath] PVPath}}
OldPVPath and PVPath : character special files
"-f": Too many arguments

Took out the -n still no luck

[Pete Randall]

Marco's got it: use -f to specify the old config file but leave off the -n option (which normally points to the config file).

Pete

[Ken Hubnik_2]

take out the /dev/vg00 also.

[Marco Santerre]

Sorry I meant to take out anything that went with -n so you had to remove
-n /dev/vg00
altogether

[Babs_1]

It looks good...
bash-2.05# vgcfgrestore -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c1t2d0
Volume Group configuration has been restored to /dev/rdsk/c1t2d0


bash-2.05# vgcfgrestore -f /etc/lvmconf/vg00.conf.old /dev/rdsk/c2t2d0
Volume Group configuration has been restored to /dev/rdsk/c2t2d0

But the lvol in question still shows at 2gb and when I try to mount it it says its corrupt and needs checking...
When I tried to do a df -k
I got this
bash-2.05# df -k
/eztrack (/etc/auto.eztrack ) : 0 total allocated Kb
0 free allocated Kb
0 used allocated Kb
Floating point exception (core dumped)
Its bad isnt it....

[Pete Randall]

You're going to need to run fsck against the lvol in question, then mount it.

Pete

[Babs_1]

What is the syntax for running fsck? Here is what I have tried

bash-2.05# fsck /dev/dsk/lvol10
fsck: /etc/default/fs is used for determining the file system type
vxfs fsck: cannot stat /dev/dsk/lvol10

bash-2.05# fsck /u02
fsck: /etc/default/fs is used for determining the file system type
cannot open device /u02
file system check failure, aborting ...

Any ideas?

[James R. Ferguson]

Hi (again):

I think you are going to need to reboot in order to see if this worked or not.

BTW, I suggest you slow down before you make a major mistake.

Regards!

...JRF...

[Ken Hubnik_2]

I believe you have to use the character device file. /dev/rdsk/cXXXXXX

[Babs_1]

James,
I know, I am starting to panic a little......ok a lot...I will reboot and hope for the best :)
Will let you know what happens :)
Thanks so much to everyone who replied, all your help (and company) was appreciated during this crappy experience for me :)

[Pete Randall]

We'll keep our fingers crossed. Take slow, deep breaths.

[Babs_1]

Hi all, well its come back up and the lvol in question is still corrupt I tried running

bash-2.05# fsck /dev/rdsk/c1t2d0
fsck: /etc/default/fs is used for determining the file system type
invalid super-block
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...
And...

bash-2.05# fsck /u02
fsck: /etc/default/fs is used for determining the file system type
cannot open device /u02
file system check failure, aborting ...

I tried to mount but says still corrupt needs checking...

I guess it didnt work...

[John Palmer]

Babs,

keep taking those slow deep breaths...

What does lvdisplay say about the size of the lvol?

You should be running fsck -F vxfs -o full /dev/vg00/rlvol?
(assuming it's a VXFS filesystem)

Not on the disk name or the mountpoint.

Regards,
John

[Babs_1]

So if my lvol is corrupt and unmountable how do I free up the space, using fsadm? (which would have saved me allthis pain in the first place :( )
I guess I need to start doing some serious restoring and hope my backups are all there and working :)
I cant thank you all enough for all the help :)

[Babs_1]

Hi John,
Thanks for the reply :)
lvdisplay says it is still 2gb not the 13 it was this morning..

Here is the result of fsck

bash-2.05# fsck -F vxfs -o full /dev/vg00/rlvol10
vxfs fsck: file system had I/O error(s) on meta-data.
log replay in progress
vxfs fsck: fsck read failure bno = 3303352, off = 0, len = 8192
file system check failure, aborting ...

Oh well we tried our best...
Onto recovery!!!