hdds physically Post: 302071577

4 More Discussions You Might Find Interesting

1. Solaris

How to check if rsc is physically exist

I have a bunch of servers that cant connect via rsc, but supposingly they can connect... Any chance I can check if the rsc card is physically exist in the server by some command? Some of the machines are in overseas, and I won't go datacenter to check anyways... Many Thanks!

2. Solaris

Physically identify hard disk.

Hi, I have a failed hard disk in my Sun Fire V240. Unfortunately it does not show up in 'cfgadm -al' or in the format command so I cannot unconfigure it and illuminate the blue light on the front to identify it. Is there any way of iluminating the blue lights on the other disks so I can at...

3. Solaris

SPARC T4-1/Solaris 11/Add 2 new HDDs in RAID 0 configuration

Hi, Couple of sentences for background: I'm a software developer, whose task was to create a server software for our customer. Software is ready for deployment and customer has a new T4-1 SPARC, but somehow it also became my task also to setup the server. I have managed to get the server is up...

4. AIX

IBM AIX 5.2 cloning Hdds

I have an old IBM Power 5 9111-520 that has data on it but the system is failing. I need to move it to a more reliable server. The current system has two drives and no raid. I would like to setup my "newer" system with raid and two partitions then clone my setup over. What is the best way to do...

LEARN ABOUT PHP

cmdk

cmdk(7D)							      Devices								  cmdk(7D)

NAME

       cmdk - common disk driver

SYNOPSIS

       cmdk@target, lun : [ partition | slice ]

DESCRIPTION

       The  cmdk  device  driver  is  a  common interface to various disk devices. The driver supports magnetic fixed disks and magnetic removable
       disks.

       The block-files access the disk using the system's normal buffering mechanism and are read and written  without	regard	to  physical  disk
       records. There is also a "raw" interface that provides for direct transmission between the disk and the user's read or write buffer. A sin-
       gle read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are transmit-
       ted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk.

       I/O  requests  to the magnetic disk must have an offset and transfer length that is a multiple of 512 bytes or the driver returns an EINVAL
       error.

       Slice 0 is normally used for the root file system on a disk, slice 1 as a paging area (for example, swap), and slice 2 for backing  up  the
       entire fdisk partition for Solaris software. Other slices may be used for usr file systems or system reserved area.

       Fdisk partition 0 is to access the entire disk and is generally used by the fdisk(1M) program.

FILES

       /dev/dsk/cndn[s|p]n     block device (IDE)

       /dev/rdsk/cndn[s|p]n    raw device (IDE)

			       where:

			       cn	controller n

			       dn	lun n (0-7)

			       sn	UNIX system slice n (0-15)

			       pn	fdisk partition(0)

       /kernel/drv/cmdk        32-bit kernel module.

       /kernel/drv/amd64/cmdk  64-bit kernel module.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Architecture		     |x86			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       fdisk(1M), mount(1M), lseek(2), read(2), write(2), readdir(3C), scsi(4), vfstab(4), attributes(5), dkio(7I)

SunOS 5.10							    9 Oct 2004								  cmdk(7D)