From: Pascal Grostabussiat (pascal@azoria.com)
Date: Wed Feb 09 2005 - 12:27:24 EST
Hi all,
I don't know if anybody mentioned the problem, but I have never
seen it mentioned on this list so far. The problem is kind of odd
and may cause troubles to some of you on the field.
Keywords: Veritas Volume Manager (VxVM) 4.0, Solaris, logging,
encapsulation, nologging, boot, UFS
The problem is (or at least seems to be) that the latest version
of VxVM, version 4.0, does not handle UFS log area properly for
some reasons during encapsulation (might some trunking of the UFS
log area).
Everything will work fine as soon as you don't have any crash on
the machine, which usually requires the use of the UFS log area
on the encapsulated disks. As long as nothing happens, your machine
will boot properly and you won't encounter any problem.
However, if the machine crasches for some reasons, UFS log areas
will be used, and an error message will be displayed during the
boot sequence and the sequence stopped. This only concerns partitions
on encapsulated disks.
The work-around is to set "nologging" in the /etc/vfstab file for
those partitions that are on encapsulated disks. Up to Solaris 8
logging was not activated by default. But logging is activated by
default on UFS from Solaris 9 and above, unless "nologging" is set
as mount option.
If you are unlucky and encounter the problem, boot the machine in
single-user mode, mount the "/" partition, edit the /etc/vfstab file
accordingly, and boot your machine twice in order to clean the log
and boot without any logging.
Hope this saves you some time and troubles. I have encountered the
problem twice recently.
Regards,
/Pascal
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:08 EDT