Hello!
When I use "sar -d" I get information about disk activities like:
sd0 ...
sd0,a ...
sd0,b ...
.....
sd22 ...
sd22,a ...
.....
How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
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)
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)
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)
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)
I installed solaris 9u8 and flar image and put on my jumpstart server which is running 10u3. Then I do jumpstart with new image with same hardware. Jumpstart acts like it installs, configures, and looks generally good. However, During the boot process, it reports the following errors.
The / file... (4 Replies)
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)
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)
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
LEARN ABOUT LINUX
datadm
datadm(1M)datadm(1M)NAME
datadm - maintain DAT static registry file
SYNOPSIS
/usr/bin/datadm [-v] [-u] [-a service_provider.conf] [-r service_provider.conf]
The datadm utility maintains the DAT static registry file, dat.conf(4).
This administrative configuration program allows uDAPL service providers to add and remove themselves to the dat.conf file.
You can add or remove interface adapters that a service provider supports from a system after its installation. You can use datadm to
update the dat.conf file to reflect the current state of the system. A new set of interface adapters for all the service providers cur-
rently installed is regenerated.
The following options are supported:
-a service_provider.conf
Enumerate each device entry in the service_provider.conf(4) file into a list of interface adapters, that is, interfaces to external
network that are available to uDAPL consumers.
-r service_provider.conf
Remove the list of interface adapters that corresponds to the device entry in the service_provider.conf(4) file.
-u
Update the dat.conf to reflect the current state of the system with an up to date set of interface adapters for the service providers
that are currently listed in the DAT static registry.
-v
Display the DAT static registry file, dat.conf.
Example 1: Enumerating a Device Entry
The following example enumerates a device entry in the service_provider.conf(4) file into interface adapters in the dat.conf(4) file.
Assume that SUNW has a service provider library that supports the device tavor. It has a service_provider.conf(4) file installed in the
directory /usr/share/dat/SUNWudaplt.conf with a single entry as follows:
driver_name=tavor u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
tavor is an Infiniband Host Channel Adapter with two ports. Both IB ports exist in a single IB partition, 0x8001. If an IP interface is
plumbed to each port, there are two IPoIB device instances, ibd0 and ibd1:
# ls -l /dev/ibd*
/dev/ibd0 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8001,ipib:ibd0
/dev/ibd1 -> /devices/pci@1/pci15b3,5a44@0/ibport@2,8001,ipib:ibd1
Running the command, datadm -a /usr/share/dat/SUNWudaplt.conf appends two new entries (if they do not already exists]) in the
/etc/dat/dat.conffile:
ibd0 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
Example 2: Updating the dat.conf to Reflect the Current State of the System
A new IB partition, 0x8002 is added to the above example covering port 1 of the Host Channel Adapter. If a new IP interface is plumbed to
port 1/partition 0x8002, there is a third IPoIB device instance: ibd2.
# ls -l /dev/ibd*
/dev/ibd0 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8001,ipib:ibd0
/dev/ibd1 -> /devices/pci@1/pci15b3,5a44@0/ibport@2,8001,ipib:ibd1
/dev/ibd2 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8002,ipib:ibd2
Running datadm -u command, updates the /etc/dat/dat.conf file with a new entry added reflecting the current state of the system.
datadm -v shows that there are now three entries in the /etc/dat/dat.conf file:
ibd0 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
ibd2 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
"driver_name=tavor"
/etc/dat/dat.conf DAT static registry file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWudaplu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
pkgadd(1M), pkgrm(1M), libdat(3LIB), dat.conf(4), service_provider.conf(4). attributes(5)
18 Jun 2004 datadm(1M)