I think you are out of luck unfortunately. UFS filesystems generally can't be grown. I believe your only choice would be to make a full backup, reinstall solaris laying out the filesystems how you want, then restore from your backup.
sry, but that's not true:
see:
you see? disksuite is complicated, but mighty.... if you are dealing with root partitions it's a pit more sophisticated. i am not sure if it will work to make a concat on the root partitions, never tried it, but i think it won't work. depending on how big your /export/home is you could dump it somewhere to, repartion your harddisk and increase the number of blocks for your root partition with the "format" menue, let the rootslice grow with "growfs", make a new fs on /export/home and restore the dump. i could imagine many ways to do it, e.g. you could use your second disk for /export/home, use the solaris feature to use a file for swapping (could be changed on the fly) and make new partitions on the 2nd disk and restore the system configuration...
but to be honest, if you are not used with solaris, it would be the easiest way for you to reinstall the system, sry
Quote:
Just Ice
also a way to do it, i like your script... but on that, you would need a downtime.... belongs to you
I tried to build a 1.3 TB volume with disk suite, and recieved an error (don't remember the exact verbage, it was very late). It only built a 1 TB volume. newfs completed without error. I rebuilt the volume to be just under 1TB, and all was fine. Is there a limitation with disk suite, or ufs, that... (3 Replies)
Hello all,
I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Hi
I am a bit green to AIX - but when our backup operator tries to do a restore from one AIX box to another, he get's the error:
'A file cannot be larger than the value set by ulimit'
I am wondering what is the impact of increasing the AIX filesize limit of 2 gb to unlimited. And how would... (1 Reply)
Hi frnz,
Need an urgent help...
I have installed solaris 8 in a sunblade workstation with 136GB hdd.
While installation it has taken a default filesystem size as 1.37GB for root.
AFtr completing the installation i have extended the root partition to 130GB.
But still df output shows... (4 Replies)
Hi All,
I am writing a block driver for a 2GB SD card where i get the total amount of data per request as follows:
struct request *req;
uint card_addr,total_bytes;
struct request_queue *rq = BlkDev->queue;
req = elv_next_request(rq);
..
..
card_addr = req->sector*512;... (1 Reply)
Hey all!
I was hoping someone knew anything about this one...
I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately)
Now I know you can increase this amount but is there any point?
The reason I am asking this is that I've setup mirroring on... (2 Replies)
Hi,
I have recently taken up to support these SunOS 5.9 sun4u sparc SUNW,Sun-Fire-V240 boxes and got a request to increase the size of /backup01 as its getting filled up quickly and can't play much on it as these are production servers. As I have no idea about how to do this, can anyone let me... (0 Replies)
Hi
Please let me know how to increase the size of /tmp file system from 512m to 1024m dynamically without reboot in solaris zone
# df -h
Filesystem size used avail capacity Mounted on
zones/zone1 11G 1.0G 10.0G 10% /
/dev 11G 1.0G ... (6 Replies)
Discussion started by: sb200
6 Replies
LEARN ABOUT MINIX
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 237SYSTEMD.SLICE(5)