Sponsored Content
Full Discussion: sar + sdXY,Z + /dev/dsk
Top Forums UNIX for Dummies Questions & Answers sar + sdXY,Z + /dev/dsk Post 39936 by Colf on Friday 5th of September 2003 12:56:34 PM
Old 09-05-2003
O, really sorry, of course.
Sun Solaris 8
all disks are SCSI, in external multipack (except system's)
 

10 More Discussions You Might Find Interesting

1. Solaris

mount: /dev/dsk/c0t6d0s0 no such device

I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one. This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies

2. Solaris

pls help - /dev/dsk 100% full

I use the following command dk -k and get the following output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 1587078 56546 1482920 4% / /dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr /proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies

3. Solaris

anyone can tell me what is /dev/dsk/c3t600A0B80002FA5F50000000000000000d0s0?

Hi all, I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below: bash-3.00# cd /dev/dsk bash-3.00# ls c3* c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4 c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies

4. Solaris

FSCK root file system (/dev/vx/dsk/bootdg/rootvol)

Hi, I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies

5. Solaris

How do I determine the hard drives in /dev/dsk in OpenSolaris?

I have a Solaris machine running OpenSolaris v5.11. It came with a hard drive. It's called /dev/dsk/c4d0s0. I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk. How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies

6. UNIX for Dummies Questions & Answers

Meaning of mount /dev/dsk/c... /mnt

Hi May I know the meaning of the following command mount /dev/dsk/c1t0d0s3 /mnt Will I be able to use my tape drive after that? Thanks (3 Replies)
Discussion started by: rahmantanko
3 Replies

7. Solaris

how to make less capacity /dev/dsk/c1t0d0s5

how to make less capacity on /dev/dsk/c1t0d0s5 Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% / /dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr /dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies

8. Solaris

Size missing on /dev/dsk/c0t0d0s3

Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb. Where is my space. Where was lost? Could you please I need your opinions? {root}/space>du -s -h * 308K alaerrm-jprof 1K argerela 20G baerckup_in 1.8G cererm 28M ecerlipselink ... (8 Replies)
Discussion started by: getrue
8 Replies

9. Solaris

Canīt open /dev/dsk/c1t0d0s0 Clone/mirror

Hello friends, I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start. The original mounting this, mirror in Raid 0: c1t0d0s0 (master)... (10 Replies)
Discussion started by: grymorum
10 Replies

10. Solaris

Lun remove, stuck in /dev/dsk and /dev/rdsk

So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following: devfsadm -Cv powermt -q luxadm -e offline <drive path> luxadm probe All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
SCSI(7) 						 Miscellaneous Information Manual						   SCSI(7)

NAME
SCSI, RAID - Small Computer System Interface SYNOPSIS
dsk#, tape#_d#, cdrom# DESCRIPTION
The operating system interfaces to disk and tape devices through the Small Computer System Interface (SCSI). SCSI support is limited to the Compaq-supplied storage devices and certain third-party devices. To determine which named devices are supported in the default system, refer to the file /etc/ddr.dbase. For example, the following devices are listed therein: Winchester disks: RZ24L, RZ25, RZ25L, RZ25M, RZ28M, RZ29B, RZ55, RZ56, RZ58, RZ73, RZ74, RX23, RX26, RX33, IOMEGA ZIP, RAID (Redundant Arrays of Independent Disks) SCSI controllers: HSZ10, HSZ40, HSZ80 Magnetic tapes: TZ30, TZK11, TLZ06, TKZ09, TKZ60, DLT8000, SDT-10000 Media Changers: TL800, ESL9000 Optical disks: RRD42, RRD43, RRD44 Vendors can add their own devices to ddr.dbase. Refer to the Software Product Description (SPD) for a given release of the operating system for more information on processor-specific device support. Under the operating system, a SCSI device is referred to by a device identifier that is assigned by the operating system. This name has no relationship to the descriptive name of the device, although in previous releases of the operating system disks such as the RZ74 mapped to a system-assigned rz# logical name (where # was the instance number of that disk. Current logical names for SCSI disks and tapes take the forms specified in the rz(8) and tz(7) reference pages, such as dsk? and tape?. Refer to the dsfmgr(8) reference page for the naming conventions for disks, tapes and other devices, such as CD-ROM readers. Refer to the hwmgr(8) reference page for information on determining device names and other device data. SCSI Device Limits The number of possible target device IDs is determined by the controller type and method of connection, such as a multibus connection using fibre channel. Refer to the emx(7) reference page for an example of device addressing. Device Special Files The dsfmgr command creates device special files for all the devices that are attached to SCSI controllers. This event occurs automatically on system startup, and no administrative intervention is required unless an event requires that a device be renamed or its I/O be reas- signed. In such cases, you can use dsfmgr and hwmgr to manage SCSI devices and their associated device special files without the need to calculate values from their Bus, Target ID, and LUN data. RESTRICTIONS
The SCSI device driver is not warrantied to operate with optical disks other than the devices listed in /etc/ddr.dbase/. The SCSI driver attempts to support, on a best-effort basis, disks and magnetic tapes supplied by other vendors. The following notes apply to the driver's handling of disks from other vendors: These disks are identified using the following command: # hwmgr -get attribute -a name This command will return the device name SCSI-WWID (World-Wide Identifier) for all devices on the system, which includes the model name of the device. You can filter the output by specifying categories of devices. Disks are assigned a default partition table. The default table can be modified by editing the ccmn_rzxx_sizes[8] entry in the /usr/sys/data/cam_data.c file. The disklabel command can also be used to modify the partition table on an RZxx disk. RELATED INFORMATION
atapi_ide(7), dsfmgr(8), emx(7), hwmgr(8), rz(7), tz(7), disklabel(8), ddr.dbase(4) delim off SCSI(7)
All times are GMT -4. The time now is 09:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy