Sponsored Content
Full Discussion: Software RAID on Linux
Operating Systems Linux Software RAID on Linux Post 302283085 by otheus on Monday 2nd of February 2009 01:59:34 PM
Old 02-02-2009
That's a good point about Sata throughput and drive throughput. What you must consider, however, is that RAID tries to write 5 blocks to five different drives right after another. Each contoller gets the data, sends a write request, waits for it to finish, sends the next, etc. Each drive gets the SATA command, positions the head to the correct place, then writes the data. When done serially, this process can reduce your throughput from 90 MB/s to 18 MB/s (90/5).

Since the PCI bus is much faster than the SATA bus, the OS can send the data to multiple controllers by the time the first disk is about to write. Thus, the OS can take advantage of multiple SATA controllers. (It could be that some SATA PCI controllers have multiple busses and multiple drive controllers, which would be nice). But if you're fine with the 20 MB/s, then just a single controller is fine.

As far as partitions, leave /boot, /, and /usr on your 80 GB drive. I don't know why you need to separate /tmp from / unless you have a large need for /tmp space (which is very uncommon these days -- most programs use the current working directory for scratch space). If you have a need for /tmp, but that consists of lots of small data files, use a memory-based solution.

You almost won't need swap at all with 4+ GB. If you have one, keep it on the array, but not on the slower 80 gb drive.
 

9 More Discussions You Might Find Interesting

1. SuSE

Raid software besides Veritass

Hello Lunix people, I am looking for Raid software or solution besides Veritas. Veritas has some great software but are way too costly. Does anyone know of good raid software that but NOT Veritas. I need the funcations but not the cost. (7 Replies)
Discussion started by: xtmeisel
7 Replies

2. UNIX for Advanced & Expert Users

Software RAID ...

Hi all, I m just trying using software RAID in RHEL 4, without problem , then i wanna simulate if disk 1 is fail (thereis an bootloader), i plug off my 1st disk. My problems is the second disk cannot boot? just stuck in grub, the computer is hang. Sorry for poor concept in RAID? I use a RAID 1.... (0 Replies)
Discussion started by: blesets
0 Replies

3. HP-UX

Software RAID (0+1)

Hi! A couple of months ago a disk failed in our JBOD cabinett and I have finally got a new disk to replace it with. It was a RAID 0 so we have to create and configure the whole thing again. First we thought of RAID 1+0 but it seems you can't do this with LVM. If you read my last thread, you can... (0 Replies)
Discussion started by: hoff
0 Replies

4. Red Hat

Software RAID doubt

hi friends, I am having issues with adding a spare device to a failed array. I have created RAID 1 with 3 partitions using mdadm command. Later I added a spare with mdadm --add /dev/md0 /dev/sdb6 This works fine and when I check this with mdadm --detail command it just sits there as a spare... (7 Replies)
Discussion started by: saagar
7 Replies

5. Filesystems, Disks and Memory

Software RAID

Hello, My company has inherited a Centos based machine that has 7 hard drives and a software based raid system. Supposedly one of the drives has failed. I need to replace the hardrive. How can I about telling which hard drive needs replacing? I have looked in the logs and there clearly is a... (5 Replies)
Discussion started by: mojoman
5 Replies

6. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

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

7. Red Hat

Software RAID configuration

We have configured software based RAID5 with LVM on our RHEL5 servers. Please let us know if its good to configure software RAID on live environment servers. What can be the disadvantages of software RAID against hardware RAID (4 Replies)
Discussion started by: mitchnelson
4 Replies

8. Solaris

Software RAID on top of Hardware RAID

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

9. Solaris

Hardware to software RAID migration

We have hardware RAID configured on our T6320 server and two LDOMs are running on this server. One of our disk got failed and replaced. After replacemnt the newly installed disk not detected by RAID controlled so Oracle suggested to upgrade the REM firmware. As this is the standalone production... (0 Replies)
Discussion started by: rock123
0 Replies
raidreconf(8)						      System Manager's Manual						     raidreconf(8)

NAME
raidreconf - reconfigure RAID arrays SYNOPSIS
raidreconf -h {--help} - or - raidreconf -V {--version} - or - raidreconf -o oldraidtab -n newraidtab -m /dev/md? - or - raidreconf -i /dev/sd?? -n newraidtab -m /dev/md? - or - raidreconf -n newraidtab -m /dev/md? -e /dev/sd?? WARNING
You should back up all data BEFORE any attempt is made to reconfigure a RAID device. YOU HAVE BEEN WARNED. The author will give you no guarantee whatsoever, that this program works in any specific way at all. It may well destroy all data on any device connected directly, indirectly, or not at all, to any system this software is used on. Please use this stuff with care, if you decide to use it at all. Ok, that said, let's see how to actually use it :-) DESCRIPTION
raidreconf will read two raidtab files, an old one, and a new one. It will then re-build your old array to match the configuration for the new array, while retaining all data possible. It can also be used to import a single block-device into a RAID array (using more block devices), or export a RAID array to a single block- device. raidreconf can, of course, only retain your original data if you grow the configuration. If you shrink the configuration from say, P bytes to Q bytes, raidreconf will retain the first Q bytes of your original data, but everything from Q bytes to the end of the old array (to P bytes) will be lost. Currently raidreconf can grow and shrink RAID-0 and RAID-5 arrays, and import non-RAID devices into a new RAID-0 or RAID-5. The whole purpose of raidreconf is to be able to add disks to an existing array, or convert it to a new type (eg. RAID-0 to RAID-5) without losing data. raidreconf will move the existing data around on your array, to match the layout of the new array. OPTIONS
-h {--help} Raidreconf will print a short help message, and exit. -V {--verbose} Raidreconf will print it's version information, and exit. -o {--old} oldraidtab Specifies the path name of the old (current) raidtab. NOTE: raidreconf performs some tests to ensure that this configuration file matches the raid superblocks stored on the disk, but there may be scenarios where the two are in conflict, but aren't detected as such. Be very careful to specify this file properly. -n {--new} newraidtab Specifies the path name of the new raidtab. After raidreconf finishes, copy the newraidtab to the oldraidtab location, as raidreconf doesn't perform this (potentially dangerous) operation. -m {--mddev} /dev/md? Specifies the name of the raid array to modify. -i {--import} /dev/sd?? Specifies the name of the device to import from. -e {--export} /dev/sd?? Specifies the name of the device to export to. BUGS
Perhaps many. Well, the basic RAID-0 growth, shrink and import algorithms seem to work, but there are lots and lots of consistency checks and graceful error handling missing. The RAID-5 algorithms are simplistic, with little optimization other than that provided by the buffer layer. Conversions between non-RAID, RAID-0, and RAID-5 all *seem* to work, but there may be some bugs left yet. If an error occurs during reconfiguration, a power failure for example, restore from backup (you DID make a backup, right?), and try again. Although RAID-4 is not supported, and almost no one uses it, it would be almost trivial to add. REPORTING BUGS
Since this is highly experimental software, there are a number of known bugs already. The author would of course like to know about bugs, but at this stage in development you shouldn't waste too much of your time trying to hunt them down. They're probably known, and maybe already fixed in the author's tree. Report bugs to <bugs@oss.connex.com>. ????? AUTHOR
raidreconf was written in 1999 by Jakob Oestergaard <jakob@ostenfeld.dk> The RAID-5 routines were written by Daniel S. Cox in 2001 <dcox@connex.com> SEE ALSO
mkraid(8), raidtab(5), raidstart(8), raidhotadd(8), raidhotremove(8), raidstop(8) raidreconf(8)
All times are GMT -4. The time now is 10:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy