[gudmo]

I have a problem that I'm reasonably sure I can fix but I'm not all that happy with the solution so I'm hoping someone here can offer a better one.

I recently lost a PV for a VG and on the PV was the log volume for the VG.
Now, I've created a new loglv did a logform on it and changed /etc/filesystems to reflect that and also given a "chfs -a log=/dev/newlog /filesystem/mount/path"

My problem is that that the system still doesn't change the loglv to the new one and I'm pretty sure I have to unmount the fs to change to the new one but there must be a better solution, does anyone know how to do this on the fly without losing the fs?

Raw problemshooting data

root[]@x00401:/> lsvg -p data02vg
data02vg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
vpath6 missing 1023 1022 205..205..204..203..205
vpath57 active 1023 66 00..00..00..00..66
vpath58 active 1023 0 00..00..00..00..00

root[]@x00401:/> lspv -l vpath6
vpath6:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
data02log 1 1 00..00..00..01..00 N/A

root[]@x00401:/> lsvg -l data02vg
data02vg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
data02log jfs2log 1 1 1 open/syncd N/A
data02lv jfs2 1979 1979 2 open/syncd /oracle/data/dgli/01
data02loglv jfs2log 1 1 1 closed/syncd N/A

[seth]

Hi

You can't change a log device for a lv without "closing" it (for FS this means umount). Well the loss of the log is not that bad if your FS stays clean, log is only necessary to repair a FS. When you just umount a FS cleanly there should be no need for that. You might get troubles the missing disk was part of the FS as well. In that case I recommend backing up all data first before doing umounts an other things.

Cheers seth