01-08-2016
Slice 4 isn't being used, but to make it part of /var it would have to contain blocks adjacent to slice 3. You could merge slice 0 and slice 4 to grow /, but you can't use the blocks in slice 4 to grow slice 3.
You could move slices 0 and 1 to use lower numbered blocks (keeping the same sizes) and and expand slice 3 using blocks no longer being used at the end of the current slice 1 to expand the start of slice 3.
This User Gave Thanks to Don Cragun For This Post:
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hello,
I need to increase /var on a DG-UX R4.2 AViion Pentium Pro box - having never used DG-UX I'm unsure how to do this - can anyone point me in the right direction? Also, can I do it with the system up or do I have to take it to single user mode??
MAny thanks. (0 Replies)
Discussion started by: AnneliseW
0 Replies
2. UNIX for Dummies Questions & Answers
I know very basic Unix commands s I would really appreacite 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 sapce allocated for my install directory. Error says it has 7235m but needs 15360m.... (2 Replies)
Discussion started by: rhack
2 Replies
3. HP-UX
Question
I am not a hp admin but aix admin.
I am wondering if to increase the fs /var we really have to umount the fs so means stop the system ... just to do an extendlv ?
It is what I saw on man page of extendlv and that surprise me. On aix we can dynamically increase a fs and with version... (2 Replies)
Discussion started by: touny
2 Replies
4. AIX
Is there a limit of 512Mb when doing a "chfs -a size=XXXXX /myfs" ?
I managed to increase /var to 512MB fine, no issues, then i wanted to increase /usr to 2Gb, but when i enter:
# chfs -a size=2260992 /usr
chfs: 0506-908 Cannot reduce size... (5 Replies)
Discussion started by: craigp84
5 Replies
5. Filesystems, Disks and Memory
I trying to calculate drive space with RAID. I know the equation is:
(n-1)/n * drive capacity
but, when I use that my calculations don't come out when I compare to what I already know exists:
I have 3 - 18.2gb SCSI drives that contain two logical drives C & D.
Using the math, (3-1)/3 * 18.2... (1 Reply)
Discussion started by: JTalbot017
1 Replies
6. AIX
Hi
have IBM aix. unix
my directories are full
when i use
$ df -k
filesystem kbytes used avail capacity mounted on
/dev/root 288880 288880 288880 100% /
/proc 0 0 0 ... (4 Replies)
Discussion started by: raosurya
4 Replies
7. 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
8. 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
9. 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
10. Solaris
I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated
# df -k /var
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/var 13241195 12475897 674524 96% /var
# fstyp /dev/vx/dsk/var
ufs
# pkginfo... (1 Reply)
Discussion started by: amity
1 Replies
LEARN ABOUT HPUX
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)