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

 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

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

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

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

  

raidtab



DESCRIPTION

       /etc/raidtab  is  the  default  configuration file for the
       raid tools (raidstart and company). It  defines  how  RAID
       devices are configured on a system.


FORMAT

       /etc/raidtab has multiple sections, one for each md device
       which is being configured. Each section  begins  with  the
       raiddev keyword.  The order of items in the file is impor­
       tant. Later raiddev entries can use  earlier  ones  (which
       allows  RAID-10,  for example), and the parsing code isn't
       overly bright, so be sure to follow the ordering  in  this
       man page for best results.

       Here's a sample md configuration file:

       #
       # sample raiddev configuration file
       # 'old' RAID0 array created with mdtools.
       #
       raiddev /dev/md0
           raid-level              0
           nr-raid-disks           2
           persistent-superblock   0
           chunk-size              8

           device                  /dev/hda1
           raid-disk               0
           device                  /dev/hdb1
           raid-disk               1

       raiddev /dev/md1
           raid-level              5
           nr-raid-disks           3
           nr-spare-disks          1
           persistent-superblock   1
           parity-algorithm        left-symmetric

           device                  /dev/sda1
           raid-disk               0
           device                  /dev/sdb1
           raid-disk               1
           device                  /dev/sdc1
           raid-disk               2
           device                  /dev/sdd1
           spare-disk              0

       Here  is  more  information on the directives which are in
       raid configuration files; the options are listen  in  this
       file  in  the  same order they should appear in the actual
       configuration file.

       nr-spare-disks count
              Number  of spare devices in the array; there should
              be count spare-disk  entries  later  in  the  file.
              Spare  disks may only be used with RAID4 and RAID5,
              and allow the kernel  to  automatically  build  new
              RAID  disks  as  needed.  It  is  also  possible to
              add/remove  spares  runtime  via   raidhotadd/raid­
              hotremove,   care   has   to   be  taken  that  the
              /etc/raidtab  configuration  exactly  follows   the
              actual   configuration   of   the  array.  (raidho­
              tadd/raidhotremove does not change  the  configura­
              tion file)

       persistent-superblock 0/1
              newly  created  RAID arrays should use a persistent
              superblock. A persistent superblock is a small disk
              area allocated at the end of each RAID device, this
              helps the kernel to safely detect RAID devices even
              if  disks have been moved between SCSI controllers.
              It can be used for RAID0/LINEAR arrays too, to pro­
              tect  against  accidental  disk mixups. (the kernel
              will either correctly reorder disks, or will refuse
              to  start  up an array if something has happened to
              any member disk. Of course for the 'fail-safe' RAID
              variants  (RAID1/RAID5) spares are activated if any
              disk fails.)

              Every   member    disk/partition/device    has    a
              superblock, which carries all information necessary
              to start up the whole array. (for autodetection  to
              work  all  the  'member'  RAID partitions should be
              marked type 0xfd via fdisk) The superblock  is  not
              visible  in  the  final  RAID  array  and cannot be
              destroyed accidentally  through  usage  of  the  md
              device  files,  all  RAID data content is available
              for filesystem use.

       parity-algorithm which
              The parity-algorithm to use with RAID5. It must  be
              one of left-asymmetric, right-asymmetric, left-sym­
              metric, or right-symmetric. left-symmetric  is  the
              one  that  offers  maximum  performance  on typical
              disks with rotating platters.

       chunk-size size
              Sets the stripe size to size kilobytes. Has to be a
              power  of  2  and has a compilation-time maximum of
              4M. (MAX_CHUNK_SIZE in the kernel  driver)  typical
              space spent on RAID5 checksum blocks)

       raid-disk index
              The  most  recently  defined  device is inserted at
              position index in the raid array.

       spare-disk index
              The most recently defined  device  is  inserted  at
              position index in the spare disk array.

       parity-disk index
              The  most  recently  defined device is moved to the
              end of the raid array, which forces it to  be  used
              for parity.

       failed-disk index
              The  most  recently  defined  device is inserted at
              position index  in  the  raid  array  as  a  failed
              device.  This  allows  you  to  create  raid  1/4/5
              devices in degraded mode - useful for installation.
              Don't use the smallest device in an array for this,
              put this after the raid-disk definitions!


NOTES

       The raidtools are derived from the md-tools and  raidtools
       packages,  which  were originally written by Marc Zyngier,
       Miguel de Icaza, Gadi Oxman, Bradley Ward Allen, and  Ingo
       Molnar.


SEE ALSO

       raidstart(8), raid0run(8), mkraid(8), raidstop(8)

                                                       raidtab(5)
  




Login
Nickname

Password

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?
You can help in many different ways.


Friends



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.04 Seconds