Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 77 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       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??


       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,  indi­
       rectly, 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  :-)


       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 configu­
       ration from say, P  bytes  to  Q  bytes,  raidreconf  will
       retain the first Q bytes of your original data, but every­
       thing 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

       -V {--verbose}
              Raidreconf will print it's version information, and

       -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  spec­
              ify 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.


       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

       The  RAID-5  algorithms  are simplistic, with little opti­
       mization 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


       raidreconf  was  written  in  1999  by  Jakob  Oestergaard

       The  RAID-5 routines were written by Daniel S. Cox in 2001


       mkraid(8), raidtab(5), raidstart(8), raidhotadd(8),  raid­
       hotremove(8), raidstop(8)




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds