|
|
Sponsored Content
Operating Systems
Linux
Red Hat
ORACLE RAC ASM disk question
Post 302168354 by robotronic on Monday 18th of February 2008 05:22:25 AM
02-18-2008
There's an oracle metalink note (368840.1) explaining that, but isn't very detailed:
Oracle's mysteries 
Quote:
"... information for the partitions and other data is contained in a special structure stored within the first 512 bytes of the disk, on the first cylinders. This structure is called VTOC (Volume Table of Contents). Actions like re-writting the VTOC will cause loosing the disk.
The output displayed above is a typical configuration, where slice 0 was formatted using the hole disk. When using ASM and during the disk discovery, the previous configuration is the cause for missing disks or disks not been discovered. The reason seems to be that having partitions that start at cylinder 0, the complete partition is interpreted as the VTOC area which is not used as a regular partition of the disk."
The output displayed above is a typical configuration, where slice 0 was formatted using the hole disk. When using ASM and during the disk discovery, the previous configuration is the cause for missing disks or disks not been discovered. The reason seems to be that having partitions that start at cylinder 0, the complete partition is interpreted as the VTOC area which is not used as a regular partition of the disk."
|
|
We Also Found This Discussion For You
1. Solaris
Hi,
Can any one please provide the command to format an Oracle Raw Disk in Solaris 10.
I have been used the following commands:
dd if=/dev/zero of=<raw disk path>
Thanks
---------- Post updated at 12:20 PM ---------- Previous update was at 10:11 AM ----------
Well this didn't give... (0 Replies)
Discussion started by: Mack1982
0 Replies
LEARN ABOUT MOJAVE
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk SYNOPSIS
systemd-machine-id-commit.service DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk file system. See machine-id(5) for more information about machine IDs. This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes. See systemd-machine-id-setup(1) for details. The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase. This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to make it permanent. SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1) systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)