09-30-2010
Can the mirroring be done on a system that already has information in the partitions.
Also on many of these sites they say put the Metadb in slice 7, will I need to create this slice?
10 More Discussions You Might Find Interesting
1. Solaris
Hi
I have two raw disk that I want to mirror and then create soft partition on that. Could someone please help in the steps required
c0t1d0
c0t0d0
Thanks
Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies
2. Solaris
I am running Solaris 10 and i need to mirror a 73 gig HD. How do you mirror one in Solaris? (2 Replies)
Discussion started by: dewsdwarfs
2 Replies
3. SCO
How Can I Do Mirroring In Unix? (0 Replies)
Discussion started by: DIMITRIOSDOUMOS
0 Replies
4. Solaris
hai i am working on sun with T3 storage i am having 2 storage mirrored T3a andT3b . nowT3b is showing faulty that is the digital to optical coverter is not workig so it has to be replaced. since it will take another 5 days due to some reasons. i want to know will it create any problem while... (2 Replies)
Discussion started by: sasiprabu
2 Replies
5. UNIX for Dummies Questions & Answers
Over the last few months the HDD spins louder and louder, so I fiqured its time to replace the HDD. Its been running 24/7/365 since 98 :eek:. yes i said since 98 :D
I have an IBM system 43P Model 240. 233 MHz. running AIX Version 4.
The current HDD is an IBM DGHS COMP IEC -950
FRU PN#... (5 Replies)
Discussion started by: Chevy89rocks
5 Replies
6. Solaris
Really sorry for the long posting. But i would really want to clear all the doubts.
I have 2 disk c0t0d0 & c0t1d0, i wanted to mirror c0t1d0 (mirror) to c0t0d0 (main).
Creating state database replica:
metadb -a -c3 -f c0t0d0s7
... (3 Replies)
Discussion started by: beginningDBA
3 Replies
7. Solaris
Hi All
i wish to mirror the root disk, but i face the below error.
root@saturn # metainit d11 1 1 c0t0d0s0
metainit: saturn: c0t0d0s0: is mounted on /
kindly assist... (27 Replies)
Discussion started by: SmartAntz
27 Replies
8. Solaris
Hello,
I just build a Solaris 10 server on an x86 box. I forgot to mirror the two disks when I install the OS. Can I get some help with this?
I have this
# zpool list
rpool 278G 5.77G 272G 2% ONLINE -
# zpool status
pool: online
state: ONLINE
scan: none requested
config:
... (12 Replies)
Discussion started by: bitlord
12 Replies
9. Red Hat
Hi,
How to identify whether the disk is being mirrored or not in RHEL (2 Replies)
Discussion started by: gsiva
2 Replies
10. AIX
Hi Folks,
I am facing an issue with the performance.
P4 with 1 processor and 16 GB RAM and SAN HDD = Oracle report takes 25 minutes
P5 with 2 processors and 16 GB RAM internall HDD with LPAR = Oracle Report takes 1 hour 15 minutes ( please note I have assigned all the max processors and... (7 Replies)
Discussion started by: filosophizer
7 Replies
LEARN ABOUT V7
systemd.slice
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)
NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice unit. A slice unit is a concept for hierarchically
managing resources of a group of processes. This management is performed by creating a node in the Linux Control Group (cgroup) tree. Units
that manage processes (primarily scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchically in a tree. The name of the
slice encodes the location in the tree. The name consists of a dash-separated series of names, which describes the path to the slice from
the root slice. The root slice is named -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
Note that slice units cannot be templated, nor is possible to add multiple names to a slice unit by creating additional symlinks to its
unit file.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic
[Unit] and [Install] sections. The slice specific configuration options are configured in the [Slice] section. Currently, only generic
resource control settings as described in systemd.resource-control(5) are allowed.
See the New Control Group Interfaces[1] for an introduction on how to make use of slice units from programs.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o Slice units automatically gain dependencies of type After= and Requires= on their immediate parent slice unit.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Slice units will automatically have dependencies of type Conflicts= and Before= on shutdown.target. These ensure that slice units are
removed prior to system shutdown. Only slice units involved with late system shutdown should disable DefaultDependencies= option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
NOTES
1. New Control Group Interfaces
https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
systemd 237 SYSTEMD.SLICE(5)