Hi Guys!!
Iam new to this thread.
I have a very urgent requirement of finding the local disk space. Iam running a php script on linux machine and need to find the local disk space on the remote machines.
I tried using df -h, which works if I specify the drive name on the remote machine.... (4 Replies)
Hello - I am trying to connect to a remote solaris box from a solaris box i have locally present with me using 'ssh login@IP' ... Its connecting fine but... when I run xclock - it says 'Can't open display'
Whereas, IF I connect to same remote solaris IP from my windows desktop locally via putty... (9 Replies)
We ordered a DVD for solaris 10 upgrade . However I realized that we have cd rom only and DVD is unreadable . Can i use this DVD , to upgrade the release from local disks. If yes , is there any specific procedure. (5 Replies)
Hi,
I am trying to move a local directory from a local disk to a nfs disk that has been shared on another file server. I am using this tar command:
tar cf - . | (cd /export/nfsdisk && tar xpf - )
It copies the data okay but the big problem is that is resets the owner:group to 'nobody'. The... (2 Replies)
I totally new to UNIX and I have a newbie question.
I have 2 servers, AIX and Solaris and I need to be on just one platform.
both serves have 2 physical drives, with the OS on one and data on the other.
can I take the data drive from the AIX server and mount it on the Solaris server?
or would... (2 Replies)
Hi,
I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name
here is what i did :
On the machine holding the internal disk
in vfstab i added the line
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Hello Team,
Our p740 systems are booting up from SAN. We would like to configure the local disk(which is not part of rootvg) as a primary dump device. I have assigned the same too. But in the errpt throwing the below error. Please help me on this.
... (1 Reply)
Dear all,
I am unable to get the desired result upon executing the below script. the problem is at `perl -le 'print scalar localtime $msecage'` ouput which gives the following result "Thu Jan 1 05:00:00 1970" instead of "Tue Nov 13 10:30:56 2012" but when I run the same command from shell... (2 Replies)
I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
LEARN ABOUT SUNOS
i2o_bs
i2o_bs(7D) Devices i2o_bs(7D)NAME
i2o_bs - Block Storage OSM for I2O
SYNOPSIS
disk@local target id#:a through u
disk@local target id#:a through u raw
DESCRIPTION
The I2O Block Storage OSM abstraction (BSA, which also is referred to as block storage class) layer is the primary interface that Solaris
operating environments use to access block storage devices. A block storage device provides random access to a permanent storage medium.
The i2o_bs device driver uses I2O Block Storage class messages to control the block device; and provides the same functionality (ioctls,
for example) that is present in the Solaris device driver like 'cmdk, dadk' on x86 for disk. The maximum size disk supported by i2o_bs is
the same as what is available on x86.
The i2o_bs is currently implemented version 1.5 of Intelligent IO specification.
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
single read or write call usually results in one I/O operation; raw I/O is therefore considerably more efficient when many bytes are
transmitted. The names of the block files are found in /dev/dsk; the names of the raw files are found in /dev/rdsk.
I2O associates each block storage device with a unique ID called a local target id that is assigned by I2O hardware. This information can
be acquired by the block storage OSM through I2O Block Storage class messages. For Block Storage OSM, nodes are created in
/devices/pci#/pci# which include the local target ID as one component of device name that the node refers to. However the /dev names and
the names in /dev/dsk and /dev/rdsk do not encode the local target id in any part of the name.
For example, you might have the following:
/devices/ /dev/dsk name
---------------------------------------------------------------
/devices/pci@0,0/pci101e,0@10,1/disk@10:a /dev/dsk/c1d0s0
I/O requests to the 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 is used 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
/dev/rdsk/cndn[s|p]n raw device
where:
cn controller n
dn instance number
sn UNIX system slice n (0-15)
pn fdisk partition(0)
/kernel/drv/i2o_bs i2o_bs driver
/kernel/drv/i2o_bs.conf Configuration file
ATTRIBUTES
See attributes(5)
for descriptions of the following attributes:
+-----------------------------+-----------------------------+
|ATTRIBUTE TYPE |ATTRIBUTE VALUE
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
SEE ALSO fdisk(1M), format(1M)mount(1M),lseek(2), read(2), write(2), readdir(3C), vfstab(4), acct.h(3HEAD), attributes(5), dkio(7I)SunOS 5.10 21 Jul 1998 i2o_bs(7D)