10-20-2005
Check the output of the format command to check if the filesystem is smaller than the slice that it is mounted on. If it is, then you can use growfs to do your job. The man page will be available on any solaris system or you can go
here. If the filesystem is already occupying the entire slice, then you may have to create a new filesystem on a new slice, possibly a new disk.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I am new to shell scripting and would really appreciate if someone could help me with this question.
I have a directory structure as follows..
main directory is DATA under which i have different directories names fileserver01, fileserver02 ... till fileserver 15.
under each... (8 Replies)
Discussion started by: kasala
8 Replies
2. AIX
I am working in AIX 4.3.3 , here when we are doing one activity we ran out of space in one mount point, we need to increase the space in that mout point by reducing it in another mount point, can anybody help me out in carrying this activity.
Vipin (3 Replies)
Discussion started by: vipin77
3 Replies
3. UNIX for Advanced & Expert Users
I know very basic Unix commands s I would really appreciate the assistance of a Unix guru.
I am installing an application on a Sun server, when attempting to install I get an error that says I do not have enough space allocated for my install directory (/ACEMS). Error says it has 7235m but needs... (1 Reply)
Discussion started by: rhack
1 Replies
4. AIX
Host Name - xxxxxxx
IP Address - xxxxxxxxx
Alert Msg - The percentage of available storage space (DMXMemory) is low (49.54374442289481 percent).
Time received - 14:23
Time Logged - 14:55
Suggested Group - MR-UNIX (5 Replies)
Discussion started by: Nyiko
5 Replies
5. Programming
I have a directory, and I write some files in to that. How to throw the error exception when my directory is full. i.e. there is no disk space (2 Replies)
Discussion started by: SamRoj
2 Replies
6. Filesystems, Disks and Memory
Hello,
I have a little problem, I would like to know how to add disk space on an NCR version 4 and above all whether it still contains vdisk space
smp001-4 4.0 3.0
/dev/dsk/vdisk15 3940505 3807833 132672 97% /data
in the dktab :
/dev/dsk/vdisk15 mirror 2 ... (0 Replies)
Discussion started by: magnetic
0 Replies
7. AIX
Guy's
This is our page space , i want some information about page space and I want the good way to how to increase the page space and what's the recommended page space that need to be configured
Page Space Physical Volume Volume Group Size %Used Active Auto Type Chksum
hd6 hdisk0... (8 Replies)
Discussion started by: Mr.AIX
8 Replies
8. Solaris
hi friends, i am a new system adminstrator and i had a directory /h03 getting full at 95%, how do i give more space to bring down it to about 70% ? i cannot delete any files inside as it is all important to the applications
/dev/dsk/c1t3d0s0 64G 60G 3.8G 95% /h03
any idea ? (4 Replies)
Discussion started by: Exposure
4 Replies
9. Solaris
Hi
Please can I have some help in increasing /var in my solaris 10 server.
At the moment the size configured is small and I need to expand it:
df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 869M 510M 307M 63% /
/devices ... (16 Replies)
Discussion started by: fretagi
16 Replies
10. Solaris
Hello All,
I have solaris server running,
uname -a
SunOS host 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-280R
Filesystem Size Used Available Capacity Mounted on
/dev/md/dsk/d0 9.8G 8.7G 1.0G 90% /
/dev/dsk/c1t1d0s3 4.3G 7.7M 4.2G ... (17 Replies)
Discussion started by: gull05
17 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)