Home > Cannot Log > Cannot Log Commit Record For Diskgroup

Cannot Log Commit Record For Diskgroup

Action: It is possible that this error results from a drive that failed to spin up. There are two possible causes of this error: Case 1: The /etc/vfstab file was erroneously updated to indicate the device for the /usr file system is a volume, but the volume Disks containing valid root mirrors are listed as part of the error message. Action: Use the vxdg reminor command to renumber all volumes in the offending disk group permanently.

A disk group is deported from one host using the -h option to cause the disk group to be auto-imported on reboot from another host. This can only happen if the operating system is not correctly tracking opens and closes. V-5-0-34 VxVM vxdmp NOTICE V-5-0-34 added disk array disk_array_serial_number A new disk array has been added to the host. There may be other error messages that appear which provide further information.

A more serious failure is indicated by error types of: Format error in configuration copy Invalid magic number Invalid block number Duplicate record in configuration Configuration records are inconsistent These Note that this requires that you restore data on the disks from backups. Otherwise, there may be problems with the drive. It can also happen as a result of Actions that caused all plexes to become unusable (for example, forcing the dissociation of subdisks or detaching, dissociation, or offlining of plexes). >>Action

The device node was removed by the administrator or by an errant shell script. >>Action For the reason "Device is already open," if you really want to run vxconfigd, then V-5-1-571 VxVM vxconfigd ERROR V-5-1-571 Disk group group, Disk disk: Skip disk group with duplicate name Two disk groups with the same name are tagged for auto-importing by the same host. If the second host was already auto-importing a disk group with the same name, then reboot of that host will yield this error. >>Action If you want to import both The disks may be considered invalid due to a mismatch between the host ID in their configuration copies and that stored in the /etc/vx/volboot file.

V-5-1-3025 VxVM vxconfigd ERROR V-5-1-3025 Unable to add portal for cluster vxconfigd was not able to create a portal for communication with the vxconfigd on the other node. Action: Reboot the system. Action: If two or more disks have been lost due to a controller or power failure, use the vxrecover utility to recover them once they have been re-attached to the system. If there is a configuration daemon process already running, then the -k option causes a SIGKILL signal to be sent to that process.

This happens if a volume's record identifier (rid) changes as a result of a disk group split that moved the original volume to a new disk group. V-5-1-4277 VxVM vxconfigd ERROR V-5-1-4277 cluster_establish: CVM protocol version out of range When a node joins a cluster, it tries to join at the protocol version that is stored in its V-5-1-124 VxVM vxconfigd ERROR V-5-1-124 Disk group group: update failed: reason Description: I/O failures have prevented vxconfigd from updating any active copies of the disk group configuration. The most common reason is "A virtual disk device is open." This implies that a VxVM tracing or volume device is open.

If the second host was already auto-importing a disk group with the same name, then reboot of that host will yield this error. Additional messages may appear to indicate other records detached as a result of the disk detach. V-5-1-569 VxVM vxconfigd ERROR V-5-1-569 Disk group group,Disk disk:Cannot auto-import group: reason Description: On system startup, vxconfigd failed to import the disk group associated with the named disk. This error will usually be followed by the error: vxvm:vxconfigd: ERROR: Disk group group: Disabled by errors >>Action If the underlying error resulted from a transient failure, such as a

V-5-1-1171 VxVM vxconfigd ERROR V-5-1-1171 Version number of kernel does not match vxconfigd The release of vxconfigd does not match the release of the Veritas Volume Manager kernel drivers. Action: None; the problem was corrected automatically. If, within a certain period of time, there is still a running configuration daemon process, the error message is displayed. If the volume is not mirrored, this message indicates that some data could not be read.

V-5-1-2928 VxVM vxdg ERROR V-5-1-2928 diskgroup: Configuration too large for configuration copies The disk group's configuration database is too small to hold the expanded configuration after a disk group move or If the vxtask list command does not show a task running for the volume, use the vxmend command to clear the TUTIL0 and PUTIL0 fields for the volume and all its A failing disk is indicated by a "Detached disk" message. V-5-1-2353 VxVM vxconfigd ERROR V-5-1-2353 Disk group group: Cannot recover temp database: reasonConsider use of "vxconfigd -x cleartempdir" [see vxconfigd(1M)].

V-5-1-2862 VxVM vxdg ERROR V-5-1-2862 object: Operation is not supported Description: DCO and snap objects dissociated by Persistent FastResync, and VVR objects cannot be moved between disk groups. V-5-0-110 VxVM vxdmp NOTICE V-5-0-110 disabled controller controller_name connected to disk array disk_array_serial_number Description: All paths through the controller connected to the disk array are disabled. V-5-1-2824 VxVM vxconfigd ERROR V-5-1-2824 Configuration daemon error 242 A node failed to join a cluster, or a cluster join is taking too long.

This is equivalent to failure of that disk. (Physical disks are located by matching the disk IDs in the disk group configuration records against the disk IDs stored in the Veritas

If the root file system is defined on a volume, then start and mount the root volume using the procedures defined in the "Recovery" appendix. Such name clashes are most likely to occur for snap objects and snapshot plexes. V-5-0-108 VxVM vxio WARNING V-5-0-108 Device major, minor: Received spurious close A close was received for an object that was not open. Use the -f option if you still want to disable this controller.

Any reason other than "A virtual disk device is open" does not normally occur unless there is a bug in the operating system or in VxVM. Consider adding more memory or paging space. This may be a serious problem for the general running of your system. V-5-0-258 VxVM vxdmp NOTICE V-5-0-258 removed disk array disk_array_serial_number A disk array has been disconnected from the host, or some hardware failure has resulted in the disk array becoming inaccessible to

See Repairing root or /usr file systems on mirrored volumes for information on how to fix problems with root or /usr file system volumes. Action: Restart the vxconfigd daemon.