Solaris 2.6 - Duplicate Filesystem to a larger slice(same drive)
One of our production systems has a slice called "oldslice" that periodically runs low on space during normal operation. We have minimum requirements for online data retention, and whoever sized this slice didn't give it much wiggle room, so it periodically runs low on space. I'm getting tired of archive files every other week in response to low space alerts.
I discovered(I inherited these systems ) that there is an unused slice on the same drive that is several times larger than then problematic one.
I've used newfs to make a filesystem on the unused slice, and have mounted it under /mnt/newslice .
Now I want to duplicate oldslice's contents to newslice. There are a number of ways to do this, but I want the most reliable and least resource intensive one to do it while the system is active.
This looks promising if it doesn't use too many resources -
ideas?
Last edited by the.gooch; 06-21-2011 at 11:15 PM..
Reason: more info
I have encountered my first problem of the year at work with one of our NMS servers. We would like to migrate Cisco Works to Solaris, as it is currently running on NT. The NMS is already running OpenView NNM 6.2 (primary NMS program). Anyhow the /var slice is only 6 mb and is almost full, as... (2 Replies)
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)
I have a drive that I need to make a sector-by-sector or exact image copy of. In Windows, I use a program call Ghost by Symantec, but the version I have does not support Unix.
Does anyone know of a good product for Unix?
Thanks,
Brett Gibson
Gibson Teldata, Inc. (13 Replies)
I am using Solaris Sparc 10,and facing some issues.
HD:80gb ; Root = 11gb(currently using) , I have made a parttition in the c0t0d0s2 slice(which is of 60gb & the partition tag is 'usr'),and I have done newfs on -> /dev/dsk/c0t0d0s2 which is mounted on /export (having ufs filesystem).
Now... (6 Replies)
I'm new to UNIX, sort of inherited this job. I have an HP lefthand SAN, where I added 100GB to one of the volumes. As I understand I also have to expand the volume on the server (solaris 10 ) as well. So, how do I do that? The file system is called: sybdump. the mount point is /export/xxx/sybdump.... (19 Replies)
Hi,
I have a problem again and I hope that someone on this forum will help me in solving it. My English is weak, but I'll try to describe it clearly.
I have an old computer ( HP B180) with HP-UX 10.20. I've done the hard disk image using G4L and replaced the drive. Old drive has 4.3 GB and 9.1... (7 Replies)
I like to increase swap size for my current server running solaris 10.
Seems like the system is not using it's full 16G of physical memory.
#swap -l
swapfile dev swaplo blocks free
/dev/dsk/c0t0d0s1 32,1 16 1058288 1058288
# swap -s
total: 4125120k bytes... (17 Replies)
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
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)