04-10-2008
is c1t0d0s0 your root filesystem? you need free space on your disk for the meta db's. when i do a fresh install of solaris i allways give 100mb to slice 6 and slice 7. you never know what happens to your machine the next day
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My company had purchased a Pro Model hard disk duplicator a couple of years ago and has used it successfully until our disk drive vendor stopped production of the currently used drives and offered us what they considder to be a direct replacement drive.
On these new drives everything matches the... (3 Replies)
Discussion started by: crazykelso
3 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. HP-UX
Im following the directions from
Mirroring the Root File System and Primary Swap
#
Mirror the root logical volume to the above disk:
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t3d0
#
Mirror the primary swap logical volume:
lvextend -m 1 /dev/vg00/prswaplv /dev/dsk/c0t3d0
#
... (1 Reply)
Discussion started by: csaunders
1 Replies
5. Shell Programming and Scripting
I'm not sure how to best explain what I'd like to do, so let me give an example. I used to work in a department that deals with internet security. This department had an "internal" website (only people in the building can get on it) and an "external" website (anyone in the world can get on it --... (1 Reply)
Discussion started by: sstevens
1 Replies
6. Solaris
hi every body
I'm new to solaris and I need your help in how to configure disk mirroring for 4 hard disks so that two of them will be replica to the other two ...???
Thanxx (7 Replies)
Discussion started by: mm00123
7 Replies
7. AIX
Hello,
On a RS6000 server I have two disks (hdisk0 and hdisk1) which are mirrored in a logical volume rootvg.
Yesterday one of these disks failed. Diagnosis, physical death.
It has therefore been replaced by a brand-new.
In terms of parameters, hdisk1 is now N# 1 in bootlist,... (2 Replies)
Discussion started by: titione
2 Replies
8. 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
9. 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
10. Solaris
Hello,
I need some help mirroring my rpool.
I have a 60gb ssd running the rpool alone and want to mirror it for redundancy so I bought a 120gb ssd that I found for a good price. 60gb drives aren't as easy to find at a good price anymore it seems.
I (a bit naively) thought after reading... (9 Replies)
Discussion started by: Zorken
9 Replies
LEARN ABOUT MINIX
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)