Sponsored Content
Operating Systems Solaris Sun StorageTek Common Array Manager 6.0 works very slowly Post 302363849 by Sapfeer on Wednesday 21st of October 2009 12:28:22 PM
Old 10-21-2009
Thanks for your answer. I have a PC workstations where CAM runs and it connects to array through network. I will try to reinstall CAM tomorrow...
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Configure large volume on Sun StorageTek 2540 array

Hi, We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies

2. Solaris

Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000

Hello, Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array? I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5). The T2000... (15 Replies)
Discussion started by: DundeeDancer
15 Replies

3. Filesystems, Disks and Memory

Backup Sun StorageTek Common Array Manager's configuration

In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10. Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies

4. Filesystems, Disks and Memory

SAN questions about Sun StorageTek array

Hi, I have a question about Sun StorageTek Common Array Manager (CAM): What is the concept of 'host'? Is it the hostname of the server that has access to the managed array? If so, can I use its IP instead of its hostname? I've found a 'host' under CAM called XYZ (See below). In our... (7 Replies)
Discussion started by: aixlover
7 Replies

5. Solaris

Common Array Manager

Hi! May be Solaris forum is not the best choice for asking such question, but I really need help with SunStorage FC array. AFAIK this array can be configured only with CAM software by Sun, but sadly all previously free Metalink downloads are now accessible only as a part of paid support (and I... (0 Replies)
Discussion started by: Gleb Erty
0 Replies
PASS(4) 						   BSD Kernel Interfaces Manual 						   PASS(4)

NAME
pass -- CAM application passthrough driver SYNOPSIS
device pass DESCRIPTION
The pass driver provides a way for userland applications to issue CAM CCBs to the kernel. Since the pass driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this driver. If used improperly, this driver can allow userland applications to crash a machine or cause data loss. The pass driver attaches to every SCSI device found in the system. Since it attaches to every device, it provides a generic means of access- ing SCSI devices, and allows the user to access devices which have no "standard" peripheral driver associated with them. KERNEL CONFIGURATION
It is only necessary to configure one pass device in the kernel; pass devices are automatically allocated as SCSI devices are found. IOCTLS
CAMIOCOMMAND This ioctl takes most kinds of CAM CCBs and passes them through to the CAM transport layer for action. Note that some CCB types are not allowed through the passthrough device, and must be sent through the xpt(4) device instead. Some examples of xpt-only CCBs are XPT_SCAN_BUS, XPT_DEV_MATCH, XPT_RESET_BUS, XPT_SCAN_LUN, XPT_ENG_INQ, and XPT_ENG_EXEC. These CCB types have various attributes that make it illogical or impossible to service them through the passthrough interface. CAMGETPASSTHRU This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question. Although this ioctl is available through the pass driver, it is of limited use, since the caller must already know that the device in question is a passthrough device if they are issuing this ioctl. It is probably more useful to issue this ioctl through the xpt(4) device. FILES
/dev/passn Character device nodes for the pass driver. There should be one of these for each device accessed through the CAM subsystem. DIAGNOSTICS
None. SEE ALSO
cam(3), cam_cdbparse(3), cam(4), xpt(4), camcontrol(8) HISTORY
The CAM passthrough driver first appeared in FreeBSD 3.0. AUTHORS
Kenneth Merry <ken@FreeBSD.org> BUGS
It might be nice to have a way to asynchronously send CCBs through the passthrough driver. This would probably require some sort of read/write interface or an asynchronous ioctl interface. BSD
October 10, 1998 BSD
All times are GMT -4. The time now is 09:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy