08-13-2009
Yes, assuming these 56 cylinders aren't already used by another slice.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
How can extend /usr filesystem in hp-ux 11.11 (I'm not using online JFS) ? (0 Replies)
Discussion started by: pedro_lezaeta
0 Replies
2. AIX
Hi Everybody,
Is it possible to extend a Filesystem by adding a new LV that exist on different VG to this Filesystem?
Thanks in advance. (6 Replies)
Discussion started by: aldowsary
6 Replies
3. Solaris
I am running solaris 10 with Veritas. I want to extend a filesystem. It's an oracle partition (/ora12). How can I find out if there is space available to expand the filesystem and then how does one extend it.
I'm from the HPUX world and so LVM was always how I did things.
Thanks
jackie (5 Replies)
Discussion started by: jackiebaron
5 Replies
4. Filesystems, Disks and Memory
OK I'm sure this question has been posed far too many times.
I have solaris 10 x86 with NO Veritas or Disksuite filesystems. Below is the output of df -k
# df -k
Filesystem kbytes used avail capacity Mounted on
/ 10485760 547513 9317128 6% /
/dev... (1 Reply)
Discussion started by: jackiebaron
1 Replies
5. Solaris
Hello
I need to expand a filesystem is full, but I understand that for this I need a volume manager like SVM or Veritas. I have installed solaris 10 but I give it a metastat and tells me there is no database, as if the installation does not have the sudmirrors attachments.
The filesystem... (1 Reply)
Discussion started by: cata
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local.
Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies
7. AIX
Hi Gurus,
I have Aix 5.3 server and would like to extend the following filesystem.
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/lv_mecdr 120.00 12.04 90% 560973 14% /home/mecdrBut there's only 16G for the VG, may be i can expand it... (11 Replies)
Discussion started by: thepurple
11 Replies
8. Solaris
Hi guys!
Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both.
I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys.
Thanks! (4 Replies)
Discussion started by: arah
4 Replies
9. AIX
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies
10. Solaris
Hello,
Need to ask the question regarding extending the zfs storage file system.
currently after using the command, df -kh
u01-data-pool/data 600G 552 48G 93% /data
/data are only 48 gb remaining and it has occupied 93% for total storage.
zpool u01-data-pool has more then 200 gb... (14 Replies)
Discussion started by: shahzad53
14 Replies
LEARN ABOUT DEBIAN
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)