In our environment we use SDS (Solaris Vlume Manager) for root file system.So, I am wondering why Veritas is not use for the same.
I understand that we can use veritas for root file system as well.But why its not so famous for root file system..??
Also we are using Veritas for other file systems.
Hello All. I have a question concerning VFS (Veritas File System).
I are attempting to upgrade Solaris 2.6 UFS to the VFS (Veritas File System). We use Veritas to perform all our backups. I have been unable to find any documentation on SUN's or Veritas's website. The server's are SUN 4500 and... (3 Replies)
hi
if anyone has docs (corporate internals on how to setup vcs mfor example, especially with Veritas VM, pleas let me know..i need exposure experience in this area of Enterprise Administration
thanks
jasmine (SCSA & MCSE) (2 Replies)
Hi
I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine?
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 ... (2 Replies)
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
hi every one ,
i know how to add swap space in ufs file system.
but i m facing problem in veritas file system .
i wants to know how will i create swap or add new swap space in existing swap space .
Note: disk under veritas volume manager control .
please help me to solve this issue . (5 Replies)
Hi,
Please someone tell me, what are the contents of root file sysytem? and significance of it, what are all possible ways to mount root file system? (5 Replies)
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
hi all
i have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore. (3 Replies)
Hi all
I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore.
backup was taken... (0 Replies)
Hi,
I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server.
When I do iostat -E. I see this.
sd0... (4 Replies)
Discussion started by: samnyc
4 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)