Solaris 10 Volume Manager - adding slice to metadb
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
I am missing the following flags.
p - replica's location was patched in kernel
l - locator for this replica was read successfully
o - replica active prior to last mddb configuration change
q1) Can anyone elaborate the meaning of 'p' and 'l' especially ?
I'm running sun volume manager on solaris 9. I have two hotspares and
are currently on standby. Both are not being utilized.
Can I newfs both of them? Do I need to deleted the hostpares first,
then newfs?
hsp002: 2 hot spares
Device Status Length Reloc
... (3 Replies)
Hello,
I am trying to do mirror in solaris 9. I have total 0-7 disks
4 5 6 7
0 1 2 3
Drive 0 and Drive 4 = Boot Drives
Need to Mirror following drives.
Drive 1 and Drive 5 = Need to mirror
Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5.
Then i... (3 Replies)
Hi all,
I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume.
Please find a sutable solutions.
Thanks and Regards
B. Nageswar... (0 Replies)
Hello friends,
I need to test some of the solaris 10 concepts and veritas volume manager.i want to know ,where i get the testing labs or E-labs(online) for this practice.i ready to pay for this labs.pls kindly help me to get the details or website names...Thanks in Advance
-Jay (6 Replies)
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest (4 Replies)
Hello All,
I have small doubt. It's related to SVM in solaris 10. I have created raid 0 (striping) using 3 slices of 500 MB size (default interlace value as 32KB)
d2: Concat/Stripe ---- Interlace value is 32 KB
Size: 2923830 blocks (1.4 GB)
Stripe 0: (interlace: 64 blocks)
Device Start... (1 Reply)
Hi Friends,
I have to migrate my raid-1 volume to raid -5 online.
Can anyone please help me, If possible then send me the step by step commands for online migration.
Thanks in advance. (2 Replies)
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Hello Admins..
I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation.
There is an eample for concatenation:
# metainit d25 1 1 c0t1d0s2
d25: Concat/Stripe is setup
the... (5 Replies)
Discussion started by: snchaudhari2
5 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)