05-30-2002
New Sds Slice
Hi,
I'd like to add two new disk (mirrored each other) in a machine still on line.
The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk.
who could send me exemples or tell me how to add a new mirrored slice in the mount point "/produit" without changing the inital configuration on the inital disks. (ex: changinf md.conf metattach etc etc...)
Regards.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
We are using Solstice Disk Suite on Solaris 2.7.
We want to add two striped volume with six disks.
On each disk, we take a slice and we create the stripe.
That I want to know :
Is it necessary to add two replicas on the same slice on the new disks, as made before on the others... (1 Reply)
Discussion started by: christophe
1 Replies
2. UNIX for Advanced & Expert Users
...I have a situation where I disks that I mirrored using Solstice Disksuite now need mirroring under Veritas Volume manager...would anyone know the best way to go about 'un-mirroring' and then removing SDS? I can see references in /etc/vfstab and /etc/system that I guess would need... (2 Replies)
Discussion started by: silvaman
2 Replies
3. UNIX for Advanced & Expert Users
Can any one Explain the artichture of Slice on SOLARIS PLATFORM.
OR else
where can i found artical on these topic.
akram shaik OCA
akram_tri_a@yahoo.com (2 Replies)
Discussion started by: smdakram
2 Replies
4. AIX
if the system pegs at 100%, can I reserve .2cpu to allow for logins and such? the oracle rman/other activities take up some resources on occassion ... 3.8 procs for the system and .2 reserved?
I'm not sure how to tackle this issue ... is this a good use for WLM?
any thoughts? (1 Reply)
Discussion started by: A Stewart
1 Replies
5. Solaris
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
6. Solaris
Hey guys,
This is how I originally had my drive setup... This is on a solaris 10 box
***BEFORE***
Current Disk = c0t1d0
Current partition table (original):
Total disk cylinders available: 7506 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks... (2 Replies)
Discussion started by: kingdbag
2 Replies
7. Solaris
Here's the scenario..
Server built with solaris 10 + SDS to mirror OS disk to 2nd disk.
If you pull the root disk while the system is running, would you expect :
1, The box to just stay running, ie off its mirror
2, The box would crash, reboot, try and boot of its primary, if not, the... (4 Replies)
Discussion started by: itsupplies
4 Replies
8. Linux
Hi all
I am testing backupPC as a backup solution for machines, as far as i knew, backuppc cannot combine more than storage from different slices so it have to be in one slice my question is, what is the easy way to offer a virtual logical drive expanded/expandable to backuppc, i mean i want to... (1 Reply)
Discussion started by: XP_2600
1 Replies
9. Solaris
I have an old V490 running an old version of Soalris 10 and an old version of VxVM.
The system disks are configured using metathis and metathat, the remaining disks
Because of the brain-damaged way engineering run things here, I cannot change this. I cannot upgrade nor patch the OS. I cannot... (2 Replies)
Discussion started by: Beast Of Bodmin
2 Replies
10. AIX
I'd like to add some x/linux-based servers to my current AIX-based TDS/SDS server community. Reading the Fine Install Guide (rtfig ?) I believe this may be covered by the section "Upgrade an instance of a previous version to a different computer" i.e. I'm going to install latest/greatest SDS on a... (4 Replies)
Discussion started by: maraixadm
4 Replies
CCD(4) BSD Kernel Interfaces Manual CCD(4)
NAME
ccd -- Concatenated disk driver
SYNOPSIS
pseudo-device ccd [count]
DESCRIPTION
The ccd driver provides the capability of combining one or more disks/partitions into one virtual disk.
This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con-
figuration file, and how to partition disks.
Note that the 'raw' partitions of the disks must not be combined. Each component partition should be offset at least one cylinder from the
beginning of the component disk. This avoids potential conflicts between the component disk's disklabel and the ccd's disklabel. The kernel
will only allow component partitions of type FS_CCD. But for now, it allows partition of all types since some port lacks support of an on-
disk BSD disklabel. The partition of FS_UNUSED may be rejected because device driver of component disk will refuse it.
In order to compile in support for the ccd, you must add a line similar to the following to your kernel configuration file:
pseudo-device ccd 4 # concatenated disk devices
The count argument is how many ccds memory is allocated for at boot time. In this example, no more than 4 ccds may be configured.
A ccd may be either serially concatenated or interleaved. To serially concatenate the partitions, specify the interleave factor of 0.
If a ccd is interleaved correctly, a ``striping'' effect is achieved, which can increase performance. Since the interleave factor is
expressed in units of DEV_BSIZE, one must account for sector sizes other than DEV_BSIZE in order to calculate the correct interleave. The
kernel will not allow an interleave factor less than the size of the largest component sector divided by DEV_BSIZE.
Note that best performance is achieved if all component disks have the same geometry and size. Optimum striping cannot occur with different
disk types.
Also note that the total size of concatenated disk may vary depending on the interleave factor even if the exact same components are concate-
nated. And an old on-disk disklabel may be read after interleave factor change. As a result, the disklabel may contain wrong partition
geometry and will cause an error when doing I/O near the end of concatenated disk.
There is a run-time utility that is used for configuring ccds. See ccdconfig(8) for more information.
WARNINGS
If just one (or more) of the disks in a non-mirrored ccd fails, the entire file system will be lost.
FILES
/dev/{,r}ccd* ccd device special files.
SEE ALSO
config(1), MAKEDEV(8), ccdconfig(8), fsck(8), mount(8), newfs(8)
HISTORY
The concatenated disk driver was originally written at the University of Utah.
BSD
March 5, 2004 BSD