From: Bob Booth - UIUC (booth@UIUC.EDU)
Date: Fri Jan 16 2004 - 13:26:57 EST
something has to be using the log for it to be open. Since you have another
log, most likely every filesystem in that VG is using the other log. Check
your filesystems file to see if any filesystems use the log that you show
as closed. Usually you only have one log per VG.
bob
On Fri, Jan 16, 2004 at 10:12:37AM -0800, admin@CF2TREE.COM wrote:
> Hi,
>
> My system: 7026-6H1 running AIX 5.1
>
> I did a 'lsvg -l' yesterday on one of the volume groups and found one of the
> jfslog to be 'closed/syncd'. I looked around, but I did not find any other
> problem associated with the drive where this jfslog is located. What caused it
> to go into "closed/syncd" state, and how I can turn it back to "open/syncd"?
>
> blah# lsvg -l archivevg
> archivevg:
> LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
> archpljfs1 jfslog 4 4 1 open/syncd N/A
> archdkpl1 jfs 538 538 1 open/syncd /archdkpl1
> archpljfs2 jfslog 4 4 1 closed/syncd N/A
> archdkpl2 jfs 538 538 1 open/syncd /archdkpl2
>
> TIA
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:31 EDT