Sponsored Content
Operating Systems Solaris Solaris 10 c0t0d0p0 Vs. c0t0d0s0 Post 302554253 by DukeNuke2 on Sunday 11th of September 2011 04:26:44 AM
Old 09-11-2011
p0 is the whole disk while 1, 2, 3 and 4 are the partitions. so there are 4 possible primary partitions!
 

5 More Discussions You Might Find Interesting

1. Solaris

"/" c0t0d0s0 showing 100%.

hi I recently started looking after server with sunsolaris os. it is dual host system. In one server the '/' showing 56% in other it is showing 100% in df -k. the status of slice was used avail capacity mounted on /dev/dsk.c0t0d0s0 961181 95**** 0 100%... (4 Replies)
Discussion started by: prabir
4 Replies

2. Solaris

What is c0t0d0s0?

I always thought c=controller, t=target, d=disk, s=slice. How exactly are they assigned? My internal drive is c0t1d0. But if I connect an external box, it jumps to c2t10d0, c2t11d0 etc. Is t=target? What exactly does those t-numbers mean and why does it jump to t10, t11 instead of going... (5 Replies)
Discussion started by: the_red_dove
5 Replies

3. 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

4. Solaris

root disk mirroring in solaris volume manager for solaris 10

Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment. Let me know if you need any deatils on this. Thanks, Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies

5. Solaris

Solaris ssh client hangs when connecting to another Solaris machine

Got a strange problem. I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10. When I try to ssh from one Solaris 10 server to another server ssh hangs. I have an identical server and when I try this everything works fine. The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
volencap(8)						      System Manager's Manual						       volencap(8)

NAME
volencap, volreconfig - Encapsulates disks, partitions, or AdvFS domains SYNOPSIS
/usr/sbin/volencap [-g diskgroup] [-p volprefix] [privlen=nn] [nconfig=nn] { diskname | partition_name | domain_name }... /usr/sbin/volencap -k { diskname | partition_name | domain_name }... /usr/sbin/volencap -k -a /usr/sbin/volencap -s /sbin/volreconfig OPTIONS
Puts the encapsulated disk into the disk group specified by disk group ID or disk group name. Instructs volencap to use the specified vol- prefix as the prefix for LSM volume names generated. This is useful if the LSM volume names generated already exist. Instructs volencap to remove any pending encapsulation requests for the specified disk(s), partition(s), or domain(s). Instructs volencap to remove all pending encapsulation requests. Displays all pending encapsulation requests. DESCRIPTION
Disk partitions that have data can be added to LSM using the encapsulation process. This enables users with existing data in disk parti- tions to easily migrate to the use of LSM volumes instead of disk partitions. The /usr/sbin/volencap command is used to encapsulate one or many disk partitions or AdvFS domains. If an individual partition is specified for encapsulation, the volencap command creates a nopriv disk and a volume for that partition. If an entire disk is specified, the volencap command creates a nopriv disk and volume for each in-use partition on the disk. If an AdvFS domain is specified, all disk partitions in the domain are converted to LSM volumes. You can use the volencap command to encapsulate the partitions on the boot disk, including the root file system, primary swap, usr and var partitions, to place them under LSM control. See the Logical Storage Manager manual for more information on encapsulating these partitions. The volencap command can be run directly or through the voldiskadm menus. The volencap command generates LSM commands that are later exe- cuted by the /sbin/volreconfig command to perform the actual conversion of disk partitions to LSM volumes. If the disk partition contains a mounted file system or is otherwise open or in use, the volreconfig command will reboot the system to com- plete the encapsulation process. If you cannot reboot the system at the time you encapsulate the disk partition, either defer running the volreconfig command until you can reboot the system, or unmount or close the disk partition, then run the volreconfig command. See the Logical Storage Manager manual for more details. ATTRIBUTES
Specifies the size of the LSM private region in bytes, for example, privlen=1024. Specifies the number of log copies and copies of the configuration database, for example, nconfig=0. EXAMPLES
To encapsulate all disk partitions on the boot disk called dsk0 to LSM volumes, enter: # volencap dsk0 # volreconfig The volreconfig command will request confirmation prior to rebooting the system. The LSM command scripts created by the volencap command will execute as the system reboots. To encapsulate only the root file system (dsk0a) and swap (dsk0b) partitions on the boot disk, enter: # volencap dsk0a dsk0b # volreconfig The volreconfig command will request confirmation prior to rebooting the system. The LSM command scripts created by the volencap command will execute as the system reboots. To convert all disk partitions in the AdvFS domain called dom1 to LSM volumes, enter: # volencap dom1 # volreconfig The volreconfig command will determine if the domain is active, and if so, request confirmation prior to rebooting the system. The LSM command scripts created by the volencap command will execute as the system reboots. If the AdvFS filesets in domain dom1 are not mounted, then /sbin/volreconfig can be executed on the command line. To encapsulate the specific partition dsk1g to an LSM volume, enter: # volencap dsk1g # volreconfig The volreconfig command will determine if the partition is open, and if so, request confirmation prior to rebooting the system. The LSM command scripts created by the volencap command will be executed as the system reboots. SEE ALSO
volintro(8) volencap(8)
All times are GMT -4. The time now is 03:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy