01-08-2009
Space is available on slices, however I do not have any free slice which I can dedicate it only for metadb.
Kindly suggest me some thing where in I can use some the slice for metadb and also I can use it for other work I mean I should be in position to mount and work on..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm interested in adding more swap space to my current workstation (Solaris 10). I currently have 2 hard drives installed, however the system was only created with 512MB for swap that resides on drive 1. This drive is already sliced up and all slices are being used.
The second drive has two... (3 Replies)
Discussion started by: here2learn
3 Replies
2. 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
3. BSD
Now, I had installed free bsd at my office. Unfortunitely, Email server have been using Local PoP3 and SMTP to our ISP with outlook. but my unix firewall sever ( free bsd ) didn't allow these port ( 110 & 25 ).
How can i create the IP table to pass at server. If u have any experience about obvious... (4 Replies)
Discussion started by: Ashraff Ali
4 Replies
4. Linux
We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
5. 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
6. Solaris
Hi Gurus,
For a particular slice I have change the minfree from 10% to 1% with tunefs -m and its allowing the creation of file on that slice, however when I am seeing the same with df -k it says that the slice is 100% full.
What could be reason for this?
Thanks (2 Replies)
Discussion started by: kumarmani
2 Replies
7. Solaris
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
Discussion started by: incredible
10 Replies
8. Solaris
Hi,
I have inherited a system with two disks mirrored, and only 1 metadb on each, I have deleted the db on c1t1 and recreated 3 which is fine.
But when it comes to c1t0, the metadb -d /dev/dsk/c1t0d0s5 doesnt removed the existing db and the create metadb -a -f -c3 /dev/dsk/c1t0dos5 wont... (0 Replies)
Discussion started by: richard.tarlton
0 Replies
9. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
10. Solaris
I have a 240GB disk as rpool. I have installed Solaris 11.3 to a partition which is 110GB. Now I have another 130GB which is unallocated. I want to use that additional space as a temporary folder to be shared between Solaris and Linux. The additional space had no /dev/dsk/c2t4... entry so I used... (8 Replies)
Discussion started by: kebabbert
8 Replies
LEARN ABOUT CENTOS
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 which is a concept for hierarchially 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 (primarilly scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may the
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchially 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.
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(7) are allowed.
Unless DefaultDependencies=false is used, slice units will implicitly 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 early boot or late system shutdown
should disable this option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
systemd 208 SYSTEMD.SLICE(5)