12-27-2010
Is this a testing machine based on an production machine, and you want to apply the mirroring procedure to the production machine later? Or is it just for experimenting? If the later, I'd say scrap it and set up mirroring during the installation (less hassle).
9 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies
3. Solaris
Hey Guys,
I am using a Sun sparc server and had 6 disks.
The root was loaded on c0t10d0s0 disk.
I made an image or mirrored the root to another disk c0t9d0s0.
But during the process instead of attaching submirrors to main mirror
(d0 <--- d01 and d11) i attached d0 <--- d01 and... (1 Reply)
Discussion started by: rjcool
1 Replies
4. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
5. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
6. Solaris
Hello All,
I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me.
--- iostat command shows the disk to be similiar
--- format command shows disk to be different :confused:
--- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies
7. Solaris
I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system
and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies
8. Solaris
I would like to perform root disk mirroring task. Can someone please help me out on this.
Thanks !!
Regards,
Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
9. AIX
Hello Team,
In one of our machine which running in AIX 6.1 we doing the root mirroring. Currently the OS booted from the local disk and we have mirrored that in to the SAN disk. All went well and both are synced but when we making it as a multiboot its throwing the below error. Kindly... (4 Replies)
Discussion started by: gowthamakanthan
4 Replies
LEARN ABOUT CENTOS
machine-id
MACHINE-ID(5) machine-id MACHINE-ID(5)
NAME
machine-id - Local machine ID configuration file
SYNOPSIS
/etc/machine-id
DESCRIPTION
The /etc/machine-id file contains the unique machine ID of the local system that is set during installation. The machine ID is a single
newline-terminated, hexadecimal, 32-character, lowercase machine ID string. When decoded from hexadecimal, this corresponds with a
16-byte/128-bit string.
The machine ID is usually generated from a random source during system installation and stays constant for all subsequent boots.
Optionally, for stateless systems, it is generated during runtime at boot if it is found to be empty.
The machine ID does not change based on user configuration or when hardware is replaced.
This machine ID adheres to the same format and logic as the D-Bus machine ID.
Programs may use this ID to identify the host with a globally unique ID in the network, which does not change even if the local network
configuration changes. Due to this and its greater length, it is a more useful replacement for the gethostid(3) call that POSIX specifies.
The systemd-machine-id-setup(1) tool may be used by installer tools to initialize the machine ID at install time.
RELATION TO OSF UUIDS
Note that the machine ID historically is not an OSF UUID as defined by RFC 4122[1], nor a Microsoft GUID; however, starting with systemd
v30, newly generated machine IDs do qualify as v4 UUIDs.
In order to maintain compatibility with existing installations, an application requiring a UUID should decode the machine ID, and then
apply the following operations to turn it into a valid OSF v4 UUID. With "id" being an unsigned character array:
/* Set UUID version to 4 --- truly random generation */
id[6] = (id[6] & 0x0F) | 0x40;
/* Set the UUID variant to DCE */
id[8] = (id[8] & 0x3F) | 0x80;
(This code is inspired by "generate_random_uuid()" of drivers/char/random.c from the Linux kernel sources.)
HISTORY
The simple configuration file format of /etc/machine-id originates in the /var/lib/dbus/machine-id file introduced by D-Bus. In fact, this
latter file might be a symlink to /etc/machine-id.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), gethostid(3), hostname(5), machine-info(5), os-release(5), sd-id128(3), sd_id128_get_machine(3)
NOTES
1. RFC 4122
https://tools.ietf.org/html/rfc4122
systemd 208 MACHINE-ID(5)