12-01-2008
No I have not as I was not sure about the consequences !
should i try ?
10 More Discussions You Might Find Interesting
1. Solaris
I dont even know what raid level this is, but its raid 5 mirrored from the looks of it.
I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hello,
Can someone advise the proper procedure for replacing a mirrored disk in SVM. I have checked the docs and various websites but the procedure seems to vary. This is what I would do...
1. Remove the db replicas from the bad disk.
2. Detach it from the mirror
3. Clear it with... (4 Replies)
Discussion started by: Actuator
4 Replies
3. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
4. Solaris
Hi Gurus, I've got an issue here:
(1) Hardware: Sun NetraT1, (2) OS: Solaris 10, (3) SVM
metastat shows /var having 12 GB. df shows /var having 4 GB. Real space for /var is about 4 GB since I can't move a big file to it. How is 8 GB space missing? Does /var/run swap need to account? Can I... (5 Replies)
Discussion started by: aixlover
5 Replies
5. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
6. Solaris
The following is the summarry:-
1) Four disks in server ie (c1t0d0. c1t1d0, c1t2d0, c1t3d0). c1t2d0 is the disk to be replaced.
c1t0d0 and c1t2d0 are mirrors.
c1t1d0 and c1t3d0 are mirrors.
Metadb to be deleted is in c1t2d0s7
a) Mirror d35 has 2 submirrors d38 and d39
d38 is a stripe... (0 Replies)
Discussion started by: aji1729
0 Replies
7. Solaris
I tried doing rootdisk mirroring in my local host , i added a new Ide disk in my system
and copied the prtvtoc from root disk to the newly added disk, and then when i tried to add database replicas on both the disks, it was added for boot disk but for the newly added disk i gave the error, which... (6 Replies)
Discussion started by: Laxxi
6 Replies
8. UNIX for Advanced & Expert Users
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
9. Solaris
Hi All
BAsed on the below I would like to verifu two things
(1) The udnerlying mirroris for '/mnt' na dit onlcy contaisne 1 sub-mirror, with one sliceon is one disk and hence, data loss on the mount point (the mount point, '/mnt' is backed up)
(2) the Procedure for renewal
# df -kh /mnt... (2 Replies)
Discussion started by: stevie_velvet
2 Replies
10. Solaris
Hi
Please can you help me on replacing or removing a faulty disk drive on a SUN NETRA X4250server with 4 internal drives only.
the format comand show me the following:
format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <drive type unknown>
... (9 Replies)
Discussion started by: fretagi
9 Replies
LEARN ABOUT REDHAT
bio_pop
BIO_push(3) OpenSSL BIO_push(3)
NAME
BIO_push, BIO_pop - add and remove BIOs from a chain.
SYNOPSIS
#include <openssl/bio.h>
BIO * BIO_push(BIO *b,BIO *append);
BIO * BIO_pop(BIO *b);
DESCRIPTION
The BIO_push() function appends the BIO append to b, it returns b.
BIO_pop() removes the BIO b from a chain and returns the next BIO in the chain, or NULL if there is no next BIO. The removed BIO then
becomes a single BIO with no association with the original chain, it can thus be freed or attached to a different chain.
NOTES
The names of these functions are perhaps a little misleading. BIO_push() joins two BIO chains whereas BIO_pop() deletes a single BIO from a
chain, the deleted BIO does not need to be at the end of a chain.
The process of calling BIO_push() and BIO_pop() on a BIO may have additional consequences (a control call is made to the affected BIOs) any
effects will be noted in the descriptions of individual BIOs.
EXAMPLES
For these examples suppose md1 and md2 are digest BIOs, b64 is a base64 BIO and f is a file BIO.
If the call:
BIO_push(b64, f);
is made then the new chain will be b64-chain. After making the calls
BIO_push(md2, b64);
BIO_push(md1, md2);
the new chain is md1-md2-b64-f. Data written to md1 will be digested by md1 and md2, base64 encoded and written to f.
It should be noted that reading causes data to pass in the reverse direction, that is data is read from f, base64 decoded and digested by
md1 and md2. If the call:
BIO_pop(md2);
The call will return b64 and the new chain will be md1-b64-f data can be written to md1 as before.
RETURN VALUES
BIO_push() returns the end of the chain, b.
BIO_pop() returns the next BIO in the chain, or NULL if there is no next BIO.
SEE ALSO
TBA
0.9.7a 2000-09-14 BIO_push(3)