Q1: can anyone tell me how cfgadm keeps track of the device even if the device is disconnected ,
when we disconnect a device using cfgadm
cfgadm -ys disconnect <ap_id>
then the device disappears from the lshal o/p. HAL uses libdevinfo for the device list. if the device is not there in the... (2 Replies)
Dear All,
I need a small script which will read from a txt file the first and and second and the last clumn of the file and determine how many are having +000 ,+024,+048 error codes.
Please help me as soon as possible.
Rgrds,
A.Ali (2 Replies)
Solaris 10, Solaris Cluser 3.2, two node cluster, all software installed succefully, all nodes join to the cluster
And on snod2 didn't recognize disks as a did devices and I can't make a quorum device.
snod1#/usr/cluster/bin/cluster status
=== Cluster Nodes ===
--- Node Status ---
Node... (2 Replies)
Is there a trick to mounting swap in n a lvm? I can't get it to work.
# swapon -va
swapon on /dev/mapper/VG-lv_swap
swapon: /dev/mapper/VG-lv_swap: found swap signature: version 1, page-size 4, same byte order
swapon: /dev/mapper/VG-lv_swap: pagesize=4096, swapsize=4294967296,... (1 Reply)
Below is the error being repeated on my Solaris 9 Sun-Fire-V890 machine.
SAN team confirmed as everything is fine from their end. I did google and found that some people say its a known Oracle bug when you have Oracle 10G installed on your system but I kind of disagree with them. Please see below... (2 Replies)
I am getting error in a shell script having a simple date command.
Error is " write to 1 failed ".
We saw that /tmp folder was 100% full. When we cleared some space in /tmp folder then script worked fine. Why does date command(or any other command) require space in /tmp folder? Which settings... (6 Replies)
Hello,
I want to install GCC gcc-4.8.1-2.src.rpm for AIX 6.1
when I lance my command rpm -i gcc-4.8.1-2.src.rpm
I have this error
unpacking of archive failed on file gcc-4.8.1.tar.bz2: cpio: copy failed - No space left on device
I checked the free space and I am surpise becouse I have... (7 Replies)
We have an IBM Power 710. It has a USB port on the front. I have done some searching and see that there is information out there on how to create a JFS2 file system on USB drives. A few have commented that they would not recommend it, if the server is important, may crash the server... Just... (0 Replies)
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Running a installation on Solaris 11 and getting error write to 1 failed
If anyone can advise ?
ORIGINAL_PATH="${PATH}"
# prepend /usr/xpg4/bin to PATH as needed
temporaryPath=`expr "${PATH}:" : '\(/usr/xpg4/bin:\)'`
if
then
PATH="/usr/xpg4/bin:${PATH}"
seem to have... (6 Replies)
Discussion started by: Mpumi
6 Replies
LEARN ABOUT SUNOS
sf
sf(7D) Devices sf(7D)NAME
sf - SOC+ FC-AL FCP Driver
SYNOPSIS
sf@port,0
DESCRIPTION
The sf driver is a SCSA compliant nexus driver which supports the Fibre Channel Protocol for SCSI on Private Fibre Channel Arbitrated
loops. An SBus card called the SOC+ card (see socal(7D)) connects the Fibre Channel loop to the host system.
The sf driver interfaces with the SOC+ device driver, socal(7D), the SCSI disk target driver, ssd(7D), and the SCSI-3 Enclosure Services
driver, ses(7D). It only supports SCSI devices of type disk and ses.
The sf driver supports the standard functions provided by the SCSA interface. The driver supports auto request sense and tagged queueing
by default.
The driver requires that all devices have unique hard addresses defined by switch settings in hardware. Devices with conflicting hard
addresses will not be accessible.
FILES
/platform/architecture/kernel/drv/sf ELF kernel module
/platform/architecture/kernel/drv/sf.consf driver configuration file
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO luxadm(1M), prtconf(1M), driver.conf(4), socal(7D), ssd(7D)
Writing Device Drivers
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
ANSI X3.269-1996, Fibre Channel Protocol for SCSI (FCP)
ANSI X3.270-1996, SCSI-3 Architecture Model (SAM)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
In addition to being logged, the messages below may display on the system console.
The first set of messages indicate that the attachment was unsuccessful, and will only display while the sf driver is initially attempting
to attach. Each message is preceded by sf%d , where %d is the instance number of the sf device.
Failed to alloc soft state
Driver was unable to allocate space for the internal state structure. Driver did not attach to device, SCSI devices will be inaccessi-
ble.
Bad soft state
Driver requested an invalid internal state structure. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to obtain transport handle
Driver was unable to obtain a transport handle to communicate with the socal driver. Driver did not attach to device, SCSI devices will
be inaccessible
Failed to allocate command/response pool
Driver was unable to allocate space for commands and responses. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate kmem cache
Driver was unable to allocate space for the packet cache. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate dma handle for
Driver was unable to allocate a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to allocate lilp map
Driver was unable to allocate space for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to bind dma handle for
Driver was unable to bind a dma handle for the loop map. Driver did not attach to device, SCSI devices will be inaccessible.
Failed to attach
Driver was unable to attach for some reason that may be printed. Driver did not attach to device, SCSI devices will be inaccessible.
The next set of messages may display at any time. The full device pathname, followed by the shorter form described above, will precede
the message.
Invalid lilp map
The driver did not obtain a valid lilp map from the socal driver. SCSI device will be inaccessible.
Target t, AL-PA x and hard
The device with a switch setting t has an AL-PA x which does not match its hard address y. The device will not be accessible.
Duplicate switch settings
The driver detected devices with the same switch setting. All such devices will be inaccessible.
WWN changed on target t
The World Wide Name (WWN) has changed on the device with switch setting t.
Target t, unknown device type
The driver does not know the device type reported by the device with switch setting t.
SunOS 5.10 27 Mar 1997 sf(7D)