09-18-2011
But if that's the case, how can I prove that the local files are copied on the other disk?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know how to force these rogue logical volumes to mirror to there respective disks?
DISK:Logical Volumes
03:cw_p05,cw_p01_01,cw_p01_02,lv00
09:cw_p05,cw_p01_01,cw_p01_02
04:cw_p01_phyldbs,cw_p01_03,cw_op01_01,cw_od01
10:cw_p01_phyldbs,cw_p01_03,cw_op01_01 (1 Reply)
Discussion started by: Optimus_P
1 Replies
2. Solaris
I hope I am posting in the correct forum.
I have a server - which I am installing solaris 9 on.
The server currently has 2 disks. I wish to run solaris 9 on one, and use the other as a mirror for the first one. ie. If the first one should ever fail, then I can swap to the mirror and just... (18 Replies)
Discussion started by: frustrated1
18 Replies
3. Solaris
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies
4. Infrastructure Monitoring
Here are the details.
cnjr-opennms>root$ zfs list
NAME USED AVAIL REFER MOUNTPOINT
openpool 20.6G 46.3G 35.5K /openpool
openpool/ROOT 15.4G 46.3G 18K legacy
openpool/ROOT/rds 15.4G 46.3G 15.3G /
openpool/ROOT/rds/var 102M ... (3 Replies)
Discussion started by: pupp
3 Replies
5. Solaris
Hi ,
I am new to SVM .when i try to learn RAID 1 , first they are creating two RAID 0 strips through
metainit d51 1 1 c0t0d0s2
metainit d52 1 1 c1t0d0s2
In the next step
metainit d50 -m d51
d50: Mirror is setup
next step is
metaattach d50 d52
d50 : submirror d52 is... (7 Replies)
Discussion started by: vr_mari
7 Replies
6. Solaris
Hi guys,
We had created a pool as follows:
zpool create filing_pool raidz c1t2d0 c1t3d0 ........
Due to some requirement, we need to destroy the pool and re-create another one. We wish to know now which disks have been included in the filing_pool, how do we list the disks used to create... (2 Replies)
Discussion started by: frum
2 Replies
7. Solaris
i have this pool1 on my sun4u sparc machine
bash-3.00# zpool get all pool1
NAME PROPERTY VALUE SOURCE
pool1 size 292G -
pool1 used 76.5K -
pool1 available 292G -
pool1 capacity 0% -... (1 Reply)
Discussion started by: Sojourner
1 Replies
8. HP-UX
what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies
9. Solaris
I have to do patching in single user mode in solaris 10 zfs root pool. Before that I have to detach the root mirror pool so that if patching fails then I can boot from detached root mirror pool. Please let me know how can I detach root pool
bash-3.2# zpool status
pool: rpool
state: ONLINE... (5 Replies)
Discussion started by: hb00
5 Replies
LEARN ABOUT XFREE86
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)