12-22-2008
oh, this is for testing only so it is not matter for cylinders size.
I had create the mirror and submirror last weekend. 2 submirror refer to both slice 7 in different disk. but I still cannot mount back the slice 7. It also had problem when i boot-up server, typically it is go the GRUB login interface.
This is login interface warning.
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
I'd like to add two new disk (mirrored each other) in a machine still on line.
The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk.
who could send me exemples or tell me how to... (1 Reply)
Discussion started by: guillaume35
1 Replies
2. UNIX for Advanced & Expert Users
Can any one Explain the artichture of Slice on SOLARIS PLATFORM.
OR else
where can i found artical on these topic.
akram shaik OCA
akram_tri_a@yahoo.com (2 Replies)
Discussion started by: smdakram
2 Replies
3. Solaris
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
4. UNIX for Advanced & Expert Users
I umount one filesystem like this:
# umount -F /export/home1
Then I tried to mount it back as:
# mount /dev/dsk/c1t0d0s6 /export/home1
mount: I/O error
mount: cannot mount /dev/dsk/c1t0d0s6
partition /dev/dsk/c1t0d0s6 and directory /export/home1 all exist in the system. Why can I not... (5 Replies)
Discussion started by: duke0001
5 Replies
5. AIX
Hi ,
Can you suggest me how to back to back printing in UNIX? Is there any way?
Kindly advise.
Regards
Vijaya Amirtha Raj (3 Replies)
Discussion started by: amirthraj_12
3 Replies
6. Solaris
Hey guys,
This is how I originally had my drive setup... This is on a solaris 10 box
***BEFORE***
Current Disk = c0t1d0
Current partition table (original):
Total disk cylinders available: 7506 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks... (2 Replies)
Discussion started by: kingdbag
2 Replies
7. IP Networking
Hi every body,
Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber.
Note it is direct connection & there is no switches between the servers.
I'm concern about using HBA adapters, it is possible or not.
Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies
8. Solaris
Part Tag Flag Cylinders Size Blocks
0 root wm 259 - 2666 4.70GB (2408/0/0) 9863168
1 swap wu 3 - 258 512.00MB (256/0/0) 1048576
2 backup wm 0 - 4091 7.99GB (4092/0/0) 16760832
3... (4 Replies)
Discussion started by: chidori
4 Replies
9. Solaris
I'm new to UNIX, sort of inherited this job. I have an HP lefthand SAN, where I added 100GB to one of the volumes. As I understand I also have to expand the volume on the server (solaris 10 ) as well. So, how do I do that? The file system is called: sybdump. the mount point is /export/xxx/sybdump.... (19 Replies)
Discussion started by: Spaseman
19 Replies
LEARN ABOUT MOJAVE
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)