01-14-2011
Sure...if you have a concatenation, it will just join the two disks end-to-end. When it starts writing to the partition it will start on the first device and write the data. It will continue to do this until that partition has been used up, and then it will start writing to the second device, etc. This is the most basic way of getting a large partition from two smaller ones.
Stripes on the other hand, although they also allow you to have a large partition, the primary use is to vastly improve disk performance. The stripes are a pre-determined size which can be specified by the admin when the metainit is called. So for example if the stripe is 32k, and there are three devices in the stripe then the first 32k of data written to the metadevice partition would go onto the first device, the second 32k would go onto the second device, the third 32k would go onto the third device, the fourth 32k would go onto the first device again, etc, etc.
This means that when an application reads or writes a large file, all three devices can share the load. This would (in a perfect world) make the reads and writes three times faster than just having one device. So disk performance can easily be improved by orders of magnitude by using this method. It is important, however, to consider your data and how big the stripes are, as this can make a huge difference on the end performance.
I hope this helps...
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
This is my first thread here.i confused with the concept of thread.Can anyone tell me this concept in detail.my Quation may be at primary level.
Thanx in advance for help. (1 Reply)
Discussion started by: vishwasrao
1 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I am new here ,i want to know about interrupts in detail.What r
Interrupts .how they r handeled.
Thanx in adavnce. (1 Reply)
Discussion started by: vishwasrao
1 Replies
3. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
4. Solaris
Dear ALl,
I have a RAID 5 volume which is as below
d120 r 60GB c1t2d0s5 c1t3d0s5 c1t4d0s5 c1t5d0s5
d7 r 99GB c1t2d0s0 c1t3d0s0 c1t4d0s0 c1t5d0s0
d110 r 99GB c1t2d0s4 c1t3d0s4 c1t4d0s4 c1t5d0s4
d8 r 99GB c1t2d0s1 c1t3d0s1... (2 Replies)
Discussion started by: jegaraman
2 Replies
5. Solaris
Hello All,
I have read enough of texts on Raid 01 and Raid 10 on solaris :wall: . But no-where found a way to create them using SVM. Some one pls tell me how to do or Post some link if that helps.
TIA
Curious
solarister (1 Reply)
Discussion started by: Solarister
1 Replies
6. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
8. Red Hat
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
LEARN ABOUT MINIX
partitio
PARTITION(8) System Manager's Manual PARTITION(8)
NAME
partition - make a partition table
SYNOPSIS
partition [-mf] device [type:]size[+*] ...
DESCRIPTION
Partition makes a partition table on device using the types and sizes given. It may be used in combination with repartition(8) for auto-
matic installation of Minix.
You may give up to four type:size[+*] specifications for the partitions. You may also specify holes before, between, and after the parti-
tions. A hole differs from a partition specification by not having a type.
The first hole is by default 1 sector to make space for the primary bootstrap and the partition table. The other holes are 0.
The type field is the type of the partitition in hexadecimal. The size field is the partition's size in sectors. The + or * may option-
ally be added to indicate that the partition must be expanded to contain any leftover space on the device or to mark the partition active.
Partitions are padded out to cylinder boundaries, except for the first one, it starts on track 1. Some operating systems care about this.
Minix and MS-DOS do not.
OPTIONS
-m Minix only, no need to pad partitions. This is the default for subpartition tables.
-f Force making a partition table even if the device is too small.
EXAMPLE
partition /dev/hd0 01:16384 81:40000 81:2880* 06:20000+
Partitions disk 0 into an 8 Mb DOS partition, 20 Mb Minix /usr, 1.44 Mb Minix / (active), and a DOS partition of at least 10 Mb at the end
of the disk. (06:0+ would have been ok too, it's just a sanity check.)
SEE ALSO
hd(4), part(8), repartition(8).
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
PARTITION(8)