Sponsored Content
Operating Systems Solaris Unable to see controller C1 on Solaris 8 Post 302997251 by hicksd8 on Wednesday 10th of May 2017 08:22:49 AM
Old 05-10-2017
What do you mean by 'maintenance slice'?

Please post the vtoc of c1t0d0s4

When you use volume management (meta) the meta database lives on a (usually) very small configured slice. That is where the OS keeps the information as to what is mirrored to what, what volumes are spanned across multiple spindles and the like. That slice is not a filesystem and is not mounted in the usual way (and is therefore not in vfstab).

So again, what do you mean by maintenance slice? Could it be the meta database slice (very small)?
 

10 More Discussions You Might Find Interesting

1. Solaris

Unable to uninstall package in Solaris

I am getting the below mentioned error while trying to unistall a package from a 2.8 Solaris box. Please help.. pkgrm: ERROR: unable to determine current run-state Removal of <PDMgr> failed (internal error). No changes were made to the system. (1 Reply)
Discussion started by: chrisanto_2000
1 Replies

2. Filesystems, Disks and Memory

HD Controller does not Work in Solaris

Hi, I'm attempting to build a raid Z NAS using solaris, but I only have 4 sata ports on my MB, so I bought a Rosewill RC-211 PCIe controller (adds 2 sata II ports). I'm new to solaris, but I understand that to add a new drive, you first run #devfsadm, which puts the files into /dev/dsk. I... (3 Replies)
Discussion started by: ciscocbee
3 Replies

3. Infrastructure Monitoring

unable to shutdown solaris 10

hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient. /etc(R)-bash-3.00$ init 6 /etc(R)-bash-3.00$ svc.startd: The system is coming down. Please wait.... (7 Replies)
Discussion started by: alienkidmj12
7 Replies

4. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

5. Solaris

unable to use thumbdrive in Solaris 10

hi friends, i had this problem in a Solaris 10 server when i inserted my thumbdrive, i can't find the device file containing usb. what should i do ? (2 Replies)
Discussion started by: Exposure
2 Replies

6. Solaris

unable to login Solaris 10

I have inherited a solaris 10 server. I went to log into it the other day over the console connection, and after sucessfully entering the password, I was booted back to the login prompt with no errors visible. If I enter an incorect password, the console displays 'incorrect password' and kicks... (8 Replies)
Discussion started by: Sol-nova
8 Replies

7. Solaris

Solaris 11 server as Primary Domain Controller

Hi, All of our servers run Solaris (currently 10, but looking to upgrade to 11). In each of our offices we have a server configured as a Primary Domain Controller via Samba to provide naming services to our Windoze users. I would like to continue with that arrangement, but I would also like... (2 Replies)
Discussion started by: wgkorb
2 Replies

8. Solaris

Unable to add printer in Solaris

HI I am unable to add printer in solaris (architecture is SUN and OS is Solaris 10) as I try to print the file it gives following error Failed to contact service for erp-cljCP2025: not-found Need help Regards (7 Replies)
Discussion started by: smazshah
7 Replies

9. Solaris

Unable to reboot Solaris

Hi, we have a sun sparc solaris 10 machine and recently there was a power failure and one of the server domain was down. So today morning i have powered up the domain and it returned me to ok prompt then i have booted the machine with disk from devalias, the system was up as normal and no error... (0 Replies)
Discussion started by: phanidhar6039
0 Replies

10. Solaris

Unable to get Solaris 11 Zone onto the network

Hello, I followed these instructions to create a Solaris 11 zone: http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-092-s11-zones-intro-524494.html And I am unable to ping anything from the Local Zone except for the IP address of the global zone. My global zone has an IP... (6 Replies)
Discussion started by: unblockable
6 Replies
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 which is a concept for hierarchially 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 (primarilly scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may the be set that apply to all processes of all units contained in that slice. Slices are organized hierarchially 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. 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(7) are allowed. Unless DefaultDependencies=false is used, slice units will implicitly 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 early boot or late system shutdown should disable this option. SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7) systemd 208 SYSTEMD.SLICE(5)
All times are GMT -4. The time now is 06:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy