08-11-2005
SUN dos not recommend to use slice 2 for general data storage.
Thats the reason why you cant partition slice 2 during solaris installation (the installer just shows you slice 1,3 and so on)
However, it should work at all.
9 More Discussions You Might Find Interesting
1. 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
2. Solaris
Has anyone managed to set up disk mirroring in Solaris 10 yet? If so can you point me in the direction of some useful documentation please.
Cheers (25 Replies)
Discussion started by: korfnz
25 Replies
3. Solaris
Hi Friends,
I am having Sun Solaris 5.8 OS installed having 2 different size hard disk, sizes are c0t0d0s0(160 GB) and c0t2d0s0 (40GB). I have installed Sun Solaris 5.8 OS in c0t0d0s0 (160GB) harddisk.
I have configured all the parameters required for disk mirroring. But when executing... (4 Replies)
Discussion started by: Vijayakumarpc
4 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
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
8. 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
9. 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
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)