Help with Raw file changes

[ConnieK]

I have a tasking to "reclaim" some storage space on an rp8400 - HPUX 11.11, Oracle DB server. A VG was created - vg_redo that is approximately 240 GB, with 64 raw filesystems. The tasking is to reclaim 200 GB and create a "cooked" filesystem and keep the 40GB as raw.

I have absolutely no idea exactly how to do this. I don't even know where to start. could someone please help me?

Thanks,

Connie

[Torsten.]

The first step could be to do

# vgdisplay -v vg_redo

and investigate what LVOLs are there and which of them you want to keep or delete.

[ConnieK]

Well, there are 64 lvols.

[Duncan Edmonstone]

Connie, do you know which lvols are no longer used? Thats the information you need first - presumably the DBAs can tell you that.

Attaching the output of "vgdisplay -v vg_redo" here would alos allow us to give you better advice.

HTH

Duncan

[Pete Randall]

How many physical volumes are involved? I would prefer to keep my cooked and raw spaces separate, hopefully in separate VGs, but that won't be possible if the physical volumes can't accomodate it. If we're stuck with just one VG, then, basically, all you need to do is run newfs against the lvols that are going to become cooked. You may prefer to lvremove them first and then lvcreate on 200GB lvol, but cooked vs raw is determined simply by which device file you use: /dev/vgXX/lvolYY or /dev/vgXX/rlvolYY.


Pete

[ConnieK]

4 Physical volumes are used. Here's the vgdisplay:

--- Volume groups ---
VG Name /dev/vg_redo
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 64
Open LV 64
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 17501
VGDA 8
PE Size (Mbytes) 4
Total PE 69996
Alloc PE 8064
Free PE 61932
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg_redo/REDO_01
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 126
Used PV 2

LV Name /dev/vg_redo/REDO_02
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 126
Used PV 2


etc.....

LV Name /dev/vg_redo/REDO_64
LV Status available/syncd
LV Size (Mbytes) 252
Current LE 63
Allocated PE 126
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c18t0d0
PV Name /dev/dsk/c20t0d0 Alternate Link
PV Status available
Total PE 17499
Free PE 13467
Autoswitch On

PV Name /dev/dsk/c18t1d0
PV Name /dev/dsk/c20t1d0 Alternate Link
PV Status available
Total PE 17499
Free PE 17499
Autoswitch On

PV Name /dev/dsk/c19t0d0
PV Name /dev/dsk/c21t0d0 Alternate Link
PV Status available
Total PE 17499
Free PE 13467
Autoswitch On

PV Name /dev/dsk/c19t1d0
PV Name /dev/dsk/c21t1d0 Alternate Link
PV Status available
Total PE 17499
Free PE 17499


I think I should tell the DBA to backup his redo logs to another location (another server). I remove the lovls and vg_redo. Create a new VG and lvol for his exports (cooked) and then create some of the raw lvols for his use. Does this make sense?

[Pete Randall · Accepted solution]

So it appears that the physical volumes are 60GB each. I would be inclined to use three of them in a VG that would contain your cooked space and one of them in another VG for raw space. To me, it would be an administrative nightmare trying to keep track of which LVs were raw and which were cooked if they were all mixed together in the same VG.

If the DBA can move his redo logs, that would be easiest. Just get rid of the existing VG (vgexport should accomplish this nicely), then re-create.


Pete

[ConnieK]

Pete, I believe you've just answered my questions. I've not really worked with raw files before (maybe once) and was not entirely sure what to do. Thank you for pointing me in the right direction and refreshing my somewhat "limited" memory.
You all are great to be so helpful!

[ConnieK]

All answered well as above, but Pete gave me the direction I needed.