--- mdadm-2.6.2.orig/debian/TESTING +++ mdadm-2.6.2/debian/TESTING @@ -0,0 +1,89 @@ +Call for help testing new versions of mdadm +=========================================== + +The problem with being the mdadm maintainer is that it doesn't make any +friends but potentially quite a lot of enemies. Even though it's actually very +unlikely that a new mdadm version causes data loss (mdadm is only the remote +control into the kernel), people seem to exhibit unexpected reactions when +their MD arrays with important data don't want to start anymore. In such +a case, don't panic, don't do anything without understanding the implications, +and consider asking for help. + +That said, I would appreciate if you guys helped me test the latest mdadm +releases a bit more thoroughly. I do extensive tests myself, but as Murphy +would be able to predict, the problem only ever occur on other people's +machines, and I'd much rather fix them sooner than later. + +The easiest way to test new mdadm packages is by adding my package repository +(i386/amd64) to your sources.list file, and configuring the APT pins +appropriately: + +---8<--- +# cat <<_eof >> /etc/apt/sources.list +deb http://debian.madduck.net/repo sid main +_eof +# cat <<_eof >> /etc/apt/preferences +Package: * +Pin: release a=unstable,o=madduck +Pin-Priority: 50 + +Package: mdadm +Pin: release a=unstable,o=madduck +Pin-Priority: 600 +_eof +# apt-get update; apt-get upgrade +---8<--- + +Alternatively, you can just download the package for i386[0] or amd64[1]: + + 0. http://debian.madduck.net/repo/dists/sid/main/binary-i386/admin/ + 1. http://debian.madduck.net/repo/dists/sid/main/binary-amd64/admin/ + +If you're running etch and are willing to test, that would be great! I've +prepared backports, which you can use like so: + +---8<--- +# cat <<_eof >> /etc/apt/sources.list +deb http://debian.madduck.net/repo etch-backports main +## unless you have backports already enabled: +deb http://www.backports.org/debian etch-backports main +_eof +# cat <<_eof >> /etc/apt/preferences +Package: * +Pin: release a=etch-backports,o=madduck +Pin-Priority: 50 + +Package: mdadm +Pin: release a=etch-backports,o=madduck +Pin-Priority: 600 + +#Package: debconf +#Pin: release a=sarge-backports +#Pin-Priority: 600 +# +#Package: lsb-base +#Pin: release a=sarge-backports +#Pin-Priority: 600 +_eof +# apt-get update; apt-get upgrade +---8<--- + +For sarge, just replace each occurrence of etch with sarge (s/etch/sarge/g), +and add the debconf and lsb-base backports from backports.org [2]; see also +further down for direct links): + + 2. http://backports.org/dokuwiki/doku.php?id=instructions + +The mdadm backport can also be directly downloaded for i386[3] or amd64[4], +the needed debconf[5] and lsb-base[6] reside in the backports.org archive. + + 3. http://debian.madduck.net/repo/dists/etch-backports/main/binary-i386/admin/ + 4. http://debian.madduck.net/repo/dists/etch-backports/main/binary-amd64/admin/ + 5. http://backports.org/debian/pool/main/d/debconf/ + 6. http://backports.org/debian/pool/main/l/lsb/ + +Much appreciated! + + -- martin f. krafft Thu, 09 Nov 2006 16:16:21 +0100 + +$Id: TESTING 330 2007-05-09 15:15:27Z madduck $ --- mdadm-2.6.2.orig/debian/patches/99-monitor-6+10-FIX.dpatch +++ mdadm-2.6.2/debian/patches/99-monitor-6+10-FIX.dpatch @@ -0,0 +1,19 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 99-monitor-6+10-FIX.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff -urNad mdadm-2.6.2~/Monitor.c mdadm-2.6.2/Monitor.c +--- mdadm-2.6.2~/Monitor.c 2007-05-21 14:24:20.000000000 +0200 ++++ mdadm-2.6.2/Monitor.c 2007-05-21 14:24:45.000000000 +0200 +@@ -401,6 +401,8 @@ + if (mse->devnum != MAXINT && + (strcmp(mse->level, "raid1")==0 || + strcmp(mse->level, "raid5")==0 || ++ strcmp(mse->level, "raid6")==0 || ++ strcmp(mse->level, "raid10")==0 || + strcmp(mse->level, "multipath")==0) + ) { + struct state *st = malloc(sizeof *st); --- mdadm-2.6.2.orig/debian/patches/80-md.txt.dpatch +++ mdadm-2.6.2/debian/patches/80-md.txt.dpatch @@ -0,0 +1,368 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 99-md.txt.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff -urNad mdadm-2.5.2~/md.txt mdadm-2.5.2/md.txt +--- mdadm-2.5.2~/md.txt 1970-01-01 01:00:00.000000000 +0100 ++++ mdadm-2.5.2/md.txt 2006-07-06 18:28:20.213989423 +0200 +@@ -0,0 +1,357 @@ ++Tools that manage md devices can be found at ++ http://www..kernel.org/pub/linux/utils/raid/.... ++ ++ ++Boot time assembly of RAID arrays ++--------------------------------- ++ ++You can boot with your md device with the following kernel command ++lines: ++ ++for old raid arrays without persistent superblocks: ++ md=,,,,dev0,dev1,...,devn ++ ++for raid arrays with persistent superblocks ++ md=,dev0,dev1,...,devn ++or, to assemble a partitionable array: ++ md=d,dev0,dev1,...,devn ++ ++md device no. = the number of the md device ... ++ 0 means md0, ++ 1 md1, ++ 2 md2, ++ 3 md3, ++ 4 md4 ++ ++raid level = -1 linear mode ++ 0 striped mode ++ other modes are only supported with persistent super blocks ++ ++chunk size factor = (raid-0 and raid-1 only) ++ Set the chunk size as 4k << n. ++ ++fault level = totally ignored ++ ++dev0-devn: e.g. /dev/hda1,/dev/hdc1,/dev/sda1,/dev/sdb1 ++ ++A possible loadlin line (Harald Hoyer ) looks like this: ++ ++e:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro ++ ++ ++Boot time autodetection of RAID arrays ++-------------------------------------- ++ ++When md is compiled into the kernel (not as module), partitions of ++type 0xfd are scanned and automatically assembled into RAID arrays. ++This autodetection may be suppressed with the kernel parameter ++"raid=noautodetect". As of kernel 2.6.9, only drives with a type 0 ++superblock can be autodetected and run at boot time. ++ ++The kernel parameter "raid=partitionable" (or "raid=part") means ++that all auto-detected arrays are assembled as partitionable. ++ ++Boot time assembly of degraded/dirty arrays ++------------------------------------------- ++ ++If a raid5 or raid6 array is both dirty and degraded, it could have ++undetectable data corruption. This is because the fact that it is ++'dirty' means that the parity cannot be trusted, and the fact that it ++is degraded means that some datablocks are missing and cannot reliably ++be reconstructed (due to no parity). ++ ++For this reason, md will normally refuse to start such an array. This ++requires the sysadmin to take action to explicitly start the array ++desipite possible corruption. This is normally done with ++ mdadm --assemble --force .... ++ ++This option is not really available if the array has the root ++filesystem on it. In order to support this booting from such an ++array, md supports a module parameter "start_dirty_degraded" which, ++when set to 1, bypassed the checks and will allows dirty degraded ++arrays to be started. ++ ++So, to boot with a root filesystem of a dirty degraded raid[56], use ++ ++ md-mod.start_dirty_degraded=1 ++ ++ ++Superblock formats ++------------------ ++ ++The md driver can support a variety of different superblock formats. ++Currently, it supports superblock formats "0.90.0" and the "md-1" format ++introduced in the 2.5 development series. ++ ++The kernel will autodetect which format superblock is being used. ++ ++Superblock format '0' is treated differently to others for legacy ++reasons - it is the original superblock format. ++ ++ ++General Rules - apply for all superblock formats ++------------------------------------------------ ++ ++An array is 'created' by writing appropriate superblocks to all ++devices. ++ ++It is 'assembled' by associating each of these devices with an ++particular md virtual device. Once it is completely assembled, it can ++be accessed. ++ ++An array should be created by a user-space tool. This will write ++superblocks to all devices. It will usually mark the array as ++'unclean', or with some devices missing so that the kernel md driver ++can create appropriate redundancy (copying in raid1, parity ++calculation in raid4/5). ++ ++When an array is assembled, it is first initialized with the ++SET_ARRAY_INFO ioctl. This contains, in particular, a major and minor ++version number. The major version number selects which superblock ++format is to be used. The minor number might be used to tune handling ++of the format, such as suggesting where on each device to look for the ++superblock. ++ ++Then each device is added using the ADD_NEW_DISK ioctl. This ++provides, in particular, a major and minor number identifying the ++device to add. ++ ++The array is started with the RUN_ARRAY ioctl. ++ ++Once started, new devices can be added. They should have an ++appropriate superblock written to them, and then passed be in with ++ADD_NEW_DISK. ++ ++Devices that have failed or are not yet active can be detached from an ++array using HOT_REMOVE_DISK. ++ ++ ++Specific Rules that apply to format-0 super block arrays, and ++ arrays with no superblock (non-persistent). ++------------------------------------------------------------- ++ ++An array can be 'created' by describing the array (level, chunksize ++etc) in a SET_ARRAY_INFO ioctl. This must has major_version==0 and ++raid_disks != 0. ++ ++Then uninitialized devices can be added with ADD_NEW_DISK. The ++structure passed to ADD_NEW_DISK must specify the state of the device ++and it's role in the array. ++ ++Once started with RUN_ARRAY, uninitialized spares can be added with ++HOT_ADD_DISK. ++ ++ ++ ++MD devices in sysfs ++------------------- ++md devices appear in sysfs (/sys) as regular block devices, ++e.g. ++ /sys/block/md0 ++ ++Each 'md' device will contain a subdirectory called 'md' which ++contains further md-specific information about the device. ++ ++All md devices contain: ++ level ++ a text file indicating the 'raid level'. This may be a standard ++ numerical level prefixed by "RAID-" - e.g. "RAID-5", or some ++ other name such as "linear" or "multipath". ++ If no raid level has been set yet (array is still being ++ assembled), this file will be empty. ++ ++ raid_disks ++ a text file with a simple number indicating the number of devices ++ in a fully functional array. If this is not yet known, the file ++ will be empty. If an array is being resized (not currently ++ possible) this will contain the larger of the old and new sizes. ++ Some raid level (RAID1) allow this value to be set while the ++ array is active. This will reconfigure the array. Otherwise ++ it can only be set while assembling an array. ++ ++ chunk_size ++ This is the size if bytes for 'chunks' and is only relevant to ++ raid levels that involve striping (1,4,5,6,10). The address space ++ of the array is conceptually divided into chunks and consecutive ++ chunks are striped onto neighbouring devices. ++ The size should be atleast PAGE_SIZE (4k) and should be a power ++ of 2. This can only be set while assembling an array ++ ++ component_size ++ For arrays with data redundancy (i.e. not raid0, linear, faulty, ++ multipath), all components must be the same size - or at least ++ there must a size that they all provide space for. This is a key ++ part or the geometry of the array. It is measured in sectors ++ and can be read from here. Writing to this value may resize ++ the array if the personality supports it (raid1, raid5, raid6), ++ and if the component drives are large enough. ++ ++ metadata_version ++ This indicates the format that is being used to record metadata ++ about the array. It can be 0.90 (traditional format), 1.0, 1.1, ++ 1.2 (newer format in varying locations) or "none" indicating that ++ the kernel isn't managing metadata at all. ++ ++ level ++ The raid 'level' for this array. The name will often (but not ++ always) be the same as the name of the module that implements the ++ level. To be auto-loaded the module must have an alias ++ md-$LEVEL e.g. md-raid5 ++ This can be written only while the array is being assembled, not ++ after it is started. ++ ++ new_dev ++ This file can be written but not read. The value written should ++ be a block device number as major:minor. e.g. 8:0 ++ This will cause that device to be attached to the array, if it is ++ available. It will then appear at md/dev-XXX (depending on the ++ name of the device) and further configuration is then possible. ++ ++ sync_speed_min ++ sync_speed_max ++ This are similar to /proc/sys/dev/raid/speed_limit_{min,max} ++ however they only apply to the particular array. ++ If no value has been written to these, of if the word 'system' ++ is written, then the system-wide value is used. If a value, ++ in kibibytes-per-second is written, then it is used. ++ When the files are read, they show the currently active value ++ followed by "(local)" or "(system)" depending on whether it is ++ a locally set or system-wide value. ++ ++ sync_completed ++ This shows the number of sectors that have been completed of ++ whatever the current sync_action is, followed by the number of ++ sectors in total that could need to be processed. The two ++ numbers are separated by a '/' thus effectively showing one ++ value, a fraction of the process that is complete. ++ ++ sync_speed ++ This shows the current actual speed, in K/sec, of the current ++ sync_action. It is averaged over the last 30 seconds. ++ ++ ++As component devices are added to an md array, they appear in the 'md' ++directory as new directories named ++ dev-XXX ++where XXX is a name that the kernel knows for the device, e.g. hdb1. ++Each directory contains: ++ ++ block ++ a symlink to the block device in /sys/block, e.g. ++ /sys/block/md0/md/dev-hdb1/block -> ../../../../block/hdb/hdb1 ++ ++ super ++ A file containing an image of the superblock read from, or ++ written to, that device. ++ ++ state ++ A file recording the current state of the device in the array ++ which can be a comma separated list of ++ faulty - device has been kicked from active use due to ++ a detected fault ++ in_sync - device is a fully in-sync member of the array ++ spare - device is working, but not a full member. ++ This includes spares that are in the process ++ of being recoverred to ++ This list make grow in future. ++ ++ errors ++ An approximate count of read errors that have been detected on ++ this device but have not caused the device to be evicted from ++ the array (either because they were corrected or because they ++ happened while the array was read-only). When using version-1 ++ metadata, this value persists across restarts of the array. ++ ++ This value can be written while assembling an array thus ++ providing an ongoing count for arrays with metadata managed by ++ userspace. ++ ++ slot ++ This gives the role that the device has in the array. It will ++ either be 'none' if the device is not active in the array ++ (i.e. is a spare or has failed) or an integer less than the ++ 'raid_disks' number for the array indicating which possition ++ it currently fills. This can only be set while assembling an ++ array. A device for which this is set is assumed to be working. ++ ++ offset ++ This gives the location in the device (in sectors from the ++ start) where data from the array will be stored. Any part of ++ the device before this offset us not touched, unless it is ++ used for storing metadata (Formats 1.1 and 1.2). ++ ++ size ++ The amount of the device, after the offset, that can be used ++ for storage of data. This will normally be the same as the ++ component_size. This can be written while assembling an ++ array. If a value less than the current component_size is ++ written, component_size will be reduced to this value. ++ ++ ++An active md device will also contain and entry for each active device ++in the array. These are named ++ ++ rdNN ++ ++where 'NN' is the possition in the array, starting from 0. ++So for a 3 drive array there will be rd0, rd1, rd2. ++These are symbolic links to the appropriate 'dev-XXX' entry. ++Thus, for example, ++ cat /sys/block/md*/md/rd*/state ++will show 'in_sync' on every line. ++ ++ ++ ++Active md devices for levels that support data redundancy (1,4,5,6) ++also have ++ ++ sync_action ++ a text file that can be used to monitor and control the rebuild ++ process. It contains one word which can be one of: ++ resync - redundancy is being recalculated after unclean ++ shutdown or creation ++ recover - a hot spare is being built to replace a ++ failed/missing device ++ idle - nothing is happening ++ check - A full check of redundancy was requested and is ++ happening. This reads all block and checks ++ them. A repair may also happen for some raid ++ levels. ++ repair - A full check and repair is happening. This is ++ similar to 'resync', but was requested by the ++ user, and the write-intent bitmap is NOT used to ++ optimise the process. ++ ++ This file is writable, and each of the strings that could be ++ read are meaningful for writing. ++ ++ 'idle' will stop an active resync/recovery etc. There is no ++ guarantee that another resync/recovery may not be automatically ++ started again, though some event will be needed to trigger ++ this. ++ 'resync' or 'recovery' can be used to restart the ++ corresponding operation if it was stopped with 'idle'. ++ 'check' and 'repair' will start the appropriate process ++ providing the current state is 'idle'. ++ ++ mismatch_count ++ When performing 'check' and 'repair', and possibly when ++ performing 'resync', md will count the number of errors that are ++ found. The count in 'mismatch_cnt' is the number of sectors ++ that were re-written, or (for 'check') would have been ++ re-written. As most raid levels work in units of pages rather ++ than sectors, this my be larger than the number of actual errors ++ by a factor of the number of sectors in a page. ++ ++Each active md device may also have attributes specific to the ++personality module that manages it. ++These are specific to the implementation of the module and could ++change substantially if the implementation changes. ++ ++These currently include ++ ++ stripe_cache_size (currently raid5 only) ++ number of entries in the stripe cache. This is writable, but ++ there are upper and lower limits (32768, 16). Default is 128. ++ strip_cache_active (currently raid5 only) ++ number of active entries in the stripe cache --- mdadm-2.6.2.orig/debian/patches/80-raid5-vs-raid10-doc.dpatch +++ mdadm-2.6.2/debian/patches/80-raid5-vs-raid10-doc.dpatch @@ -0,0 +1,188 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 99-raid5-vs-raid10-doc.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff -urNad trunk~/RAID5_versus_RAID10.txt trunk/RAID5_versus_RAID10.txt +--- trunk~/RAID5_versus_RAID10.txt 1970-01-01 01:00:00.000000000 +0100 ++++ trunk/RAID5_versus_RAID10.txt 2006-07-24 23:18:32.250326974 +0100 +@@ -0,0 +1,177 @@ ++# from http://www.miracleas.com/BAARF/RAID5_versus_RAID10.txt ++# also see http://www.miracleas.com/BAARF/BAARF2.html ++# ++# Note: I, the Debian maintainer, do not agree with some of the arguments, ++# especially not with the total condemning of RAID5. Anyone who talks about ++# data loss and blames the RAID system should spend time reading up on Backups ++# instead of trying to evangelise, but that's only my opinion. RAID5 has its ++# merits and its shortcomings, just like any other method. However, the author ++# of this argument puts forth a good case and thus I am including the ++# document. Remember that you're the only one that can decide which RAID level ++# to use. ++# ++ ++RAID5 versus RAID10 (or even RAID3 or RAID4) ++ ++First let's get on the same page so we're all talking about apples. ++ ++What is RAID5? ++ ++OK here is the deal, RAID5 uses ONLY ONE parity drive per stripe and many ++RAID5 arrays are 5 (if your counts are different adjust the calculations ++appropriately) drives (4 data and 1 parity though it is not a single drive ++that is holding all of the parity as in RAID 3 & 4 but read on). If you ++have 10 drives or say 20GB each for 200GB RAID5 will use 20% for parity ++(assuming you set it up as two 5 drive arrays) so you will have 160GB of ++storage. Now since RAID10, like mirroring (RAID1), uses 1 (or more) mirror ++drive for each primary drive you are using 50% for redundancy so to get the ++same 160GB of storage you will need 8 pairs or 16 - 20GB drives, which is ++why RAID5 is so popular. This intro is just to put things into ++perspective. ++ ++RAID5 is physically a stripe set like RAID0 but with data recovery ++included. RAID5 reserves one disk block out of each stripe block for ++parity data. The parity block contains an error correction code which can ++correct any error in the RAID5 block, in effect it is used in combination ++with the remaining data blocks to recreate any single missing block, gone ++missing because a drive has failed. The innovation of RAID5 over RAID3 & ++RAID4 is that the parity is distributed on a round robin basis so that ++there can be independent reading of different blocks from the several ++drives. This is why RAID5 became more popular than RAID3 & RAID4 which ++must sychronously read the same block from all drives together. So, if ++Drive2 fails blocks 1,2,4,5,6 & 7 are data blocks on this drive and blocks ++3 and 8 are parity blocks on this drive. So that means that the parity on ++Drive5 will be used to recreate the data block from Disk2 if block 1 is ++requested before a new drive replaces Drive2 or during the rebuilding of ++the new Drive2 replacement. Likewise the parity on Drive1 will be used to ++repair block 2 and the parity on Drive3 will repair block4, etc. For block ++2 all the data is safely on the remaining drives but during the rebuilding ++of Drive2's replacement a new parity block will be calculated from the ++block 2 data and will be written to Drive 2. ++ ++Now when a disk block is read from the array the RAID software/firmware ++calculates which RAID block contains the disk block, which drive the disk ++block is on and which drive contains the parity block for that RAID block ++and reads ONLY the one data drive. It returns the data block. If you ++later modify the data block it recalculates the parity by subtracting the ++old block and adding in the new version then in two separate operations it ++writes the data block followed by the new parity block. To do this it must ++first read the parity block from whichever drive contains the parity for ++that stripe block and reread the unmodified data for the updated block from ++the original drive. This read-read-write-write is known as the RAID5 write ++penalty since these two writes are sequential and synchronous the write ++system call cannot return until the reread and both writes complete, for ++safety, so writing to RAID5 is up to 50% slower than RAID0 for an array of ++the same capacity. (Some software RAID5's avoid the re-read by keeping an ++unmodified copy of the orginal block in memory.) ++ ++Now what is RAID10: ++ ++RAID10 is one of the combinations of RAID1 (mirroring) and RAID0 ++(striping) which are possible. There used to be confusion about what ++RAID01 or RAID01 meant and different RAID vendors defined them ++differently. About five years or so ago I proposed the following standard ++language which seems to have taken hold. When N mirrored pairs are ++striped together this is called RAID10 because the mirroring (RAID1) is ++applied before striping (RAID0). The other option is to create two stripe ++sets and mirror them one to the other, this is known as RAID01 (because ++the RAID0 is applied first). In either a RAID01 or RAID10 system each and ++every disk block is completely duplicated on its drive's mirror. ++Performance-wise both RAID01 and RAID10 are functionally equivalent. The ++difference comes in during recovery where RAID01 suffers from some of the ++same problems I will describe affecting RAID5 while RAID10 does not. ++ ++Now if a drive in the RAID5 array dies, is removed, or is shut off data is ++returned by reading the blocks from the remaining drives and calculating ++the missing data using the parity, assuming the defunct drive is not the ++parity block drive for that RAID block. Note that it takes 4 physical ++reads to replace the missing disk block (for a 5 drive array) for four out ++of every five disk blocks leading to a 64% performance degradation until ++the problem is discovered and a new drive can be mapped in to begin ++recovery. Performance is degraded further during recovery because all ++drives are being actively accessed in order to rebuild the replacement ++drive (see below). ++ ++If a drive in the RAID10 array dies data is returned from its mirror drive ++in a single read with only minor (6.25% on average for a 4 pair array as a ++whole) performance reduction when two non-contiguous blocks are needed from ++the damaged pair (since the two blocks cannot be read in parallel from both ++drives) and none otherwise. ++ ++One begins to get an inkling of what is going on and why I dislike RAID5, ++but, as they say on late night info-mercials, there's more. ++ ++What's wrong besides a bit of performance I don't know I'm missing? ++ ++OK, so that brings us to the final question of the day which is: What is ++the problem with RAID5? It does recover a failed drive right? So writes ++are slower, I don't do enough writing to worry about it and the cache ++helps a lot also, I've got LOTS of cache! The problem is that despite the ++improved reliability of modern drives and the improved error correction ++codes on most drives, and even despite the additional 8 bytes of error ++correction that EMC puts on every Clariion drive disk block (if you are ++lucky enough to use EMC systems), it is more than a little possible that a ++drive will become flaky and begin to return garbage. This is known as ++partial media failure. Now SCSI controllers reserve several hundred disk ++blocks to be remapped to replace fading sectors with unused ones, but if ++the drive is going these will not last very long and will run out and SCSI ++does NOT report correctable errors back to the OS! Therefore you will not ++know the drive is becoming unstable until it is too late and there are no ++more replacement sectors and the drive begins to return garbage. [Note ++that the recently popular IDE/ATA drives do not (TMK) include bad sector ++remapping in their hardware so garbage is returned that much sooner.] ++When a drive returns garbage, since RAID5 does not EVER check parity on ++read (RAID3 & RAID4 do BTW and both perform better for databases than ++RAID5 to boot) when you write the garbage sector back garbage parity will ++be calculated and your RAID5 integrity is lost! Similarly if a drive ++fails and one of the remaining drives is flaky the replacement will be ++rebuilt with garbage also propagating the problem to two blocks instead of ++just one. ++ ++Need more? During recovery, read performance for a RAID5 array is ++degraded by as much as 80%. Some advanced arrays let you configure the ++preference more toward recovery or toward performance. However, doing so ++will increase recovery time and increase the likelihood of losing a second ++drive in the array before recovery completes resulting in catastrophic ++data loss. RAID10 on the other hand will only be recovering one drive out ++of 4 or more pairs with performance ONLY of reads from the recovering pair ++degraded making the performance hit to the array overall only about 20%! ++Plus there is no parity calculation time used during recovery - it's a ++straight data copy. ++ ++What about that thing about losing a second drive? Well with RAID10 there ++is no danger unless the one mirror that is recovering also fails and ++that's 80% or more less likely than that any other drive in a RAID5 array ++will fail! And since most multiple drive failures are caused by ++undetected manufacturing defects you can make even this possibility ++vanishingly small by making sure to mirror every drive with one from a ++different manufacturer's lot number. ("Oh", you say, "this schenario does ++not seem likely!" Pooh, we lost 50 drives over two weeks when a batch of ++200 IBM drives began to fail. IBM discovered that the single lot of ++drives would have their spindle bearings freeze after so many hours of ++operation. Fortunately due in part to RAID10 and in part to a herculean ++effort by DG techs and our own people over 2 weeks no data was lost. ++HOWEVER, one RAID5 filesystem was a total loss after a second drive failed ++during recover. Fortunately everything was on tape. ++ ++Conclusion? For safety and performance favor RAID10 first, RAID3 second, ++RAID4 third, and RAID5 last! The original reason for the RAID2-5 specs ++was that the high cost of disks was making RAID1, mirroring, impractical. ++That is no longer the case! Drives are commodity priced, even the biggest ++fastest drives are cheaper in absolute dollars than drives were then and ++cost per MB is a tiny fraction of what it was. Does RAID5 make ANY sense ++anymore? Obviously I think not. ++ ++To put things into perspective: If a drive costs $1000US (and most are far ++less expensive than that) then switching from a 4 pair RAID10 array to a 5 ++drive RAID5 array will save 3 drives or $3000US. What is the cost of ++overtime, wear and tear on the technicians, DBAs, managers, and customers ++of even a recovery scare? What is the cost of reduced performance and ++possibly reduced customer satisfaction? Finally what is the cost of lost ++business if data is unrecoverable? I maintain that the drives are FAR ++cheaper! Hence my mantra: ++ ++NO RAID5! NO RAID5! NO RAID5! NO RAID5! NO RAID5! NO RAID5! NO RAID5! ++ ++Art S. Kagel ++ --- mdadm-2.6.2.orig/debian/patches/Makefile +++ mdadm-2.6.2/debian/patches/Makefile @@ -0,0 +1,4 @@ +.PHONY: 00list +00list: + find -maxdepth 1 -type f -name \*.dpatch -print \ + | sed -re 's,^\./(.*)\.dpatch$$,\1,' | sort -n > $@ --- mdadm-2.6.2.orig/debian/patches/80-rootraiddoc.dpatch +++ mdadm-2.6.2/debian/patches/80-rootraiddoc.dpatch @@ -0,0 +1,1344 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 99-rootraiddoc.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff -urNad trunk~/rootraiddoc.97.html trunk/rootraiddoc.97.html +--- trunk~/rootraiddoc.97.html 1970-01-01 01:00:00.000000000 +0100 ++++ trunk/rootraiddoc.97.html 2006-07-20 17:22:59.366389277 +0100 +@@ -0,0 +1,1333 @@ ++ ++ ++ ++ Convert Root System to Bootable Software RAID1 (Debian) ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++
++

++Convert Root System to Bootable Software RAID1 (Debian)

++

++How to convert a Debian system to bootable Software RAID 1 with a second hard drive, 'mdadm' and a few standard UNIX tools

++
++ ++

++Version 0.97 (2004-06-03) Lucas Albers -- admin At cs DOT montana dot edu and Roger Chrisman
++Home of most recent version: ++http://alioth.debian.org/projects/rootraiddoc
++Thanks to: Alvin Olga, Era Eriksson, Yazz D. Atlas, James Bromberger, Timothy F Nagy, and alioth.debian.org
++

++WARNING: No warranty of any kind. Proceed at your own risk. A typo, especially in lilo.conf, can leave your system unbootable. Back-up data and make a boot floppy before starting this procedure.

++ ++ ++ ++
++ ++

Table of Contents

++ ++

++Summary

++ ++

++Procedure

++ ++
    ++
  1. ++Install Debian
    ++on your Primary Master disk -- hda. Or if you already have Debian installed, go to step 2.
    2. ++
  2. ++Upgrade to RAID savvy Kernel
    ++and install 'mdadm'.
    3. ++
  3. ++Setup RAID 1
    ++declaring disk-one 'missing' and disk-two hdc.
    4. ++
  4. ++Copy your Debian system
    ++from hda to /dev/md0 ('missing' + 'hdc').
    5. ++
  5. ++Reboot to RAID device.
    6. ++
  6. ++Reformat hda as 'fd' and declare it as disk-one of your RAID,
    ++and watch the booted RAID system automatically mirror itself onto the new drive. Done.
    7. ++
++ ++

Alternate grub/initrd procedure

++
    ++
  1. ++Part II. RAID using initrd and grub
    2. ++
++ ++

++Appendix

++ ++
    ++
  1. ++RAID Introduction
    2. ++
  2. ++Drive designators (hda, hdb, hdc, hdd), jumpers and cables
    3. ++
  3. ++Setting up software RAID for multiple partitions
    4. ++
  4. ++Lilo
    5. ++
  5. ++Copying Data
    6. ++
  6. ++Rebooting
    7. ++
  7. ++Initrd
    8. ++
  8. ++Verify that system will boot even with one disk off-line
    9. ++
  9. ++Setting up a RAID 1 Swap device
    10. ++
  10. ++Performance Optimizations
    11. ++
  11. ++Disaster Recovery
    12. ++
  12. ++Quick Reference
    13. ++ ++
  13. ++Troubleshooting
    14. ++
  14. ++Raid Disk Maintenance
    15. ++
++ ++

++References

++ ++
++ ++ ++ ++ ++

++Summary

++

++We begin with Debian installed on the Primary Master drive, hda (step 1). We need RAID support in our Kernel (step 2). We add another disk as Secondary Master, hdc, set it up for RAID (step 3), and copy Debian to it (step 4). Now we can reboot to the RAID device (step 5) and declare hda part of the RAID and it automatically syncs with hdc to complete our RAID 1 device (step 6).

++

++If all goes well

++
    ++
  • You do not need a rescue disk or to boot off anything except the hard drive.
    • ++
  • You can do this operation completely remotely.
    • ++
  • And you will not lose any data.
    • ++
++

++Use this HowTo at your own risk. We are not responsible for what happens!

++

++First things first

++
    ++
  • Backup your data.
    • ++
  • Create a boot floppy.
    • ++
++

++Whenever you change your partitions, you need to reboot! (If you know what you are ++doing, ignore this advice.)

++

++I assume you will mess up a step so wherever possible, we include verification.

++

++I use 'mdadm' because it is easier than 'raidtools' or 'raidtools2'.

++

++
We now have grub and lilo directions, grub directions are still in beta form. ++
Read the grub directions, and comment on them.

++ ++ ++ ++ ++ ++ ++ ++ ++

++Procedure

++ ++ ++

++1. Install Debian

++

++Do a fresh install the normal way on your first drive, hda (the Primary Master drive in your computer). ++Or, if you already have a running Debian system that you want to use on hda; skip ahead to step 2. ++If you need Debian installation instructions, see:

++

++ ++Debian Installation HowTo » http://www.debian.org/releases/stable/installmanual

++

++ ++Sarge Debian Installation HowTo » http://d-i.alioth.debian.org/manual/

++ ++ ++

++2. Upgrade to a RAID savvy Kernel

++ ++ ++

++2.1 Compile and install a RAID savvy Kernel.

++

++RAID must be compiled into the Kernel, not added as a module, for you to boot from the RAID device (unless you use a RAID savvy initrd kernel or boot from a non-RAID boot drive. (I now cover initrd methods!). You need RAID 1 but I usually include RAID 5, too. For step by step Kernel compile and install instructions, see:

++

++Creating custom Kernels with Debian's kernel-package system » http://newbiedoc.sourceforge.net/system/kernel-pkg.html

++ ++
++ ++

++2.2 Verify your RAID savvy Kernel.

++

++cat /proc/mdstat

++

++(You should see the RAID "personalities" your Kernel supports.)

++Something like this: ++ ++

++Personalities : [linear] [raid0] [raid1] [raid5] ++read_ahead 1024 sectors ++md4 : active raid5 hdh4[3] hdg4[2] hdf4[1] hde4[0] ++ 356958720 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] ++ ++unused devices: ++

++ ++

++YOU MUST VERIFY you have raid support via /proc/mdstat. ++This is the most important item to verify before going any farther. ++So the kernel has to support it or you have to load the modules in initrd. ++

++ ++ ++(This will show you if raid is compiled into kernel, or detected as a module from initrd.) ++/etc/modules will not list RAID if Kernel has RAID compiled in instead of loaded as modules. ++
++ Use lsmod to list currently loaded modules, this will show raid modules loaded. ++

++ reiserfs
++raid1
++ext2
++ide-disk
++raid5
++ext3
++

++cat /etc/modules

++

++(IF YOU SEE ANY RAID LISTED IN /etc/modules, then you probably have your Kernel loading RAID via modules. That will prevent you from booting from your RAID device, unless you use initrd. To boot from your RAID device, unless you use a RAID savvy initrd, you need RAID compiled into Kernel, not added as a module.)

++

++ ++ ++

2.3 Install 'mdadm':

++

++apt-get install mdadm

++2.4 List what IDE devices you have: ++

++ls /proc/ide

++ ++ ++

++3. Setup RAID 1

++

++Setup RAID 1 and declare disk-one of your RAID to be 'missing' and disk-two of your RAID to be 'hdc'.

++ ++ ++

++3.1 Create RAID (fd) partition on hdc

++

++Warning: ALWAYS give the partition when editing with cfdisk. By default cfdisk will select the first disk in the system. I accidentally wiped the wrong partition with cfdisk, once.

++

++Do A or B, either way will work:

++

++A. Create partitions on new disk.

++

++cfdisk /dev/hdc

++ ++

or

++ ++

B. copy existing partitions to new disk with sfdisk.

++

++sfdisk -d /dev/hda | sfdisk /dev/hdc

++ ++
NOTE: On some disks you cannot copy over the partitions correctly using this method ++
It will detect the new partition as 0 size or a strange size. ++
You will need to manually create the partitions, making them the same size with cfdisk. ++
++

++3.2 Create correct partition type signatures on new partition.

++

++cfdisk /dev/hdc

++ ++
    ++
  • Select Type, then hit enter, then type 'fd' (this means RAID type partition).
    • ++
  • Select Write
    • ++
  • Select Quit.
    • ++
++ ++

++reboot

++

++(To verify that everything is working ok.) ++ ++ ++

++3.3 Create RAID device

++

++that has two members and one of the members does not exist yet. md0 is the RAID partition we are creating, /dev/hdc1 is the initial partition. We will be adding /dev/hda1 back into the /dev/md0

++

++RAID set after we boot into /dev/md0.

++

++mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/hdc1

++

++If this gives errors then you need to zero the super block, see useful mdadm commands.

++ ++ ++

++3.4 Format RAID device

++

++You can use reiserfs or ext3 for this, both work, I use reiserfs for larger devices. Go with what you trust.

++

++mkfs.ext3 /dev/md0

++

++or

++

++mkfs -t reiserfs /dev/md0

++ ++ ++ ++

++4. Copy your Debian system

++

++Copy your Debian system from hda to /dev/md0 ('missing' + 'hdc'). Then, check to ++make sure that the new RAID device is still setup right and can be mounted ++correctly. We do this with an entry in hda's /etc/fstab and a reboot. Note that ++by editing hda's /etc/fstab after the copy, instead of before, we leave the copy ++on md0 unaltered and only are editing hda's /etc/fstab.

++ ++ ++

++NB: THIS IS A BRANCH IN OUR SYSTEM CONFIGURATION (eg temporary!), but it ++will overwritten later by the md0 version of /etc/fstab by the sync in step 6.

++ ++ ++

++4.1 Create a mount point.

++

++mkdir /mnt/md0

++ ++ ++

++4.2 Mount your RAID device.

++

++mount /dev/md0 /mnt/md0

++ ++ ++

++4.3 Copy your Debian system to RAID device.

++

++cp -axu / /mnt/md0

++Please refer to the Copying data section to verify you copied the data correctly. ++
See Copying Data ++

++You don't need the -u switch; it just tells cp not to copy the files again if they exist. If you are running the command a second time it will run faster with the -u switch.

++ ++ ++

++4.4 Edit /etc/fstab so that you mount your new RAID partition on boot up.

++

++This verifies that you have the correct partition signatures on the partition and that your partition is correct. Sample Line in /etc/fstab:

++

++/dev/md0 /mnt/md0 ext3 defaults 0 0

++

++Then

++

++reboot

++

++And see if the RAID partition comes up.

++

++mount

++

++Should show /dev/md0 mounted on /mnt/md0.

++ ++ ++ ++

++5. Reboot to RAID device

++

++For step 5 reboot, we will tell Lilo that ++

    ++
  • as before, /boot and MBR are still on hda,
    ++
  • and now we want root (/) to mount on md0.
    ++

++

++We will, as before, be using hda's MBR (Master Boot Record is the first 512 bytes on a disk and is what the BIOS reads first in determining how to boot up a system) and hda's /boot dir (the kernel-image and some other stuff live here), but instead of mounting root (/) from hda, we will mount md0's root (/) (the root of our RAID device, currently running off of only hdc because we declared the first disk 'missing'). ++ ++ ++

++5.1 Configure Lilo to boot to the RAID device

++

++(Later we will configure Lilo to write the boot sector to the RAID boot device also, so we can still boot even if either disk fails.)

++

++Add a stanza labeled 'RAID' to /etc/lilo.conf on hda1 so that we can boot with /dev/md0, our RAID device, as root (/):

++

++#the same boot drive as before.
++boot=/dev/hda
++image=/vmlinuz
++label=RAID
++read-only
++#our new root partition.
++root=/dev/md0

++

++That makes an entry labeled 'RAID' specific to the RAID device, so you can still boot to /dev/hda if /dev/md0 does not work.

++sample complete lilo.conf file:

++

++#sample working lilo.conf for raid.
++#hda1,hdc1 are boot, hda2,hdc2 are swap
++#hda3,hdc3 are the partition used by array
++#root partition is /dev/md3 on / type reiserfs (rw)
++#I named the raid volumes the same as the partition numbers
++#this is the final lilo.conf file of a system completely finished,
++#and booted into raid.
++
++
++lba32
++boot=/dev/md1
++root=/dev/hda3
++install=/boot/boot-menu.b
++map=/boot/map
++ prompt
++ delay=50
++ timeout=50
++ vga=normal
++ raid-extra-boot=/dev/hda,/dev/hdd
++ default=RAID
++ image=/boot/vmlinuz-RAID
++ label=RAID
++ read-only
++ root=/dev/md3
++ alias=1
++ ++ image=/vmlinuz
++ label=Linux
++ read-only
++ alias=2
++
++ image=/vmlinuz.old
++ label=LinuxOLD
++ read-only
++ optional

++ ++ ++

++5.2 Test our new lilo.conf

++

++lilo -t -v

++

++(With a RAID installation, always run lilo -t first just to have Lilo tell you what it is about to do; use the -v flag, too, for verbose output.)

++ ++ ++

++5.3 Run Lilo

++

++Configure a one time Lilo boot via the -R flag and with a reboot with Kernel panic

++

++The -R <boot-parameters-here> tells Lilo to only use the specified image for the next boot. So once you reboot it will revert to your old Kernel.

++

++From 'man lilo':
++-R command line
++This option sets the default command for the boot loader the next time it executes. The boot loader will then erase this line: this is a once-only command. It is typically used in reboot scripts, just before calling `shutdown -r'. Used without any arguments, it will cancel a lock-ed or fallback command line.

++

Before you can do the 'lilo -v -R RAID' command, you must first do a 'lilo' command to update the Lilo boot record with the contents of your new lilo.conf. Otherwise Lilo does not know what you mean by 'RAID' and you just get a 'Fatal: No image "RAID" is defined' error message when you do 'lilo -v -R RAID'. So,

++

++lilo
++lilo -v -R RAID

++ ++ ++

++5.4 Edit /mnt/md0/etc/fstab and reboot

++

++to have /dev/md0 mount as root (/), when Lilo boots from our RAID device, /dev/md0.

++

++Previous root (/) in fstab was:

++

++/dev/hda1 / reiserfs defaults 0 0

++

++Edit it to:

++

++/dev/md0 / ext3 defaults 0 0

++

++Note: edit /mnt/md0/etc/fstab, not /etc/fstab, because at the moment we are booted with hda1 as root (/) but we want to change the /etc/fstab that we currently have mounted on /mnt/md0/etc/fstab, our RAID device.

++

++Reboot to check if system boots our RAID device, /dev/md0, as root (/). If it does not, just reboot again and you will come up with your previous boot partition courtesy of the -R flag in step 5.3 above.

++

++reboot

++

++Verify /dev/md0 is mounted as root (/)

++

++mount

++

++should show:

++ ++

++/dev/md0 on / type reiserfs (rw)
++proc on /proc type proc (rw)
++devpts on /dev/pts type devpts (rw,gid=5,mode=620)

++

++'type reiserfs' is just my example; you will see whatever your file system type is.

++

++Now we are booted into the new RAID device -- md0 as root (/). Our RAID device only has one disk in it at the moment because we earlier declared the other disk as 'missing'. That was because we needed that other disk, hda, to install Debian on or because it was our pre-existing Debian system.

++ ++ ++ ++

++6. Reformat hda as 'fd' and declare it as disk-one of your RAID

++ ++

++For step 6 reboots, we tell Lilo that ++

    ++
  • as in step 5 above, our root (/) is now on md0.
    • ++
  • and now, /boot is also on md0,
    • ++
  • and MBR is on both hda and hdc.
    • ++

++

++Here we not only use md0's root (/) as in step 5, but also md0's /boot (it contains an identical kernel-image to the one on hda because we copied it here from hda in step 4, but we will be overwriting everything on hda in step 6 and can't continue relying on the stuff on hda) and MBR from either hda or hdc, whichever the BIOS can find (they will be identical MBRs and the BIOS will still find hda's MBR but in case the hda disk were to fail down the road we would want the BIOS to look on hdc as a fail over so that it could still boot up the system).

++ ++ ++

++6.1 Change the signature on /dev/hda to software RAID

++

++cfdisk /dev/hda

++
    ++
  • Select "/dev/hda1"
    • ++
  • Then select "[Type]"
    • ++
  • Then hit "enter".
    • ++
  • Then type "FD".
    • ++
  • We are setting partition to "Software RAID"
    • ++
  • Should already be set.
    • ++
  • Then Select "Boot" if not set, so that you can boot ++off the device.
    • ++
  • All the boot partitions that are members of your bootable RAID device (hda1 and hdc1) should have the bootable flag set. If one is not set, set it here now
    • ++
  • Then select "Write" and enter 'yes'.
    • ++
  • Then select "Quite".
    • ++
++

++My two hard disks are from different manufacturers and as it happens, while both are roughly 40G, they have different architectures in terms of sectors and precise size. So cfdisk was unable to make the partitions precisely the same size and I had hda1 29,997.60MB and hdc1 30,000MB. This didn't work when I get to the 'mdadm --add /dev/md0 /dev/hda1' step. I got a, "failed: no space left on device!" error. So I ran cfdisk again and made hda1 slightly larger than hdc1, since I could not make them both exactly the same size. Now hda1 is 30,005.83MB and the 'mdadm -add /dev/md0 /dev/hda1' step works :-). (The remaining 10,000MB on each disk I am using for other purposes, including a md1 of 1,000MB composed of hda2 and hdc2.)

++ ++ ++

++6.2 Add the first-disk to our existing RAID device

++

++And watch the booted RAID system automatically mirror itself onto the new drive. We are currently booted from MBR and /boot device on /dev/hdc1, with /dev/md0 as root (/).

++

++mdadm --add /dev/md0 /dev/hda1

++

++Note: We are adding /dev/hda1 into our existing RAID device. See if it is syncing.

++

++cat /proc/mdstat

++

++should show that it is syncing.

++ ++ ++

++6.3 Write new /etc/lilo.conf settings

++

++these are from when we are booted onto RAID.

++

++boot=/dev/md0
++root=/dev/md0
++#this writes the boot signatures to either disk.
++raid-extra-boot=/dev/hda,/dev/hdc
++image=/vmlinuz
++label=RAID
++read-only

++

++YOU NEED THE raid-extra-boot to have it write the boot loader to all the disks.

++

++YOU ARE OVERWRITING THE BOOT LOADER ON BOTH /dev/hda and /dev/hdc.

++

++You can keep your old boot option to boot /dev/hda so you can boot RAID and /dev/hda.

++

++But remember you don't want to boot into a RAID device in non RAID as it will hurt the synchronization. If you make changes on one disk and not the other.

++ ++ ++

++6.4 Run Lilo with -R option and reboot

++

++(we are currently booted into RAID)

++

++lilo -t -v

++

++lilo -R RAID

++

++The -R option tells Lilo it to use the new Lilo setting only for the next reboot, and then revert back to previous setting.

++

++

++Note 1: Step 6.4 returned an error, "Fatal: Trying to map files from unnamed device 0x0000 (NFS/RAID mirror down ?)."

++

++So I waited for the synchronization, started in Step 6.2, to finish (checking it with 'cat /proc/mdstat'). Once it was done, did 'lilo -t -v' again. No "Fatal" error; Lilo seems happy now (no "Fatal" message).

++ ++Note 1a: The synchronization however took two hours! I checked with 'hdparm' and it seems I have DMA turned off. Perhaps the synchronization would go faster with DMA turned on. Some examination of my system revealed that I did not have my computer's PCI chipset support compiled into my custom kernel. I recompiled the kernel (kernel 2.6.4) and selected the correct PCI chipset support for my computer and now DMA works correctly :-) and by default. For DMA to be default is also configurable in the PCI area of 'make menuconfig' during kernel compile configuration, and I chose it.

++

++So I can now do Lilo with '-R ' switch and reboot.

++

++Note 2: another error, "Fatal: No image "RAID" is defined."

++

++As in Step 5.3 above, I need to do 'lilo' first so that Lilo reads my new /etc/lilo.conf, otherwise Lilo does not know about my stanza labeled "RAID" which is new in my lilo.conf. (Yes I told Lilo about it on hda1 in step 5.3, but that was after I had copied the hda1 root (/) system to here, md0, which branched my system into two separate system configurations. So it needs to be done here, too. Then I can do 'lilo -R RAID'.

++

++Note 2a: However, the '-R' switch is pointless here unless the lilo.conf stanza labeled "RAID" is *not* the first kernel-image stanza in my lilo.conf. Because if it *is* the first stanza, then it is the default stanza anyway, with or without the '-R'.

++

++

++Then

++

++reboot

++

++and check

++

++cat /proc/mdstat ++

++and check

++

++mount

++

++to be sure all is as expected.

++ ++ ++

++6.5 Now run Lilo normally (without -R) and reboot

++

++See what Lilo will do.

++

++lilo -t -v

++

++If it looks okay, do it:

++

++lilo

++

++reboot

++

++and check

++

++cat /proc/mdstat

++

++and check

++

++mount

++

++as a final system check.

++ ++

++Done.

++ ++ ++ ++ ++ ++ ++ ++

Part II. RAID using initrd and grub

- Ferdy Nagy ++

I used the following procedure with stock Debian 2.6.5, which has an initrd with all the modules ready to boot ++into RAID. The procedure also covers using grub as the boot loader. I built this from a bare install of Sarge ++using the new installer with grub as the boot loader, but most of this document is distro independent. My file system ++throughout is ext3 and it shouldn't take too much to use reiserfs.

++

These steps reference back to the procedure sections outlined above and indicate where things differ due to initrd or ++grub, so you will have to read/do/be familiar with the above steps. Also, make sure you currently use grub ++as your boot loader, if you are using LILO, install grub and make sure it works before proceeding!

++ ++ ++

Section - 2. Upgrade to a RAID savvy kernel

++ ++Section 2 ++

When using initrd the kernel does not need to have the RAID compiled in, they will be loaded as modules. Make sure ++the kernel loads the RAID modules.

++ ++

Edit /etc/modules and add

++

md
++raid1

++ ++ ++

Section - 3. Setup RAID 1

++Follow section 3 to setup the RAID 1. ++ ++ ++

Section - 4. Copy your Debian system

++Follow section 4 to copy the debian system. ++ ++ ++

Section - 5. Reboot to RAID device

++ ++

Instead of section 5 using LILO, grub is used as the boot loader, and initrd used to load the kernel. A new kernel ++entry in the grub menu is created that refers to an initrd that is created which will start the md [raid] device. ++The original kernel entry will remain and can be reverted to if something goes wrong until RAID is running. This will ++still use grub loaded installed on the /dev/hda MBR.

++ ++

5.1 Build a new RAID initrd

++ ++

A) Make sure the initrd has the modules it needs, by editing /etc/mkinitrd/modules. Add the ++following [you can see what modules are available by mounting the initrd and looking in the lib/modules - see section 8.]:

++

++ md
++ raid1

++ ++

B) Update the initrd so that the root device loaded is the raid device, not probed. Edit the /etc/mkinitrd/mkinitrd.conf, and update the ROOT line
++ROOT=/dev/md0

++ ++

C) Create the new initrd and a link to it.

++

mkinitrd -o /boot/initrd.img-2.6.5-raid

++ ++ ++

5.2 Update the grub boot menu

++ ++

edit /boot/grub/menu.lst

++

1. Add the following entry

++

++

++title           Debian GNU/Linux, kernel 2.6.5-1-686 RAID
++root            (hd0,0)
++kernel          /boot/vmlinuz-2.6.5-1-686 root=/dev/md0 ro
++initrd          /boot/initrd.img-2.6.5-1-686-raid
++savedefault
++boot
++
++

++

2. Update the following kernel root option in the file. Note: the grub known issues, so ++this option will not be used anyway.

++

# kopt=root=/dev/md0 ro
++ ++ ++

5.3 Do the above 5.4 Edit /mnt/md0/etc/fstab and reboot

++ ++

[Copied from Part I 5.4 above]

++

to have /dev/md0 mount as root (/), when grub boots from our RAID device, /dev/md0:

++

Previous root (/) in fstab was:

++

/dev/hda1 / ext3 defaults 0 0

++

Edit it to:

++

/dev/md0 / ext3 defaults 0 0

++

Note: edit /mnt/md0/etc/fstab, not /etc/fstab, because at the moment we are booted with hda1 as root (/) but we ++want to change the /etc/fstab that we currently have mounted on /mnt/md0/etc/fstab, our RAID device.

++

Reboot and choose the RAID kernel to check if system boots our RAID device, /dev/md0, as root (/). If it does not, just reboot again and choose the ++original pre-read kernel image

++

reboot

++

Verify /dev/md0 is mounted as root (/)

++

mount

++

should show something similar to:

++ ++

/dev/md0 on / type ext3 (rw)
++proc on /proc type proc (rw)
++devpts on /dev/pts type devpts (rw,gid=5,mode=620)

++ ++

Now we are booted into the new RAID device -- md0 as root (/). Our RAID device only has one disk in it at the ++moment because we earlier declared the other disk as 'missing'. That was because we needed that other disk, hda, to ++install Debian on or because it was our pre-existing Debian system.

++ ++cat /proc/mdstat shows the [degraded] array is up and running, note the [_U] - second disk is up.

++ ++ ++

Section - 6. Reformat hda as fd and declare it as disk-one of your raid

++ ++

6.1/2 Setup hda and add to array

++

Follow steps 6.1, and 6.2. Wait and make sure the drives are fully synced before proceeding. ++ ++

6.3 re-run mkinitrd again, and reboot.

++ ++

This is needed to make sure that mkinitrd starts the newly built array with all drives. mkinitrd uses mdadm -D to ++discover what drives to assemble in the array during startup, this is contained in a script in the initrd image. If this ++step is not done the next time you reboot the array will be degraded.

++ ++

Do the following

++

mkinitrd -o /boot/initrd-2.6.5-raid.img

++ ++

reboot

++ ++

and check the array is fully up, look for the [UU]

++ ++

cat /proc/mdstat

++ ++

and check /dev/md0 is mounted

++ ++

mount

++ ++ ++

7. Put grub into the MBR of the second disk

++ ++

grub refers to the boot(ed) device as hd0, so if the primary hard drive (/dev/hda) fails the system will look for ++the next bootable device (/dev/hdc) and loads it's MBR, which grub will still refer to as hd0. So, the grub ++configuration can still use hd0 even when the primary device fails.

++ ++

7.1 Put grub into the MBR

++ ++

These steps temporarily tell grub the second device is hd0 and then loads the MBR.

++ ++

start the grub command line, then run the load commands. Note: grub partition references ++are offset by 1, so in the following with a partition of /dev/hdc1, the root is (hd0,0) [previous line tells ++grub to set hdc as hd0]. If the partition was /dev/hdc2, the root would be (hd0,1)!

++

grub
++grub> device (hd0) /dev/hdc
++grub> root (hd0,0)
++grub> setup (hd0)
++

++ ++

7.2 Testing

++ ++

reboot, verify the /proc/mdstat devices always start. Follow section VIII and verify the ++system boots with one disk off line.

++ ++ ++

8. Known Issues

++ ++

grub

++

grub will already be installed on hda, and you will manually force grub to be installed on hdc so the MBRs are ++ok; however, install-grub and update-grub will fail because ++grub does not understand the md0 device. This is not a problem with install-grub as it will not be executed again ++after it has been installed, but update-grub is executed after an updated kernel is apt'd, causing an error to be ++reported by apt. The update-grub error is ok, the kernel gets installed and the initrd is created with all ++the md array information, provided the array was not degraded during the kernel upgrade. But you will have ++to manually update the grub menu.lst and add the new kernel information before you reboot, or the new ++kernel will not appear in the grub menu.

++ ++

mkinitrd

++

When using mdadm, mkinitrd will only detect disks in the array that are running at the time of execution. You should ++not install a new kernel while the array is degraded, otherwise, even if you do an mdadm --add, the next reboot will ++still be degraded! The array is started at boot time by script. You can see what ++is in the script of the initrd by mounting it, e.g.

++

mount /boot/initrd.img-X.X.X /mnt -o loop
++cat /mnt/script

++

And look for the array start line similar to

++

mdadm -A /devfs/md/0 -R -u 23d8dd00:bc834589:0dab55b1:7bfcc1ec /dev/hda1 /dev/hdc1

++ ++ ++ ++ ++

++Appendix

++ ++ ++

++I. RAID 1 Introduction

++

++Redundant Array of Inexpensive Disks (RAID) refers to putting more than one hard disk to work together in various advantageous ways. Hardware RAID relies on special hardware controllers to do this and we do not covered in this HowTo. Software RAID, this HowTo, uses software plus the ordinary controllers on your computer's motherboard and works excellently.

++

++RAID 1 is where you use two hard drives as if they were one by mirroring them onto each other. Advantages of RAID 1 are (a) faster data reads because one part of the data can be read from one of the disks while simultaneously another part of the data is read from the other disk, and (b) a measure of fail over stability -- if one of the disks in the RAID 1 fails, the system will usually stay online using the remaining drive while you find time to replace the failed drive.

++

++To achieve the speed gain, the two disks that comprise your RAID 1 device must be on separate controllers (in other words, on separate drive cables). The first part of the data is read from one disk while simultaneously the second part of data is read from the other disk. Writing data to a RAID 1 device takes twice as long apparently. However, under most system use data is more often read from disk than written to disk. So RAID 1 almost doubles the effective speed of your drives. Nice.

++

++RAID is not a substitute for regular data back ups. Many things can happen that destroy both your drives at the same time.

++ ++ ++ ++

++II. Drive designators (hda, hdb, hdc, hdd), jumpers and cables

++

++Drive designators.

++

++Drives on IDE 1 -- Primary Controller

++
    ++
  • ++hda, Primary Master drive
    • ++
  • ++hdb, Primary Slave drive
    • ++
++

++Drives on IDE 2 -- Secondary Controller

++
    ++
  • ++hdc, Secondary Master drive
    • ++
  • ++hdd, Secondary Slave drive
    • ++
++

++Jumpers. When moving drives around in your computer, be sure to set the jumpers on your drives correctly. They are the little clips that connect two of various pins on your drive to set it to Cable Select, Master, or Slave. IDE drives usually have a diagram right on their case that shows where to set the clip for what setting. Different brands sometimes use different pin configurations. ++

++Cables. Use 80 wire 40 pin IDE drive cables, not 40 wire 40 pin or you will slow down your hard drive access. For best results, cables should be no longer than the standard 18". If your cable has a blue end, that's the end to attach to the mother board (I don't know why). I don't think it matters which of the two drive connectors on the cable you plug your drive into, the middle or end one, unless you use Cable Select in which case I believe the sable's end plug is Master and its middle plug is Slave.

++ ++ ++ ++

++III. Setting up software RAID for multiple partitions.

++

++You can have a multi-partition RAID system if you prefer. You just need to create multiple RAID devices.

++

++I have found it useful when setting software RAID on multiple partitions to set the RAID device to the same name as the disk partition.

++

++If you have 3 partitions on /dev/hda and I want to add /dev/hdc for software RAID, then boot /dev/hdc and add /dev/hda back into the device, exactly what I did earlier, but with 3 partitions which are: hda1=/boot, hda2=/, hda3=/var

++

++sfdisk -d /dev/hda | sfdisk /dev/hdc;
++reboot
++mdadm --zero-superblock /dev/hda1
++mdadm --zero-superblock /dev/hda2
++mdadm --zero-superblock /dev/hda3
++mdadm --create /dev/md1 --level=1 --raid-disks=2 missing /dev/hdc1
++mdadm --create /dev/md2 --level=1 --raid-disks=2 missing /dev/hdc2
++mdadm --create /dev/md3 --level=1 --raid-disks=2 missing /dev/hdc3
++mkfs.reiserfs /dev/md1;mkfs.reiserfs /dev/md2; mkfs /dev/md3;
++mkdir /mnt/md1 /mnt/md2 /mnt/md3;
++cp -ax /boot /mnt/md1;cp -ax / /mnt/md2; cp -ax /var /mnt/md3;

++

++add entry in current fstab for all 3 and REBOOT.

++

++Sync data again, only copying changed stuff. ++

++cp -aux /boot /mnt/md1;cp -aux / /mnt/md2; cp -aux /var /mnt/md3;

++

++edit lilo.conf entry in this case: ++

++boot=/dev/md1
++root=/dev/md2

++

++Edit /mnt/md2/etc/fstab to have / set to /dev/md2.

++

++REBOOT into RAID.

++

++Add devices in: ++

++mdadm --add /dev/md1 /dev/hda1
++mdadm --add /dev/md2 /dev/hda2

++

++Wait for sync, write Lilo permanently, and REBOOT into your setup.

++

++It is not harder to include more devices in a software RAID device.

++ ++ ++ ++

++IV. Lilo

++

++You need special entries to use Lilo as your boot loader, I couldn't get grub to work, but nothing prevents you from using grub. Just standard Lilo/grub entries WILL NOT WORK FOR RAID.

++

++Entries in /etc/lilo.conf: ++

++raid-extra-boot=<option>

++

++That option only has meaning for RAID 1 installations. The <option> may be specified as none, auto, mbr-only, or a comma-separated list of devices; e.g., "/dev/hda,/dev/hdc6".

++

++panic='' line in lilo.conf tells Lilo to automatically boot back to the old install if something goes wrong with the new Kernel.

++ ++ ++ ++

++V. Copying data

++

++Use "cp -aux" to just copy updated items. if you are copying a partition that is not root you need to copy the subdirectories and not the mount point, otherwise it will just copy the directory over. To copy boot which is a separately mounted partition to /mnt/md1 which is our new software RAID partition we copy as thus: "cp -aux /boot/* /mnt/md1" NOTE THE DIFFERENCE when copying mount points and not just /. If you just do cp -aux /boot /mnt/md1 it will just copy over boot as a subdirectory of /mnt/md1.

++

++Or, alternatively, you could copy the root system with 'find' piped to 'cpio', like this:

++

++cd /
++find . -xdev -print | cpio -dvpm /mnt/md0

++ ++ ++ ++ ++

++VI. Rebooting

++

++You should always reboot if you have changed your partitions, otherwise the Kernel will not see the new partitions correctly. I have changed partitions and not rebooted, and it caused problems. I would rather have the simpler longer less potentially troublesome approach. Just because it appears to work, does not mean it does work. You really only need to reboot if you are CHANGING or rebooting a new Lilo configuration. Don't email me if you hose yourself because you did not feel the urge to reboot. Trust me.

++ ++ ++ ++

++VII. initrd

++

++initrd: Use RAID as initrd modules.

++

++The Kernel that is installed when you first build a system does not use an initrd.img. ++However the default kernel uses initrd. So you can use a stock kernel for with ++software raid.

++

++The new Kernel by default won't contain the right modules for creating a RAID savvy initrd, but they can be added.

++

++ 

++(Per James Bromberger)

++Now we need to prepare for running a RAID setup. Our packages need an update. ++Use apt, because it rocks, and install the following:
++

++DevFSd
++kernel-image-2.4.x (whatever suits you)
++reiserfsprogs
++less
++screen
++vim
++

++...Anything else you need and can't live without for the next 10 minutes
++
++You might already have some of these modules in the kernel, eg ext2. ++Edit /etc/modules and add the following modules:
++

++reiserfs
++md
++raid1
++ext2
++ide-disk (might not need this one.)
++raid5
++ext3
++ide-probe-mod (might not need this one.)
++ide-mod (might not need this one.)
++

++
++Edit /etc/mkinitrd/modules, and add the same modules to this list. Your initrd ++image needs to be able to read and write to your RAID array, before your ++filesystem is mounted. Initrd is the trick here. You probably also want to see ++if you need to edit /etc/mkinitrd/mkinitrd.cfg and set the variable ROOT=probe ++to be ROOT=/dev/md0, or possibly, if using DevFS, ROOT=/dev/md/0.
++
++Regenerate your initrd image for your new kernel with ++

++ ++mkinitrd -o /tmp/initrd-new /lib/modules/2.4.x-... . ++ ++

If all is good, move this to /boot/initrd-2.4.x-... and ++edit your /etc/lilo.conf to add initrd=/boot/initrd against the "Linux" kernel ++entry. Run lilo, and you should see an asterisk next to the boot image "Linux".

++With those modules you should be able to install the new kernel-image package. The install will add those modules to the initrd.img that. Now you can do for example (I actually only tested with kernel-image-2.4.24-1-686-smp on a machine using testing and unstable listed in the /etc/apt/source.list) ++

++apt-get install kernel-image-2.4.24-1-686-smp

++

++You will need to modify /etc/lilo.conf to include the right stuff. Otherwise the post install scripts for the package will likely fail. ++

++image=/vmlinuz
++label=Linux
++initrd=/initrd.img

++

++(The above is all one line)

++

++Run Lilo and REBOOT.

++

++You should now have the modules loaded. Check with: cat /proc/mdstat

++ ++ ++ ++

++VIII. Verify that system will boot even with one disk off-line

++

++Roger did it this way.

++
    ++
  1. Shutdown and power-off your computer.
    2. ++
  2. Open up computer and unplug the power to Primary Master disk (/dev/hda).
    3. ++
  3. Start up your computer. It should boot up from the other disk.
    4. ++
  4. Now look at
    ++ cat /proc/mdstat
    ++ you should see that one of the disks in your md0 has "failed".
    5. ++
  5. Shutdown and then unplug the power to you computer, again.
    6. ++
  6. Reconnect the power to Primary Master disk.
    7. ++
  7. Start up your computer, again. It should boot up from the other disk still. It wont try to access the disk that it now has on record as "failed" until you re-add it to your RAID. Look again at
    ++ cat /proc/mdstat
    ++ you should still see one of the disks in your md0 listed as "failed". If this were not a simulation it probably would be failed and you would want to replace it with a new one. But for the simulation we just un-plug and later re-plug the power connector to the disk.
    8. ++
  8. Now that you have re-connected the power to the disk (or replaced it with a new one were it really was a failed disk) bring it back online with mdadm,
    ++ mdadm --add /dev/md0 /dev/hda1
    ++ and check its status with, ++ cat /proc/mdstat
    ++ you should see that it is being synchronized the the other disk in your RAID 1.
    9. ++
  9. WAIT until the synchronization has completed. Then you can try the above again but unplugging the other disk in your RAID 1. WARNING if you do not wait for synchronization to fully complete (check with '/proc/mdstat') you will have a real problem because your system is only partially rebuild on the "new" disk until synchronization has finished.
    10. ++
++

++NB: I (Roger) had to disconnect power to my CD-ROM drive (because my CD-ROM was on /dev/hdd -- Secondary Slave) in order to boot with my Secondary Master disconnected. Otherwise my BIOS refused to boot the machine because my CD-ROM was then a Slave on a cable without any Master. Your mileage may vary. :-) So I decided to leave my CD-ROM disconnected, as this is a server and I need it to boot even with a failed drive more than I need the convenience of keeping the CD-ROM connected. I can of course connect the CD-ROM when I need it as long as I have a working Master drive on its cable with it or set it to Master.

++ ++ ++ ++

++IX. Setting up a RAID 1 Swap device

++

++I created a swap RAID device as follows:

++

++(I have a 1000MB hda2 and a 1000MB hdc2, both as type 'fd' created with 'cfdisk', that I will use as md1 for swap.)

++

++ (Or you can just create the swap parttions on the actual disk, don't put swap on raid. ++ Just put a swap partition on each disk in your raid set on an empty partition.) ++ ++

++ ++

++Add a Swap entry in /etc/fstab, just after root (/) partition line. Example line to add to /etc/fstab: ++

++/dev/md1 none swap sw 0 0

++

++Reboot and the boot sequence should start up the Swap when it reads /etc/fstab.

++

++reboot

++

++ You can argue whether swap should be on raid. A large colo admin mentions that he does not use swap on raid. Keep it as simple as possible. You decide.

++ ++ ++ ++

++X. Performance Optimizations

++ For every ide drive turn on hdparm. ++
++

 

hdparm -d1 -c3 /dev/hda /dev/hdc

++
You need to use bonnie++ to measure software raid performance ++
You want all your devices to be as masters. As your limited to total bandwidth on that chain of ++
hard drives. ++
I just stick as many hard drives in the system as possible, ++
I have not encountered problems where having disks on the same master ++
slave channel caused a slowdown. ++ ++

++

++XI. Disaster Recovery ++

++ ++

++

++(These directions are untested, I need to adopt them to mdadm instead of raid2 --luke)

++ ++

So what to do if you can't get your root RAID1 filesystem to boot? Here is a ++straightforward way to get to your md0:

++
    ++
    Find the 2.4 kernel install media from $DEBIAN/dists/unstable/main/disks-i386, ++
    and download the bf2.4 set of disks. ++
    You only need the rescue and root images. ++
    Find the corresponding kernel-image-2.4.18-bf2.4_2.4.18-4_i386.deb or ++
    similar; and unpack this somewhere with ++

     

    ++

    dpkg-deb -x kernel-image-2.4.yy-bf45.deb temp/

    ++
    In the temp directory, find the md.o and raid1.o modules. ++
    Copy them to a new floppy in /floppy/boot. ++
    Copy /sbin/raid* to the root of the floppy disk (/floppy). You'll notice ++
    that all the raid programs are symlinks to the same binary; doesn't matter, ++
    since you probably have a vfat disk that doesn't know about symlinks. Just make ++
    multiple copies. (Or be smart here and use an ext2 disk). ++
    Boot with the rescue, then with the root disk ++
    After choosing a language and keyboard from the installer, choose to preload ++
    some modules. Grab that third disk you just put those modules and binaries on, ++
    and put it in the floppy drive. ++
    Load up md.o first, and then raid1.o. ++
    Press Alt-F2 to get a text console. ++

    ++
    mount /floppy ++
    cp /etc/raid* /sbin ++

    ++# (Ie: copy to the ramfs /sbin) ++
    mkdir /etc/raid

    ++cp /floppy/raidtab /etc/raid ++

    ++ln -s /etc/raid/raidtab /etc/raidtab ++

    ++raidstart /dev/md0

    ++mount -t reiserfs /dev/md0 /target

++

++ ++ ++

++XII. Quick Reference

++

++DON'T JUST LOOK AT THIS QUICK REFERENCE. Understand the rest of the document.

++

++Quick Reference -- setting up bootable system on /dev/md0 using /dev/hda and /dev/hdc as RAID 1 component disks

++

++Verify RAID savvy Kernel. (1) You should see the RAID "personalities" your Kernel supports:

++

++cat /proc/mdstat

++

++ dmsg|grep -i RAID ++

++(This will show you if raid is compiled into kernel, or detected as a module from initrd.) ++/etc/modules will not list RAID if Kernel has RAID compiled in instead of loaded as modules. ++Use lsmod to list currently loaded modules this will show raid modules loaded. ++

++(2) You should NOT see any RAID modules in /etc/modules (If you do, review step 2 of Procedure):

++

++cat /etc/modules

++

++Copy partitions hda to hdc: ++

++sfdisk -d /dev/hda | sfdisk /dev/hdc

++

++Create array: ++

++mdadm --create /dev/md0 --level=1 --raid-disks=2 missing /dev/hdc1

++

++Copy data: ++

++cp -ax / /mnt/md0

++

++Example /etc/lilo.conf entry for 1 disk RAID device: ++

++boot=/dev/hda
++image=/vmlinuz
++label=RAID
++read-only
++#our new root partition.
++root=/dev/md0

++

++Add second disk to array: ++

++mdadm --add /dev/md0 /dev/hdc1

++

++Example final /etc/lilo.conf entry: ++

++boot=/dev/md0
++root=/dev/md0
++#this writes the boot signatures to either disk.
++raid-extra-boot=/dev/hda,/dev/hdc
++image=/vmlinuz
++label=RAID
++read-only

++ ++ ++

++Useful 'mdadm' commands

++

++Always zero the superblock of a device before adding it to a RAID device. Why? Because the disks decide what array they are in based on the disk-id information written on them. Zero the superblock first in case the disk was part of a previous RAID device. Also, if a partition was part of a previous RAID device, it appears to store the size of it's previous partition in the signature. Zeroing the superblock before adding it to a new RAID device takes care of cleaning up that, too.

++

++Erase the MD superblock from a device: ++

++mdadm --zero-superblock /dev/hdx

++

++Remove disk from array:

++

++mdadm --set-faulty /dev/md1 /dev/hda1
++mdadm --remove /dev/md1 /dev/hda1

++

++Replace failed disk or add disk to array: ++

++mdadm --add /dev/md1 /dev/hda1

++

++(that will format the disk and copy the data from the existing disk to the new disk.)

++

++Create mdadm config file: ++

++echo "DEVICE /dev/hda /dev/hdc" > /etc/mdadm/mdadm.conf
++mdadm --brief --detail --verbose /dev/md0 >> /etc/mdadm/mdadm.conf
++mdadm --brief --detail --verbose /dev/md1 >> /etc/mdadm/mdadm.conf

++

++To stop the array completely: ++

++mdadm -S /dev/md0

++ ++ ++ ++

++XIII. Troubleshooting

++
The main problems people encounter is:
++
Kernel must have support for raid compiled in or loaded correctly in initrd.
++
You will actually have 2 configurations of raid. You boot to the failed raid volume,
++
then add in the original disk, then boot the final raid configuration.
++ ++
Performance is too slow:
++
See Performance Optimizations ++ ++ ++

++XIIII. Raid Disk Maintenance.

++
You need to configure raid to monitor for errors.
++
It will email you when it detects and error
++
Once a failed disk is detected, remove it and then add it back in.
++
Create an mdadm.conf file
++
See mdadm commands ++
You can also configure hot spare, that will come online if a disk fails.
++
++

++ Finish directions on smart monitoring and mdadm configuration to monitor disks,and hot spares. ++

++ ++ ++ ++

++

++References

++

++RAID 1 Root HowTo PA-RISC
++http://www.pa-RISC-linux.org/faq/RAIDboot-howto.html

++

++Lilo RAID Configuration:
++http://lists.debian.org/debian-user/2003/debian-user-200309/msg04821.html

++

++Grub RAID Howto
++http://www.linuxsa.org.au/mailing-list/2003-07/1270.html

++

++Building a Software RAID System in Slackware 8.0
++http://slacksite.com/slackware/RAID.html

++

++Root-on-LVM-on-RAID HowTo
++http://www.midhgard.it/docs/lvm/html/install.disks.html

++

++Software RAID HowTo
++http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO.txt

++

++HowTo - Install Debian Onto a Remote Linux System
++http://trilldev.sourceforge.net/files/remotedeb.html

++

++Kernel Compilation Information and good getting started info for Debian
++http://newbiedoc.sourceforge.net

++

++Initrd information and Raid Disaster Recovery,

++

++ ++http://www.james.rcpt.to/programs/debian/raid1/

++ ++ ++ ++ ++ ++ --- mdadm-2.6.2.orig/debian/patches/99-init-avail-FIX.dpatch +++ mdadm-2.6.2/debian/patches/99-init-avail-FIX.dpatch @@ -0,0 +1,19 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 99-init-avail-FIX.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff -urNad mdadm-2.6.2~/Detail.c mdadm-2.6.2/Detail.c +--- mdadm-2.6.2~/Detail.c 2007-05-21 06:25:50.000000000 +0200 ++++ mdadm-2.6.2/Detail.c 2007-05-21 14:41:40.000000000 +0200 +@@ -59,7 +59,7 @@ + void *super = NULL; + int rv = test ? 4 : 1; + int avail_disks = 0; +- char *avail; ++ char *avail = NULL; + + if (fd < 0) { + fprintf(stderr, Name ": cannot open %s: %s\n", --- mdadm-2.6.2.orig/debian/patches/01-mdadm.conf-location.dpatch +++ mdadm-2.6.2/debian/patches/01-mdadm.conf-location.dpatch @@ -0,0 +1,117 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 01-mdadm.conf-location.dpatch by martin f. krafft +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: Reverses conffile locations to favour /etc/mdadm/mdadm.conf + +@DPATCH@ +diff -urNad mdadm-2.5.1~/Makefile mdadm-2.5.1/Makefile +--- mdadm-2.5.1~/Makefile 2006-06-26 00:06:29.000000000 +0200 ++++ mdadm-2.5.1/Makefile 2006-06-26 00:06:45.936514898 +0200 +@@ -48,8 +48,8 @@ + endif + + SYSCONFDIR = /etc +-CONFFILE = $(SYSCONFDIR)/mdadm.conf +-CONFFILE2 = $(SYSCONFDIR)/mdadm/mdadm.conf ++CONFFILE = $(SYSCONFDIR)/mdadm/mdadm.conf ++CONFFILE2 = $(SYSCONFDIR)/mdadm.conf + MAILCMD =/usr/sbin/sendmail -t + CONFFILEFLAGS = -DCONFFILE=\"$(CONFFILE)\" -DCONFFILE2=\"$(CONFFILE2)\" + CFLAGS = $(CWFLAGS) $(CXFLAGS) -DSendmail=\""$(MAILCMD)"\" $(CONFFILEFLAGS) +diff -urNad mdadm-2.5.1~/ReadMe.c mdadm-2.5.1/ReadMe.c +--- mdadm-2.5.1~/ReadMe.c 2006-06-25 23:52:13.000000000 +0200 ++++ mdadm-2.5.1/ReadMe.c 2006-06-26 00:06:34.108601730 +0200 +@@ -504,7 +504,7 @@ + + + char Help_config[] = +-"The /etc/mdadm.conf config file:\n\n" ++"The /etc/mdadm/mdadm.conf config file:\n\n" + " The config file contains, apart from blank lines and comment lines that\n" + " start with a hash(#), four sorts of configuration lines: array lines, \n" + " device lines, mailaddr lines and program lines.\n" +diff -urNad mdadm-2.5.1~/mdadm.8 mdadm-2.5.1/mdadm.8 +--- mdadm-2.5.1~/mdadm.8 2006-06-25 23:52:13.000000000 +0200 ++++ mdadm-2.5.1/mdadm.8 2006-06-26 00:06:34.116601671 +0200 +@@ -225,9 +225,9 @@ + .TP + .BR -c ", " --config= + Specify the config file. Default is to use +-.BR /etc/mdadm.conf , ++.BR /etc/mdadm/mdadm.conf , + or if that is missing, then +-.BR /etc/mdadm/mdadm.conf . ++.BR /etc/mdadm.conf . + If the config file given is + .B partitions + then nothing will be read, but +@@ -253,7 +253,7 @@ + permission to get any missing information, like component devices, + array devices, array identities, and alert destination from the + configuration file: +-.BR /etc/mdadm.conf . ++.BR /etc/mdadm/mdadm.conf . + One exception is MISC mode when using + .B --detail + or +@@ -985,7 +985,7 @@ + or requested with (a possibly implicit) + .B --scan. + In the later case, +-.B /etc/mdadm.conf ++.B /etc/mdadm/mdadm.conf + is used. + + If +@@ -1260,7 +1260,7 @@ + .B --scan + will cause the output to be less detailed and the format to be + suitable for inclusion in +-.BR /etc/mdadm.conf . ++.BR /etc/mdadm/mdadm.conf . + The exit status of + .I mdadm + will normally be 0 unless +@@ -1296,7 +1296,7 @@ + then multiple devices that are components of the one array + are grouped together and reported in a single entry suitable + for inclusion in +-.BR /etc/mdadm.conf . ++.BR /etc/mdadm/mdadm.conf . + + Having + .B --scan +@@ -1706,7 +1706,7 @@ + on Monitor mode. + + +-.SS /etc/mdadm.conf ++.SS /etc/mdadm/mdadm.conf + + The config file lists which devices may be scanned to see if + they contain MD super block, and gives identifying information +diff -urNad mdadm-2.5.1~/mdadm.conf.5 mdadm-2.5.1/mdadm.conf.5 +--- mdadm-2.5.1~/mdadm.conf.5 2006-06-25 23:52:13.000000000 +0200 ++++ mdadm-2.5.1/mdadm.conf.5 2006-06-26 00:06:34.116601671 +0200 +@@ -2,7 +2,7 @@ + .SH NAME + mdadm.conf \- configuration for management of Software Raid with mdadm + .SH SYNOPSIS +-/etc/mdadm.conf ++/etc/mdadm/mdadm.conf + .SH DESCRIPTION + .PP + .B mdadm +diff -urNad mdadm-2.5.1~/mdassemble.8 mdadm-2.5.1/mdassemble.8 +--- mdadm-2.5.1~/mdassemble.8 2006-06-25 23:52:13.000000000 +0200 ++++ mdadm-2.5.1/mdassemble.8 2006-06-26 00:06:34.116601671 +0200 +@@ -33,7 +33,7 @@ + + .SH FILES + +-.SS /etc/mdadm.conf ++.SS /etc/mdadm/mdadm.conf + + The config file lists which devices may be scanned to see if + they contain MD super block, and gives identifying information --- mdadm-2.6.2.orig/debian/mdadm.examples +++ mdadm-2.6.2/debian/mdadm.examples @@ -0,0 +1,2 @@ +mdadm.conf-example +misc/syslog-events --- mdadm-2.6.2.orig/debian/mdadm.cron.d +++ mdadm-2.6.2/debian/mdadm.cron.d @@ -0,0 +1,14 @@ +# +# cron.d/mdadm -- schedules periodic redundancy checks of MD devices +# +# Copyright © martin f. krafft +# distributed under the terms of the Artistic Licence 2.0 +# +# $Id: mdadm.cron.d 147 2006-08-30 09:26:11Z madduck $ +# + +# By default, run at 01:06 on every Sunday, but do nothing unless the day of +# the month is less than or equal to 7. Thus, only run on the first Sunday of +# each month. crontab(5) sucks, unfortunately, in this regard; therefore this +# hack (see #380425). +6 1 * * 0 root [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 7 ] && /usr/share/mdadm/checkarray --cron --all --quiet --- mdadm-2.6.2.orig/debian/mdadm.logcheck.violations +++ mdadm-2.6.2/debian/mdadm.logcheck.violations @@ -0,0 +1,3 @@ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: kicking non-fresh [[:alnum:]]+ from array!$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: raid[[:digit:]]+: Disk failure on [[:alnum:]]+, disabling device\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+Operation continuing on [[:digit:]]+ devices?$ --- mdadm-2.6.2.orig/debian/mdadm.init +++ mdadm-2.6.2/debian/mdadm.init @@ -0,0 +1,80 @@ +#!/bin/sh +# +# Start the MD monitor daemon for all active MD arrays if desired. +# +# Copyright © 2001-2005 Mario Jou/3en +# Copyright © 2005-2006 Martin F. Krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: mdadm.init 290 2006-12-19 08:18:50Z madduck $ +# +### BEGIN INIT INFO +# Provides: mdadm +# Required-Start: $local_fs $remote_fs +# Required-Stop: $local_fs $remote_fs +# Default-Start: 2 3 4 5 +# Default-Stop: 0 1 6 +# Short-Description: MD monitoring daemon +# Description: mdadm provides a monitor mode, in which it will scan for +# problems with the MD devices. If a problem is found, the +# administrator is alerted via email, or a custom script is +# run. +### END INIT INFO + +set -eu + +MDADM=/sbin/mdadm +RUNDIR=/var/run/mdadm +PIDFILE=$RUNDIR/monitor.pid +DEBIANCONFIG=/etc/default/mdadm + +test -x "$MDADM" || exit 0 + +test -f /proc/mdstat || exit 0 + +START_DAEMON=true +test -f $DEBIANCONFIG && . $DEBIANCONFIG + +. /lib/lsb/init-functions + +is_true() +{ + case "${1:-}" in + [Yy]es|[Yy]|1|[Tt]|[Tt]rue) return 0;; + *) return 1; + esac +} + +case "${1:-}" in + start) + if is_true $START_DAEMON; then + log_daemon_msg "Starting MD monitoring service" "mdadm --monitor" + mkdir -p $RUNDIR + set +e + start-stop-daemon -S -p $PIDFILE -x $MDADM -- \ + --monitor --pid-file $PIDFILE --daemonise --scan ${DAEMON_OPTIONS:-} + log_end_msg $? + set -e + fi + ;; + stop) + if [ -f $PIDFILE ] ; then + log_daemon_msg "Stopping MD monitoring service" "mdadm --monitor" + set +e + start-stop-daemon -K -p $PIDFILE -x $MDADM + rm -f $PIDFILE + log_end_msg $? + set -e + fi + ;; + restart|reload|force-reload) + ${0:-} stop + ${0:-} start + ;; + *) + echo "Usage: ${0:-} {start|stop|restart|reload|force-reload}" >&2 + exit 1 + ;; +esac + +exit 0 --- mdadm-2.6.2.orig/debian/mdadm.postinst +++ mdadm-2.6.2/debian/mdadm.postinst @@ -0,0 +1,192 @@ +#!/bin/sh +# Copyright © 2001-2005 Mario Jou/3en +# Copyright © 2005-2006 Martin F. Krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: mdadm.postinst 314 2007-03-05 11:23:05Z madduck $ +# + +. /usr/share/debconf/confmodule +# See #369953 for ordering +set -eu + +case "${1:-}" in + configure|reconfigure) + + if [ ! -f /proc/mdstat ] && [ -x $(command -v modprobe 2>/dev/null) ]; then + modprobe -k md >/dev/null 2>&1 || : + fi + if [ ! -f /proc/mdstat ]; then + echo 'W: mdadm: failed to load MD subsystem.' >&2 + fi + + if [ ! -e /dev/md15 ] \ + && [ ! -e /dev/.static/dev/md15 ] \ + && [ ! -e /dev/.devfsd ]; then + + echo -n 'Generating array device nodes... ' >&2 + cd /dev + if /sbin/MAKEDEV md >&2 >/dev/null; then + echo 'done.' >&2 + else + echo 'failed.' >&2 + fi + fi + + DEBIANCONFIG=/etc/default/mdadm + CONFIG=/etc/mdadm/mdadm.conf + ALTCONFIG=/etc/mdadm.conf + MDADM=/sbin/mdadm + + if [ -z "${2:-}" ] && [ -s /etc/mdctl/mdctl.conf ] \ + && [ ! -f /etc/mdadm/mdadm.conf ]; then + cp -a /etc/mdctl/mdctl.conf /etc/mdadm/mdadm.conf + fi + + # load current settings, most of which will be overwritten. + [ -f $DEBIANCONFIG ] && . $DEBIANCONFIG + + db_get mdadm/mail_to + MAILADDR="${RET:-root}" + + [ ! -f $CONFIG ] && [ -f $ALTCONFIG ] && CONFIG=$ALTCONFIG + if [ ! -f $CONFIG ]; then + echo -n 'Generating mdadm.conf... ' >&2 + # pass the MAILADDR variable into the script + MDADM_MAILADDR__="$MAILADDR"; export MDADM_MAILADDR__ + if /usr/share/mdadm/mkconf generate $CONFIG 2>/dev/null; then + echo done. >&2 + else + echo "done (failed to scan arrays; /proc probably not mounted)." >&2 + fi + elif dpkg --compare-versions "${2:-2.5.3-1}" le 2.5.3-1; then + # we're upgrading from before 2.5.3-1 and there's apparently already + # a configuration file which we cannot verify. We'll use the sentinel + # during initramfs creation. + md5sum $CONFIG > /var/lib/mdadm/CONF-UNCHECKED + fi + + if [ -w $CONFIG ] && [ -z "${MDADM_MAILADDR__:-}" ]; then + # if the configuration is writeable but has not been written just + # before, then edit it to reflect the MAILADDR preference + if grep -q '^MAILADDR' $CONFIG; then + sed -i -e "s/^MAILADDR.*/MAILADDR $MAILADDR/" $CONFIG + else + echo "MAILADDR $MAILADDR" >> $CONFIG + fi + fi + unset MDADM_MAILADDR__ + + db_get mdadm/initrdstart + INITRDSTART="${RET:-all}" + db_get mdadm/autostart + AUTOSTART="${RET:-true}" + db_get mdadm/autocheck + AUTOCHECK="${RET:-true}" + db_get mdadm/start_daemon + START_DAEMON="${RET:-true}" + #db_get mdadm/daemon_options + [ -n "${DAEMON_OPTIONS:-}" ] || DAEMON_OPTIONS='--syslog' + + cat <<_eof > $DEBIANCONFIG +# mdadm Debian configuration +# +# You can run 'dpkg-reconfigure mdadm' to modify the values in this file, if +# you want. You can also change the values here and changes will be preserved. +# Do note that only the values are preserved; the rest of the file is +# rewritten. +# + +# INITRDSTART: +# list of arrays (or 'all') to start automatically when the initial ramdisk +# loads. This list *must* include the array holding your root filesystem. Use +# 'none' to prevent any array from being started from the initial ramdisk. +INITRDSTART='$INITRDSTART' + +# AUTOSTART: +# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically +# during boot? +AUTOSTART=$AUTOSTART + +# AUTOCHECK: +# should mdadm run periodic redundancy checks over your arrays? See +# /etc/cron.d/mdadm. +AUTOCHECK=$AUTOCHECK + +# START_DAEMON: +# should mdadm start the MD monitoring daemon during boot? +START_DAEMON=$START_DAEMON + +# DAEMON_OPTIONS: +# additional options to pass to the daemon. +DAEMON_OPTIONS="$DAEMON_OPTIONS" + +# VERBOSE: +# if this variable is set to true, mdadm will be a little more verbose e.g. +# when creating the initramfs. +VERBOSE=${VERBOSE:-false} + +# MAIL_TO: +# this variable is now managed in /etc/mdadm/mdadm.conf (MAILADDR). +# Please see mdadm.conf(5). + +# USE_DEPRECATED_MDRUN: +# mdrun is deprecated. If you still want to use it without a warning, set +# the following to true. +# +USE_DEPRECATED_MDRUN=${USE_DEPRECATED_MDRUN:-false} +_eof + + db_stop + + # try to undo udev rules (installed by 2.5.2-10, see 2.5.3.git200608202239-1 + # changelog). Do this before update-initramfs, which copies udev into + # initrd. + V=2.5.3.git200608202239-1~ + if [ "${1:-}" = "configure" ] && [ -n "${2:-}" ] \ + && dpkg --compare-versions $2 ge 2.5.2-10 \ + && dpkg --compare-versions $2 lt $V; then + + # first, disable the rules + rm -f /etc/udev/rules.d/z60_mdadm.rules + + if echo "0843432c9c01ed95c42481eee0cf6fbf /etc/udev/mdadm.rules" \ + | md5sum -c >/dev/null; then + # no changes by user, so remove + rm -f /etc/udev/mdadm.rules + else + echo "W: mdadm: I tried to remove /etc/udev/mdadm.rules (see changelog)," >&2 + echo "W: mdadm: but you have modified it, so I won't touch it. Please" >&2 + echo "W: mdadm: remove the file at your leisure." >&2 + fi + fi + + command -v update-initramfs >/dev/null 2>&1 && update-initramfs -u -k all + ;; +esac + +# remove S04 installed as a fix to #294404 as it does not work +# we only remove the startup links if the previous version was 1.9.0-2.1 (the +# one with the erroneous fix) and the S04 link exists to make sure that +# chances are minimised to overwrite admin changes (even though this would +# not affect woody upgraders) +if [ "${1:-}" = "configure" ] && [ "${2:-}" = "1.9.0-2.1" ] \ + && test -L /etc/rcS.d/S04mdadm-raid; +then + update-rc.d -f mdadm-raid remove +fi + +# See #369953 +set +u +#DEBHELPER# +set -u + +# do start mdadm-raid, but don't use dh_installinit to do so, to prevent +# stopping raids on remove/upgrade. +if [ -x /etc/init.d/mdadm-raid ]; then + if [ -x "$(command -v invoke-rc.d)" ]; then + invoke-rc.d mdadm-raid start || exit $? + else + /etc/init.d/mdadm-raid start || exit $? + fi +fi --- mdadm-2.6.2.orig/debian/rules +++ mdadm-2.6.2/debian/rules @@ -0,0 +1,120 @@ +#!/usr/bin/make -f +# Copyright (C) 2001-2005 Mario Jou/3en +# Copyright (C) 2005-2006 Martin F. Krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: rules 329 2007-05-05 19:32:46Z madduck $ +# + +#export DH_VERBOSE=1 + +CXFLAGS = -ggdb +CXFLAGS_UDEB := $(CXFLAGS) -fomit-frame-pointer +ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) + CXFLAGS += -O0 + CXFLAGS_UDEB += -O0 +else + CXFLAGS += -O2 + CXFLAGS_UDEB += -Os +endif + +include /usr/share/dpatch/dpatch.make + +$(DPATCH_STAMPFN): debian/patches/00list +force-run: +.PHONY: force-run +debian/patches/00list: force-run + dh_testdir + make -sC debian/patches + +.PHONY: configure +configure: debian/patches/00list + +debian/mdadm-startall.8: debian/mdadm-startall.sgml + docbook-to-man $< > $@ + +build: configure patch build-stamp +build-stamp: debian/mdadm-startall.8 + dh_testdir + $(MAKE) -f debian/rules mdadm.udeb DEBIAN=yes + $(MAKE) clean + $(MAKE) -f debian/rules mdadm DEBIAN=yes + touch $@ + +mdadm.udeb: FLAGS = CXFLAGS="$(CXFLAGS_UDEB)" CONFFILE=/tmp/mdadm.conf +mdadm.udeb: configure + dh_testdir + $(MAKE) $(FLAGS) all + mv mdadm mdadm.udeb +.PHONY: mdadm.udeb + +mdadm: FLAGS = CXFLAGS="$(CXFLAGS)" CONFFILE=/etc/mdadm/mdadm.conf CONFFILE2=/etc/mdadm.conf +mdadm: configure + dh_testdir + $(MAKE) $(FLAGS) all +.PHONY: mdadm + +clean: clean-patched unpatch + rm -f debian/patches/00list + +clean-patched: + dh_testdir + dh_testroot + rm -f build-stamp + -$(MAKE) clean + rm -f mdadm.udeb mdadm + dh_clean + debconf-updatepo + +install: DESTDIR=$(CURDIR)/debian/mdadm +install: DESTDIR_UDEB=$(DESTDIR)-udeb +install: build + dh_testdir + dh_clean -k + dh_installdirs + install -m0755 mdadm $(DESTDIR)/sbin + install -m0755 debian/mdrun $(DESTDIR)/sbin + + install -m0755 mdadm.udeb $(DESTDIR_UDEB)/sbin/mdadm + install -m0755 debian/mdrun $(DESTDIR_UDEB)/sbin + + install -m0755 debian/initramfs/hook \ + $(DESTDIR)/usr/share/initramfs-tools/hooks/mdadm + install -m0755 debian/initramfs/script.local-top \ + $(DESTDIR)/usr/share/initramfs-tools/scripts/local-top/mdadm + + install -m0755 debian/mkconf $(DESTDIR)/usr/share/mdadm + install -m0755 debian/checkarray $(DESTDIR)/usr/share/mdadm + install -m0755 debian/bugscript $(DESTDIR)/usr/share/bug/mdadm/script + + install -m0755 debian/mdadm-startall $(DESTDIR)/sbin + + install -m0644 debian/mdadm.lintian-overrides \ + $(DESTDIR)/usr/share/lintian/overrides/mdadm + +binary-indep: build install + +binary-arch: build install + dh_testdir + dh_testroot + dh_installdebconf + dh_installdocs + dh_installexamples + dh_installinit --init-script=mdadm-raid --no-start -- start 25 S . start 50 0 6 . + dh_installinit -- defaults 25 + dh_installman + dh_installcron + dh_installchangelogs ChangeLog + dh_installlogcheck + dh_link + dh_strip + dh_compress + dh_fixperms + dh_installdeb + dh_shlibdeps + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch +.PHONY: build clean binary-indep binary-arch binary install configure --- mdadm-2.6.2.orig/debian/mdadm-startall +++ mdadm-2.6.2/debian/mdadm-startall @@ -0,0 +1,34 @@ +#!/bin/sh +# +# startall -- starts all existing arrays after creating mdadm.conf +# overrides the AUTOSTART variable in /etc/default/mdadm +# +# Copyright © martin f. krafft +# distributed under the terms of the Artistic Licence 2.0 +# +# $Id: mdadm-startall 325 2007-05-05 18:57:20Z madduck $ +# + +set -eu + +CONFIG=/etc/mdadm/mdadm.conf +ALTCONFIG=/etc/mdadm.conf + +modprobe -kq md 2>/dev/null || : + +[ ! -f $CONFIG ] && [ -f $ALTCONFIG ] && CONFIG=$ALTCONFIG + +if ! grep -q '^ARRAY' $CONFIG 2>/dev/null; then + /usr/share/mdadm/mkconf force-generate || ret=$? + case ${ret:-0} in + 0) :;; + *) + echo E: mdadm: mdadm.conf creation failed, aborting. >&2 + exit $ret + ;; + esac +else + echo W: mdadm: using ARRAYs defined in existing mdadm.conf. >&2 +fi + +MDADM_FORCE_AUTOSTART__=1 exec /etc/init.d/mdadm-raid start --- mdadm-2.6.2.orig/debian/changelog +++ mdadm-2.6.2/debian/changelog @@ -0,0 +1,1076 @@ +mdadm (2.6.2-1~bpo.1) etch-backports; urgency=low + + * Rebuilt for etch. + + -- martin f. krafft Thu, 7 Jun 2007 08:52:47 +0200 + +mdadm (2.6.2-1) unstable; urgency=low + + * New upstream release + - new options --fail detach and --remove faulty can be used to fail and + remove devices that are no longer physically present (closes: #416512). + - --help output now goes to stdout (closes: #416653). + - plenty of manpage fixes, thanks Peter Samuelson (closes: #414688). + * Incorporated patch by Mikko Rasa to fix detecting of raid6 (and raid10) + devices with --scan (closes: #421915). + + -- martin f. krafft Mon, 21 May 2007 14:25:43 +0200 + +mdadm (2.6.1-1) unstable; urgency=low + + * Release to unstable. + * Start arrays read-only in initramfs to prevent syncing and hence enable + resuming/freezing. The arrays will automatically sync as soon something + writes to it; thanks to Tim Dijkstra, Neil Brown, and Luis Rodrigo + Gallardo Cruz (closes: #415441). + * mkconf now tries to preserve existing values for DEVICE, CREATE and + HOMEHOST (in addition to MAILADDR, which it preserved previously already). + PROGRAM is preserved but only added to mdadm.conf if it occured in the + previously existing configuration file. + * startall is now mdadm-startall and lives in /sbin, thanks to Eduard Bloch. + It now can handle existing mdadm.conf files much more gracefully, mostly + thanks to the above mkconf enhancements (closes: #415336). + + -- martin f. krafft Sat, 05 May 2007 16:12:29 +0200 + +mdadm (2.6.1-1~exp.5) experimental; urgency=low + + * Fix mdadm.conf typo; thanks Tim Phipps (closes: #416626). + * Execute udevtrigger after assembly of arrays during initramfs processing; + thanks to Michael Prokop (closes: #416658). + + -- martin f. krafft Sat, 31 Mar 2007 12:12:27 +0200 + +mdadm (2.6.1-1~exp.4) experimental; urgency=low + + * Incorporate patches by Peter Samuelson fixing several typography as well + as typesetting issues in the manpages. Thanks a lot! (closes: #414688) + + -- martin f. krafft Tue, 13 Mar 2007 19:26:37 +0100 + +mdadm (2.6.1-1~exp.3) experimental; urgency=low + + * Patch by Jørn V. Christensen to properly handle multiple email addresses + for the MAILADDR setting (closes: #413330). + + -- martin f. krafft Mon, 5 Mar 2007 11:19:18 +0000 + +mdadm (2.6.1-1~exp.2) experimental; urgency=low + + * Updated debconf translations: + - Galician by Jacobo Tarrio (closes: #412203). + + -- martin f. krafft Sat, 24 Feb 2007 16:41:16 +0100 + +mdadm (2.6.1-1~exp.1) experimental; urgency=low + + * New upstream release, targeted at experimental until etch is out: + - adds --syslog option (closes: #402457). + - now can --wait for sync activity to finish (closes: #328197). + - for other changes, please see /usr/share/doc/mdadm/changelog.gz + * Updated debconf translations: + - Portuguese by Rui Branco (closes: #411745). + + -- martin f. krafft Thu, 22 Feb 2007 16:35:16 +0100 + +mdadm (2.5.6-9) UNRELEASED; urgency=low + + * More logcheck filters to prevent redundant information logged by mdadm + --syslog. + * Improved mdadm-raid init script to correctly output status information for + drives that are initialising or adding spares. + + -- martin f. krafft Thu, 11 Jan 2007 16:05:12 +0100 + +mdadm (2.5.6-8) unstable; urgency=low + + * Hard-code path to /sbin/mdadm binary rather than searching the $PATH. This + closes: #403307 and should be a little more robust in the presence of + installations of mdadm in /usr/local. + * Made the bugscript a little more failure-resilient. + * Added more documentation. + + -- martin f. krafft Mon, 8 Jan 2007 02:04:25 +0100 + +mdadm (2.5.6-7) unstable; urgency=low + + * Only parse ARRAY lines from configuration file when collecting the array + pairs. Thanks to Daniel Dehennin for the bug report and suggested fix + (closes: #402106). + * Prevent modules from being loaded during initramfs time if no arrays are + to be assembled at this stage. + * Export DAEMON_OPTIONS to /etc/default/mdadm, which gets passed to the + mdadm daemon on startup from the init.d script. The value is set to + -y/--syslog by default, and will get incorporated into debconf in a future + version; thanks for the idea by Alex Owen (closes: #401696). + * Incorporate patch by upstream to fix handling of --syslog long option + (closes: #402457). + * Added logcheck filters for new syslog entries by mdadm monitoring daemon. + * Added Spanish debconf translation by Javier Fernández-Sanguino + (closes: #402681). + + -- martin f. krafft Tue, 12 Dec 2006 11:49:52 +0100 + +mdadm (2.5.6-6) unstable; urgency=medium + + * Fixed a typo in the debconf control script which would cause failures with + a dash shell; thanks to Santiago Garcia Mantinan for reporting this, and + Andreas Metzeler for providing a solution (closes: #399315). + + -- martin f. krafft Mon, 20 Nov 2006 15:02:34 +0800 + +mdadm (2.5.6-5) unstable; urgency=low + + * Prevent initramfs hook from exiting prematurely when VERBOSE=false. + * Moved debconf question about arrays to start by initramfs to high + priority. + + -- martin f. krafft Mon, 13 Nov 2006 11:24:21 +0100 + +mdadm (2.5.6-4) unstable; urgency=low + + * Actually remove mdadm.conf on purge; previously, the generation of + a temporary file for initramfs would screw up the purging; thanks to + Fabrice Lorrain for the report (closes: #398088). + + -- martin f. krafft Sat, 11 Nov 2006 20:07:55 +0100 + +mdadm (2.5.6-3) unstable; urgency=low + + * Fix a syntax error in mdadm-raid script. + + -- martin f. krafft Thu, 9 Nov 2006 15:47:51 +0100 + +mdadm (2.5.6-2) unstable; urgency=low + + * Small fixes to mkconf, now returns 255 instead of -1. + * Added /usr/share/mdadm/startall, a helper script to facilitate starting + all arrays when booting from rescue/live media. It overrides AUTOSTART in + /etc/default/mdadm and starts arrays even if the variable is set to + a false value. + + -- martin f. krafft Thu, 9 Nov 2006 14:44:35 +0100 + +mdadm (2.5.6-1) unstable; urgency=low + + * New upstream release: + - added note to mdadm(8)/--metadata about overriding the default in + mdadm.conf (closes: #396914). + - fixed problems that could cause infinite loop with auto assemble. Thanks + to Dan Pascu for pointing this out (closes: #396582). + - fixed problems with bitmap file names lost after reading from + configuration file. + * Merged patch by Dan Pascu to nicely handle situations where a degraded + array only has one drive left nicely by the mdadm-raid script. + * Updated Japanese debconf translation; thanks to Hideki Yamane + (closes: #396400). + + -- martin f. krafft Thu, 9 Nov 2006 00:47:45 +0100 + +mdadm (2.5.5-1) unstable; urgency=low + + * New upstream release: + - fixes the build problems on several architectures (closes: #393314) by + including the contents of linux/blkpg.h literally, not via #include. + - optimises bitmap file use on 64bit systems. + - does not error out anymore when trying to assemble an already assembled + array without a corresponding /dev device node. + - does not report an error if --assemble --scan only finds already running + arrays. + - fixes several bugs related to RAID10 and the new offset layout. + - improves error message when a wrong '--update' option is given. + * Added FAQ entries about partitionable arrays. + * chroot detection now also works for 2.6.18 and beyond (c.f. kernel commit + 778c1144771f0064b6f51bee865cceb0d996f2f9). + * Now recommends module-init-tools. + * Hides ugly errors during configuration in the absense of module-init-tools + or initramfs-tools. + * Send udev events for arrays assembled by the mdadm-raid init.d script. + This does not close #394193 but it's a good addition anyway. I am not + sending these events from the initramfs as well because it would be + non-trivial to ensure that an event doesn't get sent twice for a given + array. + Anyway, this is all a hack until the kernel sends online/offline events to + udev. See #394193. + * Added more RAID10 information to the FAQ. + * Added filters to logcheck for regular events, even by the md driver; also + promoted messages about non-fresh components to security events. + * Hide informational messages unless VERBOSE is set to a true value in + /etc/default/mdadm. + + -- martin f. krafft Thu, 26 Oct 2006 22:35:24 +0200 + +mdadm (2.5.4-1) unstable; urgency=low + + * New upstream release: + - --examine now reports chunk size also for RAID6 and RAID10 + - fix endianness issues with v1 superblocks (closes: #385726) and bitmap + metadata. + - improved message when mdadm detects similar superblocks + (closes: #385951). + - documents that the automatic update of the super-minor field in the + superblock when using a 2.6 kernel only applies to RAID levels 1 and + higher. RAID0 array superblocks must be manually updated + (closes: #386315, #388172). + - removes partition table from any whole device added to an array. + - allow --auto=yes to specify a number; if mdadm determines from the + device name that you want a partitionable array, this number determines + the number of sub-device nodes to create. + * Removed patch previously used to fix #385951 because it's not adequate. + See the bug log for reasons. + + -- martin f. krafft Fri, 13 Oct 2006 08:32:20 +0200 + +mdadm (2.5.3.git200608202239-8) unstable; urgency=low + + * This revision is dedicated to Peter Samuelson for his RAID10 expertise^W + educated guess^W^W pure luck. (: + * Now writes minimal mdadm.conf file even if the MD subsystem has not been + loaded and the scan for arrays thus failed. + * Now tries to ensure that the configuration file used for the initramfs + actually defines arrays. + * Now preserves MAILADDR from an existing mdadm.conf when generating a new + one. + * Documentation updates. + * Updated debconf translations: + - German by Mario Joußen. + - Vietnamese by Clytie Siddall (closes: #390311). + - Dutch by Frans Pop (closes: #390955). + - French by Jean-Luc Coulon (closes: #391215). + + -- martin f. krafft Fri, 6 Oct 2006 15:03:46 +0200 + +mdadm (2.5.3.git200608202239-7) unstable; urgency=medium + + * Fixed a serious bug in the debconf script which would cause the + configuration to exit prematurely in cases when the root could not be + determined. Since this is RC, the urgency is set to medium. + * Updated the documentation a bit. + * Updated debconf translations: + - Swedish by Daniel Nylander (closes: #389040). + - Czech by Miroslav Kure (closes: #389083). + - Russian by Yuri Kozlov (closes: #389086). + - Brazilian Portuguese by Felipe Augusto. + + -- martin f. krafft Fri, 29 Sep 2006 16:31:44 +0200 + +mdadm (2.5.3.git200608202239-6) unstable; urgency=high + + * Bumping urgency to high because previous version has been in unstable for + three days and this one really only fixes a stupid segfault: + * Reworked the parsing of /proc/partitions and spotted a mean segfault + (closes: #388355). + + -- martin f. krafft Thu, 21 Sep 2006 15:25:21 +0200 + +mdadm (2.5.3.git200608202239-5) unstable; urgency=medium + + * Keeping medium urgency due to RC bug. + * Modified the patch responsible for pruning parent devices so that + superblocks at the end of a disk do not get interpreted twice. It now + makes less assumptions about the exact output of /proc/partitions and + should thus be more robust (now closes: #385951). + * Added code that defers mdadm preconfiguration when the debconf backend is + too old (and does not provide debconf-escape). Now configuration is + postponed until the postinst is run in this case. + + -- martin f. krafft Thu, 14 Sep 2006 11:16:39 +0200 + +mdadm (2.5.3.git200608202239-4) unstable; urgency=medium + + * Correct error related to an unbound variable in postinst. + * Keeping medium urgency. + + -- martin f. krafft Wed, 13 Sep 2006 20:49:33 +0200 + +mdadm (2.5.3.git200608202239-3) unstable; urgency=medium + + * Urgency medium because of RC bugs. + * Add versioned dependency to debconf (closes: #385994); temporary fix until + we find a proper fix for #386439. + * Add patch by Steinar H. Gunderson to ensure mdadm does not interpret + a superblock as belonging to a device when it's actually part of + a partition on that device (closes: #385951). + * Do not override the superblock default version in mdadm.conf to prevent + creation of superblocks that the kernel can't handle (closes: #384614). + * Added a note to alert people that the warning about arrays not listed in + the configuration file is only relevant if the arrays are needed to be + brought up by mdadm from initramfs during boot (closes: #385017). + * Added bootloader/cmdline info to bugscript so that future bug reports via + bug/reportbug include information on how the system is booted with respect + to RAID (the root partition). + * If mdadm is being configured in a chroot, it now defaults to starting all + arrays from the initial ramdisk, rather than trying to figure out the root + MD array (we're using /proc information, so it would be the one of the + host, not the one of the chroot) (closes: #386468). + * Added LSB headers to init scripts. + * Reworked the documentation with respect to the use of "MD" and "RAID", and + added a FAQ entry on the meaning of "MD". Thanks to Frans Pop for his + help! + * Updated debconf translations: + - Czech by Miroslav Kure (closes: #384754). + - French by Florentin Duneau (closes: #385690). + - Russian by Yuri Kozlov (closes: #387017). + + -- martin f. krafft Thu, 7 Sep 2006 14:32:04 +0200 + +mdadm (2.5.3.git200608202239-2) unstable; urgency=low + + * Allow ARRAY lines in configuration file to break across lines + (closes: #384222). + * Improved initramfs hook; now does not rely on initramfs to provide RAID + assembly: + - if a checked mdadm.conf file is present, use that. + - if an unchecked mdadm.conf is present, create a temporary one + - if that fails, use the unchecked one iff it contains at least one + ARRAY statement. Otherwise rely on auto-generation from the initramfs + during the book (and hope for the best). + - if no mdadm.conf is found, create one on the fly + - if that fails, hope that the auto-generation will work during boot + * Improved the messages printed by the initramfs script. + * Do not store the debconf answer for whether arrays not listed in the + configuration file should be used. + * Now asks again for the devices to start (preseeded with 'all') if the user + does not want to proceed with devices not listed in the configuration + file. + + -- martin f. krafft Wed, 30 Aug 2006 16:29:07 +0200 + +mdadm (2.5.3.git200608202239-1) unstable; urgency=low + + * Tracking upstream git releases. + - now the --run switch behaves as stated in the manpage. This properly + fixes #287415 + - new version-1 partitionable arrays are now named X instead of _dX (e.g. + 0 instead of _d0) for device names like md_dX. I actually think this is + a bug and hope upstream will use dX (e.g. d0) instead in a future + version. + - we specify --symlink=no and thus disable the new feature to create + /dev/mdX symlinks to /dev/md/X devices until the entire device node mess + is cleared up. No need to introduce yet another complicating factor at + this stage. + * Instead of trying to do a whole lot of magic with respect to detecting + RAID devices to start, mdadm from now on requires a valid mdadm.conf file + to be installed. It still tries to do what it can, but there are no + heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 . + * Removed the zero-superblock warning because we require the user to sign + off the configuration file anyway. + * This also enables us to use mdadm.conf from the initial ramdisk and thus + closes: #381303. + * In case the user chooses to assemble all arrays from the initial ramdisk, + use the new homehost feature of mdadm (closes: #381057). This will start + only those arrays belonging to the local system, unless it is the first + run on a system, in which case it will start all arrays and mark them as + belonging to the local system. + * Improved the debconf control script: integrated error messages into the + frontends, and made it a bit smarter. Error messages can now be + translated, and the script checks whether the user's choice is listed in + the configuration file and only proceeds if it is, or the user chooses to + ignore that it is not. + * mkconf can now take a generate/force-generate parameter to write directly + to /etc/mdadm/mdadm.conf. A second parameter specifies an alternate + filename. + * mkconf now outputs comments for the settings it suggests. + * Removed all udev-related stuff. We must coexist with udev because there + are setups that assemble arrays without mdadm, so the device nodes must be + created by udev, if that is used. + (closes: #382263, #382450, #383688, #383891, #383806, #382480) + Staying at low urgency since these (RC) bugs only exist in unstable. + * Now installs MD modules and mdadm/mdrun into initial ramdisk regardless of + whether the hook script thinks there are devices to start. This was done + to enable recovery from the initramfs shell. + * Now uses 'MD' instead of 'RAID' consistently in all messages. + * Now rebuilds initramfs for all installed kernels. + * Now breaks the endless config loop only when the user does not see the + question (see #381284, #381007). + * Don't fail mdadm-raid when /dev is on a read-only filesystem + (closes: #382876). + * Updated debconf translations: + - French by Florentin Duneau (closes: #382389). + + -- martin f. krafft Mon, 21 Aug 2006 00:25:22 +0100 + +mdadm (2.5.2-10) unstable; urgency=low + + * Applied patch by upstream to fix the logic of the --run switch (see + #287415). Thus also reverted the mdadm-raid hack used to fix the bug in + the 2.5.2-9 upload. + * Recognise devfs-style device nodes by fixing a regression bug in the root + RAID autodetection code (closes: #381007), which was introduced as part of + the fix for #380596 in the 2.5.2-9 upload. The bug is RC, but it only + applies to unstable right now, so I am not pumping up the urgency. + The autodetection code now doesn't care about the actual name of the array + device, but instead only insists that it exists, is a block device, and + recognised as an array by mdadm (mdadm --detail). + * Added safety net to prevent endless loops in RAID autodetection. Now just + falls back to starting all arrays from the initramfs if it fails to + determine an acceptable array for the / filesystem in three tries + (closes: #381284, also see #381007). + * Added udev rules file to prevent udev from ever creating md device nodes, + which can get in the way of mdadm (also see next item). + * Added a workaround to the initramfs hook to deal with the problem with + /dev/md/X device nodes when /dev/mdX is also present and version-0 + superblocks are in use (closes: #381181). + * checkarray: correctly recognise when the kernel is too old for parity + checks, or when there are no redundant arrays present (closes: #380746). + * checkarray: now supports -s|--status switch to query parity check status + for given devices. + * checkarray: now supports -x|--cancel switch to cancel running checks. + * mkconf: now also outputs 'MAILADDR root' and 'HOMEHOST '. + * Added README.checkarray with some information about the check process. + * Added /usr/share/doc/mdadm/FAQ to answer some FAQs. + + -- martin f. krafft Thu, 3 Aug 2006 22:54:04 +0100 + +mdadm (2.5.2-9) unstable; urgency=low + + * Added logcheck rules for kernel messages generated by checkarray, using + logcheck server level. + * Added handling of partitionable arrays to root RAID autodetection script + (closes: #380596). + * Forcing RAID assembly to run the arrays, working around an upstream bug + until that's fixed (closes: #287415). + * Updated documentation in README.initramfs-transition to include + information related to #380089. + * Updated debconf translations: + - Vietnamese by Clytie Syddall, thanks! + + -- martin f. krafft Mon, 31 Jul 2006 14:35:38 +0100 + +mdadm (2.5.2-8) unstable; urgency=low + + * Re-added rootraiddoc.97.html which was mysteriously lost (closes: #378678). + * Catching modprobe error in case of absence of the kernel modules, or + a non-modular kernel. Thanks to Holger Levsen. + * Copy raid456 kernel module into initramfs, if present (closes: #380152). + * checkarray: check for presence of active RAID arrays and give an + appropriate error if there are none present (closes: #379019). + * checkarray: skip sync for non-redundant devices (closes: #379352, #380424). + * Fixing cron registration for checkarray. crontab(5) is really stupid and + makes me think that they simply documented a bug instead of fixing it, so + now I have to hack around it. See the cron.d file (closes: #380425). + * Removed the code writing auto-detected devices to /var, which was silly + since /var isn't necessarily mounted yet by the time mdadm-raid is called. + Thanks to Maurizio Avogadro for pointing this out. + * Add reference to BAARF to README.Debian and included the RAID5 vs RAID10 + article from the BAARF website. + * Updated debconf translations: + - Japanese by Hideki Yamane, thanks! + - French by Florentin Duneau, thanks! (closes: #379511) + + -- martin f. krafft Thu, 27 Jul 2006 22:49:32 +0100 + +mdadm (2.5.2-7) unstable; urgency=low + + * Release to unstable. + + -- martin f. krafft Thu, 20 Jul 2006 17:23:23 +0100 + +mdadm (2.5.2-6) experimental; urgency=low + + * Adding mdrun to generated udeb. I will only remove mdrun after etch. + * Updated debconf translations: + - Dutch, thanks to Frans "Franzerl" Pop! (closes: #377412) + - French, thanks to Florentin Duneau! (closes: #377968) + + -- martin f. krafft Thu, 13 Jul 2006 23:11:24 +0200 + +mdadm (2.5.2-5) UNRELEASED; urgency=low + + * Remove the check for the lvm prereq in the initramfs hook, as #369617 is + now fixed. Thus conflicts against initramfs-tools (<< 0.65). + * Updated debconf translations: + - German, thanks to Mario Joußen! + * Added short note about maintenance in SVN to README.Debian. + + -- martin f. krafft Thu, 13 Jul 2006 23:10:36 +0200 + +mdadm (2.5.2-4) UNRELEASED; urgency=low + + * The "it takes two to swing" release. + * Now does not stop arrays on upgrade or remove. Thanks (and sorry) to + Christian Pernegger (and hopefully no others). + * Fixed small problem in debconf configuration script related to unbound + MAIL_TO variable. Thanks to Christian Pernegger. + + -- martin f. krafft Fri, 7 Jul 2006 16:59:01 +0200 + +mdadm (2.5.2-3) UNRELEASED; urgency=low + + * The initramfs now gets all RAID modules installed. It's a lot safer to + have them all around, the size difference is negligible, and we still only + load the needed ones at boot time. + * Added /usr/share/mdadm/checkarray, which can be used to check arrays for + parity. Also added a debconf question to let the user choose whether + cron should run these checks (closes: #377071). + * Only shut down arrays automatically when they've been automatically + started (closes: #376009). + * Make sure the user has a chance to choose the autostart feature by + elevating the debconf priority to high (see #376009). The warning about + reuse of RAID components has also been elevated to debconf priority high. + * The MAIL_TO setting from /etc/default/mdadm has been removed. Instead, use + MAILADDR in /etc/mdadm/mdadm.conf. See mdadm.conf(5). Your setting should + be automatically migrated. + * Now rewrites /etc/default/mdadm (but preserves settings) instead of trying + to patch it with changes. + * Added note to README.Debian to ensure users know that only the devices + listed in mdadm.conf will be autostarted (see #376009). + * Now includes latest md.txt from kernel documentation in + /usr/share/doc/mdadm/md.txt.gz. + * Added some more recipes to /usr/share/doc/mdadm/README.recipes.gz. + * Updated debconf translations: + - Swedish, thanks to Daniel Nylander! + - Brazilian Portuguese, thanks to Felipe Augusto van de Wiel! + - Czech, thanks to Miroslav Kure! + - Russian, thanks to Yuri Kozlov (closes: #376181). + * Further updates to the debconf templates; I hope the translators aren't + going to kill me. + + -- martin f. krafft Fri, 7 Jul 2006 15:09:40 +0200 + +mdadm (2.5.2-2) experimental; urgency=low + + * The "if it weren't for Munich's wheat beer, there'd be no" release. + * Removed -fno-strict-aliasing from compiler options, after upstream fixed + the bug that led to its use (see #369779, #356153). Thanks to Elimar + Riesebieter for pointing this out (closes: #375876). + * Moved detection of RAID devices from initramfs hook to debconf control + file, and added a (low-priority) debconf question as to which devices + should be started early in the boot sequence. For the cases where we + failed to auto-detect previously (e.g. root on LVM on RAID), it's paranoid + and suggests to start them all (closes: #375879). Thanks to Alec Berryman + for spotting this. + * Fixed a typo in README.experimental, which could lead to an unbootable + system with initramfs-tools 0.64 or before. Again, thanks to Alec for + spotting this. + * Extended bug script to include --examine output for all components (at + least if called by root, which hopefully should never happen. Err, + wait...) + * Disabled deprecation warning in mdrun until the transition is complete. + * Reworded the debconf templates due to a new question, and also for + readability. + + -- martin f. krafft Thu, 29 Jun 2006 22:54:47 +0200 + +mdadm (2.5.2-1) experimental; urgency=low + + * New upstream release. + * Implemented checks in the initramfs hooks and scripts for compatibility + with initramfs-tools. Now we do not need a conflict anymore because + mdadm's hooks and scripts will simply do nothing while the ones provided + by initramfs-tools are still present. + * Not using /bin/bash for mdrun, which I thought we'd need for read timeout + support (for the deprecation warning). Since the -n and -t flags to the + read shell builtin are non-POSIX, I dropped them, they were merely + cosmetic anyway. + + -- martin f. krafft Tue, 27 Jun 2006 15:06:55 +0200 + +mdadm (2.5.1-2) experimental; urgency=low + + * Updating dependency on initramfs-tools, which has not yet adopted to mdadm + taking over the hooks. + + -- martin f. krafft Mon, 26 Jun 2006 22:35:08 +0200 + +mdadm (2.5.1-1) experimental; urgency=low + + * New upstream release: + - Really fixes return status of examine (closes: #367901). + - Fixes a memory leak in monitor mode (closes: #372618). + - Fixes compiler warnings and errors (closes: #373802, #356153, #369779). + - Fix byte swapping issues (closes: #369765). + - Now lists devices it stops (closes: #369850). This also leads to + beautification of the init.d script's stop action. + * Fixed RAID init script to not complain about missing logger command. + + -- martin f. krafft Mon, 26 Jun 2006 00:58:36 +0200 + +mdadm (2.5-4) experimental; urgency=low + + * The "would you like fries with your parasite?" release. + * Now does not require RAID support from the kernel just for package + installation; that was silly of me, sorry (closes: Bug#370115). + * Added version to Replaces: initramfs-tools dependency. + * Further init.d script improvements. + * Recommends mail-transport-agent, or the monitor daemon won't be able to + send anything. + * Ignores failures from modprobe in postinst when RAID modules are not + available (closes: #370582). + + -- martin f. krafft Tue, 6 Jun 2006 12:45:53 +0200 + +mdadm (2.5-3) experimental; urgency=low + + * Added /usr/share/doc/mdadm/README.recipes with some common usage examples. + * Vastly improved the mdadm-raid init.d script output, and removed bashisms. + + -- martin f. krafft Fri, 2 Jun 2006 00:45:06 +0200 + +mdadm (2.5-2) experimental; urgency=low + + * The "on her majesty's secret service" release. + * Enabled -DDEBIAN during build, which will take care of default permissions + on devices created by mdadm. Together with the CREATE configuration + directive in 2.5, this now certainly closes: Bug#310241. + * Added a patch (incorporating lib/mm/xlate.h from lvm2) to prevent direct + access to kernel headers from userspace (closes: Bug#369765). + * Disabled strict aliasing compiler checks until we find a better + implementation for linked lists in C (closes: Bug#369779, Bug#356153). + * Actually decreased the size of the udeb mdadm binary with -Os + -fomit-frame-pointer (as suggested by Joey Hess) (closes: Bug#314370) + * Added Replaces: initramfs-tools to communicate that we're not conflicting + but replacing instead (see Bug#367567) + * Updated conflict with initramfs-tools to (<< 0.63) per suggestion by the + maintainers. + + -- martin f. krafft Thu, 1 Jun 2006 20:15:17 +0200 + +mdadm (2.5-1) experimental; urgency=low + + * The "show me the way to the next whiskey bar" release. + * See /usr/share/doc/mdadm/README.experimental or + http://madduck.net/~madduck/scratch/README.experimental + * New upstream release: + - mails include /proc/mdstat output (closes: Bug#355882) + - allows specification of device permissions in config (closes: Bug#310241) + * /sbin/mdrun has been deprecated and replaced by calls to /sbin/mdadm; + a proper deprecation warning is in place (see NEWS). + * Moved initramfs hook and script into the package, and switched it to mdadm + (from mdadm. Thanks to Stephen Frost for his help (closes: Bug#354144). + This should make sure that the right minor numbers are chosen during boot + (mainly because mdadm takes care of it all) (closes: Bug#361408). + * Removing mdrun from the udeb (d-i patch submitted to debian-boot mailing + list) + * Upstream links against openssl for SHA1 support (homehost feature), which + is a problem. An internal SHA1 implementation is provided, however, so + I just link against that. + * Switched init.d scripts to use LSB-compliant output. + * Enhanced init.d script output. + + -- martin f. krafft Thu, 1 Jun 2006 02:20:22 +0200 + +mdadm (2.4.1-2) unstable; urgency=low + + * The "this took way longer than I thought" release. + * Migrating to unstable. + * If the init.d script creates the mdadm.conf file, it should remove it on + purge. To accomplish this, I create a semaphore in /var/lib/mdadm if it + was generated, and only remove the conffile on purge if the semaphore + exists. + * Added a little helper /usr/share/mdadm/mkconf to aid generation of + configuration file. + * Added a bug script to collect some important information when the user + uses Debian bug reporting tools (such as reportbug). + * Added a debian/watch file. + + -- martin f. krafft Wed, 31 May 2006 23:07:48 +0200 + +mdadm (2.4.1-1) experimental; urgency=low + + * The "I'll kill that maintainer... uh, wait, it's me" release. Sorry for + the delay, here's the long awaited new upstream release (closes: + Bug#337903, Bug#363592), which gets rid of a bunch of functionality bugs: + - reiserfs size does not overflow anymore (closes: Bug#318230) + - fixed typos in manpages (closes: Bug#352798) + Oh, and we're moving away from that arch nightmare too. Sorry for the + confusion. + * Experimental release, because I really don't want to be responsible for + data loss. Though I am quite sure that the upgrade is painless, I also + don't have access to 18 drive RAID 10 with multipath on s390 or similar + arrangements. + * We now make the /dev/md* devices in postinst unless /dev/md15 exists (no + longer checking for /dev/md0), or unless devfs is in use. If udev is used, + /dev/md15 will only exist in complex setups, so the devices will be made + in /dev/.static by MAKEDEV, which is not really a concern. I opted against + unconditionally calling MAKEDEV until #367407 is fixed so as to preserve + custom permissions or owner settings. This also acknowledges the NMU + (#299623). + closes: Bug#310247, Bug#299623 + * Patched some of the code to make mdadm honour /etc/mdadm/mdadm.conf over + /etc/mdadm.conf (see NEWS). + * Fixed a couple of typos in the mdadm(8) manpage; thanks to Reuben Thomas. + closes: Bug#345669, Bug#345667 + * Pushed Standards-Version to 3.7.2; no changes required. + * Updated Debconf translations: + - Vietnamese by Clytie Siddall (closes: Bug#323950) + - Czech by Miroslav Kure (closes: Bug#360290) + - Russian by Yuri Kozlov (closes: Bug#361116) + - French by Eric Madesclair (closes: Bug#323988) + * Added new Debconf translations: + - Swedish by Daniel Nylander (closes: Bug#333486) + - Dutch by Frans Pop (closes: Bug#344714) + + -- martin f. krafft Tue, 16 May 2006 18:21:36 -0500 + +mdadm (1.12.0-1) unstable; urgency=low + + * New upstream release. + (obsoletes branches: symlinks) + (reduces branches: gcc4signedness, debian, autoscan) + * Fixed typo in mdadm.conf(5) manpage (closes: Bug#321152). + + -- martin f. krafft Sun, 24 Jul 2005 19:20:01 +0200 + +mdadm (1.9.0-5) unstable; urgency=low + + * martin f. krafft: (the, "look ma', we're maintained in arch now!" release) + (no functional differences except for added/updated translations) + - Acknowledge NMU by Steve Langasek; thanks! (closes: Bug#299623) + - split diff.gz into different arch branches (see debian/arch-branches). + - debian/control: + - Changed maintainer to pkg-mdadm-devel. + - Reworded some of the descriptions (closes: Bug#304170). + - Pushed Standards-Version to 3.6.2.1; no changes needed. + - fixed po-debconf integration + - debian/rules: + - fixed po-debconf integration + - l10n changes: + - Removed amiguity from debconf template (closes: Bug#312754). + - Added Vietnamese debconf translation; thanks to Clytie Siddall! + (closes: Bug#312753) + - Added Czech debconf translation; thanks to Miroslav Kure! (closes: Bug#319626) + - Updated German debconf translation; thanks to Jens Seidel! (closes: Bug#313981) + - backported upstream's gcc4 signedness fixes from 1.12.0 (gcc4signedness + branch) (closes: Bug#319743). + + -- martin f. krafft Sun, 24 Jul 2005 17:58:46 +0200 + +mdadm (1.9.0-4.1) unstable; urgency=high + + * Non-maintainer upload. + * High-urgency upload for sarge-targetted RC bugfix + * Make sure error output from MAKEDEV is sent to stderr, to avoid + interfering with debconf; this avoids installation problems on + udev-using systems. Thanks to Jonas Smedegaard for the patch. + Closes: #299623. + + -- Steve Langasek Wed, 1 Jun 2005 03:36:42 -0700 + +mdadm (1.9.0-4) unstable; urgency=high + + * High-urgency upload for sarge targeted RC bugfix. + * mdrun: replaced invocation of /usr/bin/seq with hard-coded sequence + (closes: Bug#310671). + + -- martin f. krafft Wed, 25 May 2005 09:51:41 +0200 + +mdadm (1.9.0-3) unstable; urgency=high + + * High-urgency upload for sarge targeted RC bugfix. + * Applied patch by Peter Samuelson , which causes mdadm to + follow symlinks of device nodes (closes: #274859, #310412, #310492). + * Added myself as co-maintainer as per agreement with Mario Joussen. + + -- martin f. krafft Tue, 24 May 2005 00:03:49 +0200 + +mdadm (1.9.0-2.3) unstable; urgency=high + + * Non-maintainer upload. + * Do not prevent postinst node creation when udev is being used; MAKEDEV + puts files into /dev/.static/dev with udev, which is needed so that device + nodes will be there even if udev is removed. Sorry for letting this slip + my mind and thanks to Steve Langasek for spotting this error. + * Leaving urgency at high to make sarge. + + -- martin f. krafft Sun, 22 May 2005 19:35:04 +0200 + +mdadm (1.9.0-2.2) unstable; urgency=high + + * Non-maintainer upload. + * High-urgency upload for sarge targeted RC bugfix. + * Move mdadm-raid back to S25 as it needs to run after modules have been + loaded at S20 (see followups to #294404, #301560). + * Verified that Steve Langasek's patch to config.c (see item 4 of the + 1.9.0-2.1 changelog) is necessary for `mdadm -A -s` to work. + (closes: #301560) + * Integrated patch by Erik van Konijnenburg to fix mdadm's --auto + option in the presence of --scan. + (closes: #294404, #273182, #284028, #310126). + * Modified mdrun to call mdadm with --auto in assembly mode. Removed code + which would auto-create 24 device nodes during system startup when udev + was used. + * Fixed next_free_md function in mdrun to iterate all 24 nodes instead of + using some fragile shell globbing, which did not work anyway. + * Prevent postinst node creation when udev is being used. + * Added a README.udev file to /usr/share/doc/mdadm. + + -- martin f. krafft Sun, 22 May 2005 12:57:56 +0200 + +mdadm (1.9.0-2.1) unstable; urgency=high + + * Non-maintainer upload. + * High-urgency upload for sarge targetted RC bugfix. + * Start mdadm-raid before udev on boot-up, so that mdadm device node + creation is honored, and support changing the init script ordering + on upgrades (closes: #294404). + * Fix mdadm --scan to prefer the values contained in /proc/partitions, + instead of picking up device node names at random from /dev. + * Teach mdrun to look at /dev/.static/dev instead of /.dev for udev + mounts requiring autostart (closes: #301560). + + -- Steve Langasek Sun, 27 Mar 2005 21:59:12 -0800 + +mdadm (1.9.0-2) unstable; urgency=low + + * Patched is_standard() to accept /dev/md/* names as standard. + Thanks to Colin Watson . + (closes: Bug#296794) + * Added another typecast to make it compilable on amd64 with gcc-4.0. + Thanks to Andreas Jochens . + (closes: Bug#294217) + * Removed unnecessary second assignment to $BASE in mdrun. + Thanks to Colin Watson . + (closes: Bug#295433) + + -- Mario Joussen Sun, 6 Mar 2005 14:22:24 +0100 + +mdadm (1.9.0-1) unstable; urgency=high + + * New upstream release. + Solves problems with same UUID for each array. + Again a stable upstream version. + (closes: Bug#292282, Bug#293406, Bug#292784, Bug#290363, Bug#292715) + * Added some typecasts to make it compilable on amd64 with gcc-4.0. + Thanks to Andreas Jochens . + (closes: Bug#287638) + + -- Mario Joussen Sun, 6 Feb 2005 12:25:03 +0100 + +mdadm (1.8.1-1) unstable; urgency=low + + * New upstream release. + Fixed segfault if no config file present and --scan is used. + (closes: Bug#283425, Bug#282604, Bug#284024) + * Fixed typo in detailed help of grow mode. + (closes: Bug#286980) + * Added japanese debconf translation. Thanks to Hideki Yamane + . + (closes: Bug#281073) + * Fixed missing variable initialization causing segfaults. + + -- Mario Joussen Sun, 26 Dec 2004 14:44:31 +0100 + +mdadm (1.7.0-2) unstable; urgency=high + + * Changed debconf script to save the settings from the config file. + Thanks to Fabio Massimo Di Nitto and + Frank Lichtenheld for the patch. + (closes: Bug#274208) + * Moved try to load md module inside the AUTOSTART if branch in + /etc/init.d/mdadm. + * Removed try to load md module from /etc/init.d/mdadm-raid. + + -- Mario Joussen Sun, 24 Oct 2004 19:48:06 +0200 + +mdadm (1.7.0-1) unstable; urgency=low + + * New upstream release. + (closes: Bug#267814) + + -- Mario Joussen Sun, 12 Sep 2004 20:48:33 +0200 + +mdadm (1.6.0-3) unstable; urgency=high + + * Added 'Conflicts: raidtools2 (<< 1.00.3-12.1)' because these packages + contain a mdrun.8 man page also. + (closes: Bug#268634, Bug#266527) + * Updated the french translation. + Thanks to Eric + (closes: Bug#266251) + + -- Mario Joussen Sat, 28 Aug 2004 18:23:17 +0200 + +mdadm (1.6.0-2) unstable; urgency=low + + * Included version 0.97 of "Debian Software Root Raid Documentation". + * Now mdrun is only used if no mdadm.conf is present. + Thanks to Thomas Prokosch <7nrmi1s02@sneakemail.com>. + (closes: Bug#264059) + * Added man page for mdrun. + Thanks to Robert Collins . + (closes: Bug#265480) + * Moved /etc/mdadm/debian.conf to /etc/default/mdadm. + (closes: Bug#254922) + * Added a little workaround to mdrun to interact better with udev. + Thanks to Fabio Massimo Di Nitto . + (closes: Bug#259491) + * Updated Brazilian Portuguese translation. + Thanks to Andre Luis Lopes . + (closes: Bug#264220) + + -- Mario Joussen Mon, 16 Aug 2004 22:10:59 +0200 + +mdadm (1.6.0-1) unstable; urgency=low + + * New upstream release. + Detect degraded arrays in --monitor mode now. + (closes: Bug#257357) + * Changed default to autostart RAID array. + (closes: Bug#250792) + * Fixed mdrun problem with kernel 2.6. + Thanks to Andre Tomt and Fabio Massimo Di Nitto + + (closes: Bug#231823) + * Changed reuse warning to be less misleading. + (closes: Bug#253339) + + -- Mario Joussen Tue, 20 Jul 2004 21:40:33 +0200 + +mdadm (1.5.0-2) unstable; urgency=low + + * Added french debconf template. + Thanks to Eric Madesclair . + (closes: Bug#231968) + + -- Mario Joussen Tue, 4 May 2004 21:29:19 +0200 + +mdadm (1.5.0-1) unstable; urgency=low + + * New upstream release. + * Rewrote debconf templates to avoid referring to debconf interface + widgets. + (closes: Bug#231221) + * Removed manual scan for RAID devices from init script. + (closes: Bug#233122, Bug#236762) + * Added creation of an udeb package. + (closes: Bug#243609) + * Added "Debian Software Root Raid Documentation". + Thanks to Lucas Albers . + + -- Mario Joussen Sun, 25 Apr 2004 16:16:06 +0200 + +mdadm (1.4.0-3) unstable; urgency=low + + * Updated to standards version 3.6.1.0 and debhelper 4. + * Corrected definition of BLKGETSIZE64 macro to compile with the + 2.6 kernel headers. + (closes: Bug#223191) + * Swichted to po-debconf to provide localized debconf templates. + (closes: Bug#225288) + + -- Mario Joussen Sun, 1 Feb 2004 19:30:53 +0100 + +mdadm (1.4.0-2) unstable; urgency=low + + * Corrected human readable size calculation. + (closes: Bug#225041) + * Added a warning about reusing hard disks and using the autostart + feature. + (closes: Bug#223790) + + -- Mario Joussen Thu, 25 Dec 2003 19:52:57 +0100 + +mdadm (1.4.0-1) unstable; urgency=low + + * New upstream release. + + -- Mario Joussen Sun, 7 Dec 2003 19:39:27 +0100 + +mdadm (1.3.0-2) unstable; urgency=low + + * Added upstream changelog to package. + + -- Mario Joussen Tue, 12 Aug 2003 21:51:59 +0200 + +mdadm (1.3.0-1) unstable; urgency=low + + * New upstream release. + (closes: Bug#191561, Bug#200921) + + -- Mario Joussen Thu, 31 Jul 2003 20:59:20 +0200 + +mdadm (1.2.0-1) unstable; urgency=low + + * New upstream release. (closes: Bug#183191) + * New version of mdrun that works properly with devfs and temporary + device directory. + (closes: Bug#182035) + * Added 'Conflicts: raidtools' because of a name clash with mdrun. + (closes: Bug#182960) + + -- Mario Joussen Sun, 16 Mar 2003 13:32:45 +0100 + +mdadm (1.0.1-4) unstable; urgency=low + + * Changed mdrun so that it can deal with partition statistics in + /proc/partitions. + (closes: Bug#174000, Bug#175130) + * Added russian (ru) debconf template translation. Thanks to Sergey + Spiridonov . + + -- Mario Joussen Sun, 5 Jan 2003 13:14:45 +0100 + +mdadm (1.0.1-3) unstable; urgency=low + + * Fixed a bug in mdrun. (closes: Bug#167607) + + -- Mario Joussen Mon, 11 Nov 2002 07:53:23 +0100 + +mdadm (1.0.1-2) unstable; urgency=low + + * Fixed typo in help option. (closes: Bug#151533) + * Added a script that discovers and assembles all arrays automatically. + Thanks to Eduard Bloch . + (closes: Bug#161699) + + -- Mario Joussen Fri, 1 Nov 2002 13:46:47 +0100 + +mdadm (1.0.1-1) unstable; urgency=low + + * New upstream release. + + -- Mario Joussen Thu, 30 May 2002 14:01:22 +0200 + +mdadm (0.8.2-1) unstable; urgency=low + + * New upstream release. + * Splitted up mdadm.templates in one file for each language. + * Added brazilian portuguese (pt_BR) debconf template translation. + Thanks to Andre Luis Lopes . + (closes: Bug#141540) + + -- Mario Joussen Thu, 18 Apr 2002 19:31:00 +0200 + +mdadm (0.7.2-1) unstable; urgency=low + + * New upstream release. + * 'mdctl' was renamed to 'mdadm' upstream. + * Removed question about updating mdctl init script links. + + -- Mario Joussen Sat, 23 Mar 2002 02:50:51 +0100 + +mdctl (0.5-4) unstable; urgency=low + + * Added debconf template to ask the user if the init script links + should be updated. + + -- Mario Joussen Mon, 4 Mar 2002 22:53:37 +0100 + +mdctl (0.5-3) unstable; urgency=low + + * Splitted up init script in two parts. One starts the md array and the + other starts the raid monitor daemon. + (closes: Bug#136184) + + -- Mario Joussen Thu, 28 Feb 2002 22:45:57 +0100 + +mdctl (0.5-2) unstable; urgency=low + + * Included optimization in Makefile + (closes: Bug#127687) + * Removed Conflicts/Replaces/Provides: mdutils + (closes: Bug#127684, Bug#127719) + * Added an init script, which can start md arrays and the raid monitor + daemon + * MD devices are now created under /dev if necessary + * Added a sample configuration file + + -- Mario Joussen Sun, 13 Jan 2002 23:43:40 +0100 + +mdctl (0.5-1) unstable; urgency=low + + * Initial Release. + (closes: Bug#126610) + + -- Mario Joussen Wed, 26 Dec 2001 17:07:09 +0100 --- mdadm-2.6.2.orig/debian/mdadm.dirs +++ mdadm-2.6.2/debian/mdadm.dirs @@ -0,0 +1,8 @@ +sbin +etc/mdadm +usr/share/mdadm +usr/share/initramfs-tools/hooks +usr/share/initramfs-tools/scripts/local-top +usr/share/bug/mdadm +usr/share/lintian/overrides +var/lib/mdadm --- mdadm-2.6.2.orig/debian/TODO +++ mdadm-2.6.2/debian/TODO @@ -0,0 +1,31 @@ +debian mdadm TODO list +====================== + +- version-1 is a nightmare. E.g. on partitionable arrays, with / on + /dev/md_d0p3, mdadm -Es ignores /dev/md_d0 and just uses the name, so + /dev/md/. +- figure out something about device names. +- (better) udev integration + +- check whether mdadm.conf and system are consistent during initramfs creation + and fail otherwise (#381303). +- add code to compare existing and expected configuration, after standardising + the files. In most cases, we'll have to answer DUNNO as to whether the + existing configuration file is okay, but I guess in some cases we can + determine that the configuration is okay. A conservative approach would be + beneficial to the user. Not sure if it's worth the effort though. +- one nice^W important thing would be to check device names and UUIDs at least. + +- verify operation without udev + - udev removed before mdadm installed + - udev removed after mdadm installed + +- more granular handling of init.d starts/stops, don't force all arrays to be + started. +- let user specify when to start/stop which array (#398310). +- also only stop those array we started; this can be easily done with + sentinels in $STATEDIR + +- manage DAEMON_OPTIONS with debconf + +$Id: TODO 282 2006-12-08 08:32:53Z madduck $ --- mdadm-2.6.2.orig/debian/mkconf +++ mdadm-2.6.2/debian/mkconf @@ -0,0 +1,110 @@ +#!/bin/sh +# +# mkconf -- outputs valid mdadm.conf contents for the local system +# +# Copyright © martin f. krafft +# distributed under the terms of the Artistic Licence 2.0 +# +# $Id: mkconf 324 2007-05-05 18:49:44Z madduck $ +# + +set -eu + +ME="${0##*/}" +MDADM=/sbin/mdadm +DEBIANCONFIG=/etc/default/mdadm +CONFIG=/etc/mdadm/mdadm.conf + +test -r $DEBIANCONFIG && . $DEBIANCONFIG + +if [ -n "${MDADM_MAILADDR__:-}" ]; then + # honour MAILADDR from the environment (from postinst) + MAILADDR="$MDADM_MAILADDR__" +else + # preserve existing MAILADDR + MAILADDR="$(sed -ne 's/^MAILADDR //p' $CONFIG 2>/dev/null)" || : +fi + +# save existing values as defaults +if [ -r "$CONFIG" ]; then + DEVICE="$(sed -ne 's/^DEVICE //p' $CONFIG)" + CREATE="$(sed -ne 's/^CREATE //p' $CONFIG)" + HOMEHOST="$(sed -ne 's/^HOMEHOST //p' $CONFIG)" + PROGRAM="$(sed -ne 's/^PROGRAM //p' $CONFIG)" +fi + +generate=0 +[ "${1:-}" = force-generate ] && rm -f $CONFIG +case "${1:-}" in + generate|force-generate) + [ -n "${2:-}" ] && CONFIG=$2 + # only barf if the config file specifies anything else than MAILADDR + if egrep -qv '^(MAILADDR.*|#.*|)$' $CONFIG 2>/dev/null; then + echo "E: $ME: $CONFIG already exists." >&2 + exit 255 + fi + + mkdir --parent ${CONFIG%/*} + exec >$CONFIG + generate=1 + ;; +esac + +cat <<_eof +# mdadm.conf +# +# Please refer to mdadm.conf(5) for information about this file. +# + +# by default, scan all partitions (/proc/partitions) for MD superblocks. +# alternatively, specify devices to scan, using wildcards if desired. +DEVICE ${DEVICE:-partitions} + +# auto-create devices with Debian standard permissions +CREATE ${CREATE:-owner=root group=disk mode=0660 auto=yes} + +# automatically tag new arrays as belonging to the local system +HOMEHOST ${HOMEHOST:-} + +# instruct the monitoring daemon where to send mail alerts +MAILADDR ${MAILADDR:-root} + +_eof + +if [ -n "$PROGRAM" ]; then + cat <<-_eof + # program to run when mdadm monitor detects potentially interesting events + PROGRAM ${PROGRAM} + + _eof +fi + +error=0 +if [ ! -r /proc/mdstat ]; then + echo W: $ME: MD subsystem is not loaded, thus I cannot scan for arrays. >&2 + error=1 +elif [ ! -r /proc/partitions ]; then + echo W: $ME: /proc/partitions cannot be read, thus I cannot scan for arrays. >&2 + error=2 +else + echo "# definitions of existing MD arrays" + if ! $MDADM --examine --scan --config=partitions; then + error=$(($? + 128)) + echo W: $ME: failed to scan for partitions. >&2 + echo "### WARNING: scan failed." + else + echo + fi +fi + +if [ $generate -eq 1 ]; then + cat <<_eof +# This file was auto-generated on $(date -R) +# by mkconf \$Id: mkconf 324 2007-05-05 18:49:44Z madduck $ +_eof + + mkdir -p /var/lib/mdadm + md5sum $CONFIG > /var/lib/mdadm/mdadm.conf-generated +fi + +exit $error --- mdadm-2.6.2.orig/debian/mdadm.config +++ mdadm-2.6.2/debian/mdadm.config @@ -0,0 +1,195 @@ +#!/bin/sh +# Copyright © 2001-2004 Mario Jou/3en +# Copyright © martin f. krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: mdadm.config 314 2007-03-05 11:23:05Z madduck $ +# + +# we need debconf-escape. Without it, defer the configuration. +if [ ! -x "$(command -v debconf-escape 2>/dev/null)" ]; then + echo 'I: mdadm: debconf backend too old, defering configuration...' >&2 + exit 0 +fi + +. /usr/share/debconf/confmodule +# see #369953 for ordering +set -eu + +CONFIG=/etc/mdadm/mdadm.conf +ALTCONFIG=/etc/mdadm.conf +[ ! -f $CONFIG ] && [ -f $ALTCONFIG ] && CONFIG=$ALTCONFIG + +DEBIANCONFIG=/etc/default/mdadm +DEBIANCONFIG_OLD=/etc/mdadm/debian.conf + +if [ ! -e "$DEBIANCONFIG" ]; then + if [ -e "$DEBIANCONFIG_OLD" ]; then + DEBIANCONFIG="$DEBIANCONFIG_OLD" + fi +fi + +INITRDSTART='' + +if [ -s $DEBIANCONFIG ] ; then + AUTOSTART=true + AUTOCHECK=true + START_DAEMON=true + MAILADDR=root + + [ -f $DEBIANCONFIG ] && . $DEBIANCONFIG + if [ -f $CONFIG ]; then + MAILADDR=$(sed -rne 's/^MAILADDR[[:space:]]*([^[:space:]]+).*/\1/p' $CONFIG) + fi + + # if $MAIL_TO from $DEBIANCONFIG is set, give it priority. This is because + # it was used in the command line invocation of the mdadm monitor, and thus + # overruled any existing setting in /etc/mdadm/mdadm.conf. + # There's a slight chance of loss of a configuration setting (MAILADDR in + # /etc/mdadm/mdadm.conf), but it's only an email address, and it is likely + # unused anyway, thus we run the risk. + [ -n "${MAIL_TO:-}" ] && MAILADDR="$MAIL_TO" + + [ -n "$AUTOSTART" ] && db_set mdadm/autostart "$AUTOSTART" + [ -n "$AUTOCHECK" ] && db_set mdadm/autocheck "$AUTOCHECK" + [ -n "$START_DAEMON" ] && db_set mdadm/start_daemon "$START_DAEMON" + [ -n "$MAILADDR" ] && db_set mdadm/mail_to "$MAILADDR" +fi + +chrooted() { + test "$(stat -c "%d/%i" /)" != "$(stat -Lc "%d/%i" /proc/1/root 2>/dev/null)" +} + +get_root_raiddev() { + local rootraiddev; + rootraiddev="$(df / | sed -rne 's,^(/dev/[^[:space:]]+).*,\1,p')" + if ! mdadm --detail $rootraiddev >/dev/null 2>&1; then + return 1 + fi + echo ${rootraiddev%p[0-9]*} + return 0 +} + +get_initrdstart() { + db_fget mdadm/initrdstart seen + if chrooted || [ "$RET $INITRDSTART" = "false all" ]; then + echo all + return 1 + fi + + get_root_raiddev || echo all +} + +[ -z "$INITRDSTART" ] && INITRDSTART="$(get_initrdstart)" || : +[ -n "$INITRDSTART" ] && db_set mdadm/initrdstart "$INITRDSTART" + +db_capb escape + +msg=intro; suffix=''; error=0 +while true; do + db_metaget mdadm/initrdstart_msg_${msg} extended_description || : + db_subst mdadm/initrdstart msg "$(echo -n "${RET}${suffix}" | debconf-escape -e)" + ret=0; db_input high mdadm/initrdstart || ret=$? + db_go + + if [ $error -ne 0 ] && [ $ret -eq 30 ]; then + # there was an error in a previous run of this loop, but the above question + # was not asked, so we better exit the endless loop... + echo "W: mdadm: unable to determine MD arrays needed for boot." >&2 + echo "W: mdadm: falling back to starting all of them..." >&2 + INITRDSTART=all + break + fi + + db_get mdadm/initrdstart + INITRDSTART="$(echo $RET | tr , ' ')" + + case "$INITRDSTART" in + ''|none) INITRDSTART=none; break;; + all) break;; + + *) + arrays='' + for i in $INITRDSTART; do + + # standardise by prefixing /dev/ + i="/dev/${i#/dev/}" + + # remove partition from partitionable array + i="${i%p[0-9]*}" + + if [ ! -e "$i" ]; then + error=1; msg=errexist; suffix=": $i"; break + fi + + if [ ! -b "$i" ]; then + t="$(readlink -nf "$i")" + if [ ! -b "$t" ]; then + suffix=": $t" + else + suffix=": $i" + fi + error=1; msg=errblock; break + fi + + if ! mdadm --detail "$i" >/dev/null 2>&1; then + error=1; msg=errmd; suffix=": $i"; break + fi + + if [ -f $CONFIG ]; then + if ! egrep -q "^(ARRAY)?[[:space:]]+$i([[:space:]]+|$)" $CONFIG; then + t="$(readlink -nf "$i")" + if [ -L "$i" ] \ + && egrep -q "^(ARRAY)?[[:space:]]+$t([[:space:]]|$)+" $CONFIG; then + i="$t" + else + db_set mdadm/initrdstart_notinconf false + db_fset mdadm/initrdstart_notinconf seen false + db_subst mdadm/initrdstart_notinconf array "$i" + db_subst mdadm/initrdstart_notinconf config "$CONFIG" + db_input high mdadm/initrdstart_notinconf || : + db_go + db_get mdadm/initrdstart_notinconf + if [ "$RET" = true ]; then + md5sum $CONFIG > /var/lib/mdadm/CONF-UNCHECKED + error=0 + else + db_fset mdadm/initrdstart seen false + db_set mdadm/initrdstart all + error=1; msg=errconf; suffix=": $i"; break + fi + fi + fi + fi + + # uniquely add device name + echo $arrays | egrep -q "\b${i}\b" || arrays="${arrays:+$arrays }$i" + done + + if [ $error -eq 0 ]; then + INITRDSTART="$arrays" + # exit the while true loop + break + fi + ;; + esac +done + +db_set mdadm/initrdstart "$INITRDSTART" + +if [ "$INITRDSTART" != all ]; then + db_input high mdadm/autostart || : + db_go +fi + +db_input medium mdadm/autocheck || : +db_go + +db_input medium mdadm/start_daemon || : +db_go + +db_get mdadm/start_daemon || : +if [ "$RET" = true ]; then + db_input medium mdadm/mail_to || : + db_go +fi --- mdadm-2.6.2.orig/debian/README.Debian +++ mdadm-2.6.2/debian/README.Debian @@ -0,0 +1,87 @@ +mdadm for Debian +================ + +Please make sure you read into /usr/share/doc/mdadm/NEWS.Debian.gz and the +documents listed under "further reading" a little later in this file. + +The latest version of this document is available here: + http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.Debian?op=file&rev=0&sc=0 + +Upgrading and the configuration file +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +This version of mdadm now NEEDS /etc/mdadm/mdadm.conf, which it will try to +generate during installation, if nonexistent. + +PLEASE MAKE SURE TO READ /usr/share/doc/mdadm/README.upgrading-2.5.3.gz ! + +You can use the output of /usr/share/mdadm/mkconf to generate your very own +mdadm.conf file, and look into +/usr/share/doc/mdadm/examples/mdadm.conf-example for inspiration. + +Autostarting devices +~~~~~~~~~~~~~~~~~~~~ +The mdadm.conf file controls which devices are to be started automatically by +mdadm during boot (assuming AUTOSTART is set to true in /etc/default/mdadm), +and various other parameters about how they are to be started. The file can +also contain some control parameters for the mdadm monitor daemon. See +mdadm.conf(5) for more information. + +Note: this only applies to modular kernels. If you use a monolithic kernel, +you can control which devices are started automatically by changing the +partition type: 0xfd for autostart, 0x83 to prevent autostart. mdadm does not +actually care about the partition type, only the kernel does. + +Common recipes +~~~~~~~~~~~~~~ +Check /usr/share/doc/mdadm/README.recipes.gz for some simple examples of how +to do the most common stuff with mdadm. + +To RAID5 or not to RAID5 +~~~~~~~~~~~~~~~~~~~~~~~~ +See http://www.miracleas.com/BAARF/BAARF2.html . The package maintainer could +not possibly come up with so much emotion over such a technical topic. + +See also the RAID5_versus_RAID10.txt.gz document included with this package. + +Further reading +~~~~~~~~~~~~~~~ +The documentation for the kernel md driver is included in +/usr/share/doc/mdadm/md.txt.gz. In addition, the md(4) manpage provides +valuable information about the applicable concepts. Do read those! + +Further documents of interest: + - Linux-RAID reference Wiki: + http://linux-raid.osdl.org + - Linux software RAID HOWTO: + http://tldp.org/HOWTO/Software-RAID-HOWTO.html + - linux-raid mailing list info: + http://vger.kernel.org/vger-lists.html#linux-raid + - linux-raid mailing list FAQ: + http://www.faqs.org/contrib/linux-raid/ + +Upstream +~~~~~~~~ +For completeness: The upstream repository is available from + http://neil.brown.name/git?p=mdadm + git clone git://neil.brown.name/mdadm + +Debian package maintenance +~~~~~~~~~~~~~~~~~~~~~~~~~~ +The package is maintained in SVN on alioth.debian.org. To obtain the source: + + svn://svn.debian.org/svn/pkg-mdadm/mdadm/trunk + svn+ssh://@svn.debian.org/svn/pkg-mdadm/mdadm/trunk + +The second form is for developers with the intention to contribute. If you +want to join the mdadm effort, please talk to me. + +Since the SVN repository only store the ./debian directory, you need the +upstream tarball as well. I suggest using svn-buildpackage. + +Please do not forget to tag new releases. + +There are things to do listed in debian/TODO . + + -- martin f. krafft Fri, 07 Jul 2006 10:55:42 +0200 + +$Id: README.Debian 253 2006-10-31 13:29:35Z madduck $ --- mdadm-2.6.2.orig/debian/mdrun.8 +++ mdadm-2.6.2/debian/mdrun.8 @@ -0,0 +1,65 @@ +.\" +.\" This man page writeen aug 13 3004 by Robert Collins +.\" This template provided by Tom Christiansen . +.\" +.TH MDRUN 8 +.SH NAME +mdrun \- autodetect and activate all raid partitions +.SH SYNOPSIS +mdrun detects all (or named) raid partitions and activates them. + +Without arguments: autodetect all RAID partitions and activate MDs. +.PP +.B mdrun +.B LIST +.PP +.B mdrun +[ +.I DEVDIR +] +.I NUMBER UUID +[ +.I NUMBER UUID ... +] +.SH WARNING +mdrun has been deprecated on Debian. Please use +.B mdadm +instead. You can find information on how to use and configure +.B mdadm +in the +.BR mdadm(8) +and +.BR mdadm.conf(5) +manpages +.SH OPTIONS +.TP +.B LIST +lists all raids in the syntax needed for the number uuid pairs the alternative syntax accepts. +.TP +.I DEVDIR +An optional override for the /dev directory. +.TP +.I NUMBER UUID +pairs of number, uuids that define a md element to run. number comes from /dev/md/*. +.SH "RETURN VALUE" +Nothing is displayed and mdrun returns 0 on success. +.SH ERRORS +On error, non-zero is returned, and a diagnostic string is printed. +.SH EXAMPLES +mdrun. +.SH ENVIRONMENT +MORERAIDVOLUMES (list of strings) : additional raid disks to scan, eg. loop devices. +.SH NOTES +If the first argument is a directory, it will be used as a writeable temporary directory for device nodes. +mdrun needs mknod to create them on-the-fly. +.SH CAVEATS +Create /dev/fs directory if you have devfs support in the kernel but do not want to mount it over /dev. +Usage of /dev/fs directory will keep mdrun away from /dev. +.SH AUTHOR +Eduard Bloch . +.SH HISTORY +This man page was created Aug 13 2004 by Robert Collins. +.SH "SEE ALSO" +.BR mdadm (8). + + --- mdadm-2.6.2.orig/debian/checkarray +++ mdadm-2.6.2/debian/checkarray @@ -0,0 +1,175 @@ +#!/bin/sh +# +# checkarray -- initiates a check run of an MD array's redundancy information. +# +# Copyright © martin f. krafft +# distributed under the terms of the Artistic Licence 2.0 +# +# $Id: checkarray 198 2006-10-05 06:24:26Z madduck $ +# + +set -eu + +PROGNAME=${0##*/} + +about() +{ + echo "$PROGNAME -- MD array (RAID) redundancy checker tool" + echo '$Id: checkarray 198 2006-10-05 06:24:26Z madduck $' + echo "Copyright © martin f. krafft " + echo "Released under the terms of the Artistic Licence 2.0" +} + +usage() +{ + about + echo + echo "Usage: $PROGNAME [options] [arrays]" + echo + echo "Valid options are:" + cat <<-_eof | column -s\& -t + -a|--all & check all assembled arrays (check /proc/mdstat). + -c|--cron & honour AUTOCHECK setting in /etc/default/mdadm. + -s|--status & print redundancy check status of devices. + -x|--cancel & queue a request to cancel a running redundancy check. + -q|--quiet & suppress informational messages. + -Q|--real-quiet & suppress all output messages, including warnings and errors. + -h|--help & show this output. + -V|--version & show version information. + _eof + echo + echo "Examples:" + echo " $PROGNAME --all" + echo " $PROGNAME --quiet /dev/md[123]" + echo " $PROGNAME -sa" + echo " $PROGNAME -x --all" + echo + echo "Devices can be specified in almost any format. The following are" + echo "all equivalent:" + echo " /dev/md0, md0, /dev/md/0, /sys/block/md0" + echo + echo "The --all option overrides all arrays passed to the script." + echo + echo "You can also control the status of a check with /proc/mdstat ." +} + +SHORTOPTS=achVqQsx +LONGOPTS=all,cron,help,version,quiet,real-quiet,status,cancel + +eval set -- $(getopt -o $SHORTOPTS -l $LONGOPTS -n $PROGNAME -- "$@") + +arrays='' +cron=0 +all=0 +quiet=0 +status=0 +action=check + +for opt in $@; do + case "$opt" in + -a|--all) all=1;; + -c|--cron) cron=1;; + -s|--status) action=status;; + -x|--cancel) action=idle;; + -h|--help) usage; exit 0;; + -q|--quiet) quiet=1;; + -Q|--real-quiet) quiet=2;; + -V|--version) about; exit 0;; + /dev/md/*|md/*) arrays="${arrays:+$arrays }md${opt#*md/}";; + /dev/md*|md*) arrays="${arrays:+$arrays }${opt#/dev/}";; + /sys/block/md*) arrays="${arrays:+$arrays }${opt#/sys/block/}";; + --) :;; + *) echo "$PROGNAME: E: invalid option: $opt" >&2; usage >&2; exit0;; + esac +done + +is_true() +{ + case "${1:-}" in + [Yy]es|[Yy]|1|[Tt]rue|[Tt]) return 0;; + *) return 1; + esac +} + +DEBIANCONFIG=/etc/default/mdadm +[ -r $DEBIANCONFIG ] && . $DEBIANCONFIG +if [ $cron = 1 ] && ! is_true ${AUTOCHECK:-false}; then + [ $quiet -lt 1 ] && echo "$PROGNAME: I: disabled in $DEBIANCONFIG ." >&2 + exit 0 +fi + +if [ ! -f /proc/mdstat ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: E: MD subsystem not loaded, or /proc unavailable." >&2 + exit 2 +fi + +if [ ! -d /sys/block ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: E: /sys filesystem not available." >&2 + exit 7 +fi + +if [ -z "$(ls /sys/block/md* 2>/dev/null)" ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: W: no active MD arrays found." >&2 + [ $quiet -lt 2 ] && echo "$PROGNAME: W: (maybe uninstall the mdadm package?)" >&2 + exit 5 +fi + +if [ -z "$(ls /sys/block/md*/md/level 2>/dev/null)" ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: W: kernel too old, no support for redundancy checks." >&2 + exit 6 +fi + +if ! egrep -q '^raid([1456]|10)$' /sys/block/md*/md/level 2>/dev/null; then + [ $quiet -lt 1 ] && echo "$PROGNAME: I: no redundant arrays present; skipping checks..." >&2 + exit 0 +fi + +if [ -z "$(ls /sys/block/md*/md/sync_action 2>/dev/null)" ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: W: no kernel support for redundancy checks." >&2 + exit 3 +fi + +[ $all = 1 ] && arrays="$(ls -d1 /sys/block/md* | cut -d/ -f4)" + +for array in $arrays; do + SYNC_ACTION_CTL=/sys/block/$array/md/sync_action + + if [ ! -e $SYNC_ACTION_CTL ]; then + [ $quiet -lt 1 ] && echo "$PROGNAME: I: skipping non-redundant array $array." >&2 + continue + fi + + cur_status="$(cat $SYNC_ACTION_CTL)" + + if [ $action = status ]; then + echo "$array: $cur_status" + continue + fi + + if [ ! -w $SYNC_ACTION_CTL ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: E: $SYNC_ACTION_CTL not writeable." >&2 + exit 4 + fi + + case "$action" in + idle) + echo $action > $SYNC_ACTION_CTL + [ $quiet -lt 1 ] && echo "$PROGNAME: I: cancel request queued for array $array." >&2 + ;; + + check) + if [ "$cur_status" != idle ]; then + [ $quiet -lt 2 ] && echo "$PROGNAME: W: array $array not idle, skipping..." >&2 + continue + fi + + # queue request for the array. The kernel will make sure that these requests + # are properly queued so as to not kill one of the array. + echo $action > $SYNC_ACTION_CTL + [ $quiet -lt 1 ] && echo "$PROGNAME: I: check queued for array $array." >&2 + ;; + esac + +done + +exit 0 --- mdadm-2.6.2.orig/debian/README.upgrading-2.5.3 +++ mdadm-2.6.2/debian/README.upgrading-2.5.3 @@ -0,0 +1,137 @@ +Upgrading to mdadm 2.5.3 from previous versions +=============================================== + +With version 2.5.3, the Debian mdadm package now requires a mdadm.conf file. +This file should be in /etc/mdadm/mdadm.conf, although /etc/mdadm.conf will +also be read if the former is not present, but it is less preferred. + +The reason the configuration file is now required is because it was impossible +to come up with robust heuristics to replace the previously used mdrun, while +addressing its primary deficiency of not honouring the super-minor field and +randomly assembling devices (see #354705). + +Also see /usr/share/doc/mdadm/README.mdrun + +Systems without a mdadm.conf file +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +If your system does not have an mdadm.conf file, the package creates one for +you during the installation phase. Furthermore, a configuration file is +created during the updating of the initramfs (initial ramdisk), if no file is +found at the time. In both cases, the running system is used as a reference, +meaning that the file is generated automatically in such a way as to reflect +the running system. + +This should work in most cases. I strongly suggest, however, that you inspect +the generated file (/etc/mdadm/mdadm.conf) before you reboot. If you find any +anomaly or mistakes, correct them and proceed with the next step ("Systems +with a mdadm.conf file"). + +Systems with a mdadm.conf file +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +If an existing configuration file is found, it is *ignored* until you checked +it and gave mdadm permission to use it. Even though this is a nuisance to some +users, it is a necessary measure: previous versions of mdadm did not +necessarily use the information in this file, even if it existed; thus there +is no guarantee that the file properly describes the system's configuration. + +Therefore, you are required to inspect /etc/mdadm/mdadm.conf or +/etc/mdadm.conf (whichever one is present, the first gets priority if both are +present) and ensure that all arrays are properly identified. Here are a number +of recommended checks: + + - Verify that all arrays referenced by /etc/fstab, /etc/crypttab, your LVM + metadata, and whatever other subsystem uses MD arrays (RAIDs) on your + machine have a corresponding line in the configuration file. + + Make sure to verify that your bootloader refers to the proper device name, + in case your root filesystem is on an MD array. + + In particular, verify that the device node name is exactly the same; + /dev/md6 is *not* identical to /dev/md/6. Partitionable arrays are + a slight exception: if /dev/md_d0p3 is referenced, you need an entry for + /dev/md_d0 in the configuration file. + + - Compare your file with the output of /usr/share/mdadm/mkconf . In + particular, make sure that the UUID matches for each array, whenever + a UUID is specified. Also compare the values of super-minor, name, and + devices. Only one match identifier (UUID, super-minor, name, devices) is + needed for each array, but if multiple identifiers are specified, all must + match. See mdadm.conf(5). + + Identifying arrays by UUID is the preferred method. + +Once you have verified that the configuration file is accurate, you need to +let mdadm know, and update the initial ramdisk. This is accomplished with the +following two commands: + + rm -f /var/lib/mdadm/CONF-UNCHECKED + update-initramfs -u -k all + +Depending on your setup, mdadm should print an appropriate informational +message. Please make sure that it is in accordance with what you would expect. + +What to do if my system does not boot anymore? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +First thing: don't panic! If your system does not boot anymore as a result of +an mdadm upgrade, it is *very* unlikely that you lost any data. + +Having said that, it is important that you exercise great care and understand +what you are doing. If you do not know how to revive a system that does not +boot because it fails to assemble MD arrays (RAIDs), consider asking someone +who does for help. + +If you are using initramfs (which is the default since Debian "etch"), it will +probably be easy to revive the system. If you are experiencing problems with +another initial ramdisk alternative, you will have to resort to using a rescue +disk, such as the debian-installer CD/DVD, or a live system, such as Knoppix. + +With initramfs, specify 'break=mount' as a kernel boot command line option, +and commence the boot process. Eventually, you will be dumped into a shell. +From here, you can execute + + ./scripts/local-top/mdadm + +and inspect the output. If you want to see what exactly the script is doing, +run + + sh -x ./scripts/local-top/mdadm + +instead. + +Your primary goal is the assembly of the array(s) needed to bring up your root +filesystem. If the above script fails to do that, take note of its output (for +a later bug report), and then proceed to simply assemble the array by hand. + +For instance, if your root array is on /dev/md1, which is made up of +/dev/sd[abc]1, just run: + + /sbin/mdadm -A --auto=yes /dev/md1 --run /dev/sd[abc]1 + /sbin/mdadm -Q /dev/md1 # to verify + +If your root filesystem is on multiple arrays (e.g. on LVM), repeat for each +constituent array. + +When you are done, hit ctrl-d and watch the system boot. + +When it is back up, carefully inspect your mdadm.conf file and ensure that +INITRDSTART is properly set in /etc/default/mdadm; set it to 'all' to be safe. + +In case you are not using initramfs, you need to find out what's going wrong +during the boot process. Both yaird and initrd use a single mdadm --assemble +call to bring up the device holding the root filesystem. If that command +fails, you may need to recreate the image and make sure it gets the right +parameters. + +If you rely on the kernel to assemble the arrays (MD support built-in, not +modular, and partitions of type 0xfd) and the process fails, the superblock +information is probably not accurate. In such a case, try to assemble the +arrays from a rescue disc or live system just as you would expect the kernel +to do it. Afterwards, verify the superblock information (mdadm --examine). + +If you continue to experience problems, please file a bug report with all the +relevant information. The reportbug tool will automatically include the most +relevant data in the report. + + -- martin f. krafft Mon, 23 Sep 2006 23:49:10 +0100 + +$Id: README.initramfs-transition 89 2006-08-08 09:33:05Z madduck $ --- mdadm-2.6.2.orig/debian/README.initramfs-transition +++ mdadm-2.6.2/debian/README.initramfs-transition @@ -0,0 +1,52 @@ +mdadm for Debian - initramfs transition +======================================= + +If you are using monolithic kernels (no modules), you need not concern +yourself with any of this. + +If you are using yaird or initrd-tools/mkinitrd, please see README.mdrun. The +following information is irrelevant to you. + +The following information is about #367567. The gist is that the hooks and +scripts to take care of MD arrays (RAIDs) during boot with an initramfs have +been improved and moved into the mdadm package. mdrun has been deprecated on +the way (see README.mdrun). + +initramfs-tools does *not* conflict with older mdadm but instead provides +fallback code in case mdadm << 2.5-1 is installed (which does not provide the +hooks yet). This decision was made in order to prevent the slight chance that +mdadm would be removed due to the conflict. See #380089. + +Unless I've overlooked a detail, no interaction is required from the side of +the user (apart from the new debconf question) to install and get mdadm +running and integrated with initramfs-tools. It helps to ensure that +update-initramfs produces output that squares with your own perception of what +is needed to boot, and that the output of the script /usr/share/mdadm/mkconf +is sane after installation and before you reboot. + +Also, you may want to provide yourself a safety net by making a copy of the +initrd: + + cp /boot/initrd.img-$(uname -r) /boot/initrd.img-$(uname -r).before-mdadm2 + +and then to duplicate your main grub or lilo stanzas (rerun lilo!) and point +them to the saved initrd. If things go haywire, you should be able to restore +a working condition with the saved initrd. + +If you want to move to the new hooks and scripts without installing +initramfs-tools 0.70, do this: + + rm /usr/share/initramfs-tools/hooks/md + sed -i -e 's,^PREREQ=\"md\"$,PREREQ=\"mdadm\",' \ + /usr/share/initramfs-tools/scripts/local-top/lvm + update-initramfs -u -k all + +If update-initramfs says something about initrd having been altered and +refuses to do something, use -t unless you modified the initrd on purpose and +don't want it overwritten. + +Again, please report success or failure to me. + + -- martin f. krafft Mon, 23 Sep 2006 23:48:21 +0100 + +$Id: README.initramfs-transition 190 2006-09-23 21:48:23Z madduck $ --- mdadm-2.6.2.orig/debian/mdadm.links +++ mdadm-2.6.2/debian/mdadm.links @@ -0,0 +1 @@ +sbin/mdadm-startall usr/share/mdadm/startall --- mdadm-2.6.2.orig/debian/compat +++ mdadm-2.6.2/debian/compat @@ -0,0 +1 @@ +4 --- mdadm-2.6.2.orig/debian/README.checkarray +++ mdadm-2.6.2/debian/README.checkarray @@ -0,0 +1,23 @@ +checkarray notes +================ + +checkarray will run parity checks across all your redundant arrays. By +default, it is configured to run on the first Sunday of each month, at 01:06 +in the morning. This is realised by asking cron to wake up every Sunday with +/etc/cron.d/mdadm, but then only running the script when the day of the month +is less than or equal to 7. See #380425. + +'check' is a read-only operation, even though the kernel logs may suggest +otherwise (e.g. /proc/mdstat and several kernel messages will mention +"resync"). Please also see question 21 of the FAQ. + +If, however, while reading, a read error occurs, the check will trigger the +normal response to read errors which is to generate the 'correct' data and try +to write that out - so it is possible that a 'check' will trigger a write. +However in the absence of read errors it is read-only. + +You can cancel a running array check with the -x option to checkarray. + + -- martin f. krafft Mon, 08 Jan 2007 02:07:19 +0100 + +$Id: README.checkarray 295 2007-01-08 01:07:42Z madduck $ --- mdadm-2.6.2.orig/debian/mdadm-raid +++ mdadm-2.6.2/debian/mdadm-raid @@ -0,0 +1,263 @@ +#!/bin/sh +# +# Start all arrays specified in the configuration file. +# +# Copyright © 2001-2005 Mario Jou/3en +# Copyright © 2005-2006 Martin F. Krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: mdadm-raid 297 2007-01-11 15:05:42Z madduck $ +# +### BEGIN INIT INFO +# Provides: mdadm-raid +# Required-Start: mountkernfs +# Should-Start: udev devfsd +# Required-Stop: mountkernfs +# Should-Stop: udev devfsd +# Default-Start: S +# Default-Stop: 0 6 +# Short-Description: MD array assembly +# Description: This script assembles a system's MD arrays, according to +# the settings in /etc/mdadm/mdadm.conf and the preferences +# in /etc/default/mdadm. +### END INIT INFO + +set -eu + +MDADM=/sbin/mdadm +CONFIG=/etc/mdadm/mdadm.conf +ALTCONFIG=/etc/mdadm.conf +DEBIANCONFIG=/etc/default/mdadm + +test -x "$MDADM" || exit 0 + +AUTOSTART=true +test -f $DEBIANCONFIG && . $DEBIANCONFIG + +. /lib/lsb/init-functions + +short_dev() +{ + local dev=${1##*/} + case "$dev" in + md*|md_*|mdp*|mdp_*) echo "$dev";; + d*) echo "md_${dev}";; + *) echo "md${dev}";; + esac +} + +log() +{ + case "$1" in + [[:digit:]]*) success=$1; shift;; + *) :;; + esac + log_action_begin_msg "$1"; shift + log_action_end_msg ${success:-0} "$*" +} + +log_dev() +{ + success=${1:-}; shift + dev=${1:-}; shift + log $success "${PREFIX:-} $(short_dev ${dev:-})" "$*" +} + +log_notice() +{ + log 0 "${PREFIX:-}s" "$*" +} + +log_problem() +{ + log 1 "${PREFIX:-}s" "$*" +} + +is_true() +{ + case "${1:-}" in + [Yy]es|[Yy]|1|[Tt]rue|[Tt]) return 0;; + *) return 1; + esac +} + +for dir in /lib/init/rw /dev/shm /dev; do + statedir=$dir/.mdadm + test -d $statedir && STATEDIR=$statedir && break + test -w $dir || continue + mkdir $statedir || continue + STATEDIR=$statedir + break +done + +case "${1:-}" in + start) + PREFIX="Assembling MD array" + + if is_true $AUTOSTART || is_true ${MDADM_FORCE_AUTOSTART__:-0}; then + if [ ! -f /proc/mdstat ] && [ -x "$(command -v modprobe)" ] ; then + modprobe -kq md 2>/dev/null || : + fi + if [ ! -f /proc/mdstat ]; then + log_problem "failed to load MD subsystem" + exit 0 + fi + + if [ -f $CONFIG ] || [ -f $ALTCONFIG ]; then + # handle devfs-style names and version-1 devices + # fail gracefully in case we're on a read-only filesystem, in which + # case it's safe to assume that the admin knows what s/he's doing. + # See (#382876). + mkdir --parent /dev/md || : + + # ugly hack because shell sucks + IFSOLD=${IFS:-} + IFS=' +' + for line in $($MDADM --assemble --scan --auto=yes --symlink=no 2>&1); do + IFS=$IFSOLD + set -- $line + shift + + case "$@" in + + 'No arrays found in config file'*) + # no point in carrying on. + shift + log_problem "no $*" + exit 0 + ;; + + 'Unknown keyword'*) + # warn only + if [ -x $(command -v logger >/dev/null) ]; then + logger -t mdadm -p syslog.warning -- "$*" + elif [ -w /dev/console ]; then + echo "mdadm: $*" > /dev/console + else + echo "mdadm: $*" >&2 + fi + ;; + + *' is already active.') + log_dev 0 $1 "already running" + ;; + + *'has been started with '[[:digit:]]*' drive'*' (out of '[[:digit:]]*') and '[[:digit:]]*' spare'*'.') + log_dev 0 $1 "initialising [$6/${10%).}]" + ;; + + *'has been started with '[[:digit:]]*' drive'*' (out of '[[:digit:]]*').') + log_dev 0 $1 "degraded [$6/${10%).}]" + ;; + + *'has been started with '[[:digit:]]*' drive'*'.') + log_dev 0 $1 "started [$6/$6]" + ;; + + *'assembled from '[[:digit:]]*' drive'*' - not enough to start the array.') + log_dev 1 $1 "not enough devices" + ;; + + 'no devices found for '*) + log_dev 1 $5 "no devices found" + ;; + + 'failed to RUN_ARRAY '*': Input/output error') + log_dev 1 ${4%:} "RUN_ARRAY input/output error" + ;; + + *) :;; + esac + done + ret=$? + + log_action_begin_msg "Generating udev events for MD arrays" + for uevent in /sys/block/md*/uevent; do + sentinel=${uevent#/sys/block/}; sentinel=${sentinel%/uevent}-uevent + test -e ${STATEDIR:-/doesnotexist}/$sentinel && continue + test -w $uevent || continue + echo add > $uevent + test -d "${STATEDIR:-}" && : > $STATEDIR/$sentinel + done + log_action_end_msg 0 + + [ $ret -ne 0 ] && exit $ret + + else + log_problem "no $CONFIG file" + fi + else + log_notice "disabled in $DEBIANCONFIG" + fi + ;; + + stop) + PREFIX="Stopping MD array" + + if is_true $AUTOSTART; then + if [ ! -f /proc/mdstat ]; then + log_problem "no MD subsystem loaded" + exit 0 + fi + + # ugly hack because shell sucks + IFSOLD=${IFS:-} + IFS=' +' + set +e + for line in $($MDADM --stop --scan 2>&1); do + set -e + IFS=$IFSOLD + set -- $line + shift + + case "$@" in + + 'Unknown keyword'*) + # warn only + if [ -x $(command -v logger >/dev/null) ]; then + logger -t mdadm -p syslog.warning -- "$*" + elif [ -w /dev/console ]; then + echo "mdadm: $*" > /dev/console + else + echo "mdadm: $*" >&2 + fi + ;; + + 'stopped '*) + log_dev 0 $2 stopped + ;; + + 'fail to stop array '*': Device or resource busy') + log_dev 1 ${5%:} busy + ;; + + *) :;; + esac + done || exit $? + + rm -rf ${STATEDIR:-} + + else + log_notice "disabled in $DEBIANCONFIG" + fi + ;; + + restart|force-reload) + ${0:-} stop + ${0:-} start + ;; + + reload) + PREFIX="Reloading MD array" + log_notice "never anything to do" + ;; + + *) + echo "Usage: ${0:-} {start|stop|restart}" >&2 + exit 1;; + +esac + +exit 0 --- mdadm-2.6.2.orig/debian/mdadm.lintian-overrides +++ mdadm-2.6.2/debian/mdadm.lintian-overrides @@ -0,0 +1 @@ +mdadm: virtual-package-depends-without-real-package-depends recommends: mail-transport-agent --- mdadm-2.6.2.orig/debian/mdadm.preinst +++ mdadm-2.6.2/debian/mdadm.preinst @@ -0,0 +1,36 @@ +#!/bin/sh +# Copyright © martin f. krafft +# Distributed under the terms of the Artistic Licence 2.0 +# +# $Id: mdadm.preinst 290 2006-12-19 08:18:50Z madduck $ +# + +set -eu + +case "$1" in + + upgrade|install) + + # migrate old configuration from *way back then* + DEBIANCONFIG=/etc/default/mdadm + OLDCONFIG=/etc/mdadm/debian.conf + if [ -s $OLDCONFIG ] && [ ! -f $DEBIANCONFIG ]; then + mv $OLDCONFIG $DEBIANCONFIG + fi + + # save the v1 output of -Es just in case we need it for upgrades + MDADM=/sbin/mdadm + if [ -x "$MDADM" ] && [ -n "${2:-}" ] && \ + dpkg --compare-versions $2 lt 2; then + echo DEVICE partitions > /var/backups/mdadm-Es_v1.dump + $MDADM -Esc /var/backups/mdadm-Es_v1.dump >> /var/backups/mdadm-Es_v1.dump || : + fi + ;; + + *) :;; +esac + +# See #369953 +set +u +#DEBHELPER# +set -u --- mdadm-2.6.2.orig/debian/initramfs/script.local-top +++ mdadm-2.6.2/debian/initramfs/script.local-top @@ -0,0 +1,117 @@ +#!/bin/sh +# +# Copyright © 2006 Martin F. Krafft +# based on the scripts in the initramfs-tools package. +# released under the terms of the Artistic Licence. +# +# $Id: script.local-top 322 2007-05-05 14:14:40Z madduck $ +# + +set -eu + +PREREQ="udev_helper" + +prereqs() +{ + echo "$PREREQ" +} + +case ${1:-} in + prereqs) + prereqs + exit 0 + ;; +esac + +. /scripts/functions + +if [ -e /scripts/local-top/md ]; then + log_warning_msg "old md initialisation script found, getting out of its way..." + exit 1 +fi + +MDADM=/sbin/mdadm +[ -x "$MDADM" ] || exit 0 + +verbose() +{ + case "$quiet" in y*|Y*|1|t*|T*) + return 1;; + *) + return 0;; + esac +} + +MD_DEVS=all +MD_MODULES='linear multipath raid0 raid1 raid456 raid5 raid6 raid10' +[ -s /conf/md.conf ] && . /conf/md.conf + +verbose && log_begin_msg Loading MD modules +for module in ${MD_MODULES:-}; do + if modprobe --syslog "$module"; then + verbose && log_success_msg "loaded module ${module}." + else + log_failure_msg "failed to load module ${module}." + fi +done +log_end_msg + +if [ ! -f /proc/mdstat ]; then + verbose && panic "cannot initialise MD subsystem (/proc/mdstat missing)" + exit 1 +fi + +# handle /dev/md/X nodes +mkdir --parent /dev/md + +CONFIG=/etc/mdadm/mdadm.conf +# in case the hook failed to install a configuration file, this is our last +# attempt... the "emergency procedure"... +if [ ! -e $CONFIG ]; then + log_warning_msg "missing mdadm.conf file, trying to create one..." + mkdir -p ${CONFIG%/*} + echo DEVICE partitions > $CONFIG + $MDADM --examine --scan >> $CONFIG + if [ -s $CONFIG ]; then + verbose && log_success_msg "mdadm.conf created." + else + verbose && log_failure_msg "could not create mdadm.conf, the boot will likely fail." + fi + MD_DEVS=all +fi + +# prevent writes/syncs so that resuming works (#415441). +echo 1 > /sys/module/md_mod/parameters/start_ro + +if [ "$MD_DEVS" = all ]; then + + verbose && log_begin_msg "Assembling all MD arrays" + extra_args='' + [ -n "$MD_HOMEHOST" ] && \ + extra_args="--homehost='$MD_HOMEHOST' --auto-update-homehost" + if $MDADM --assemble --scan --run --auto=yes $extra_args; then + verbose && log_success_msg "assembled all arrays." + else + log_failure_msg "failed to assemble all arrays." + fi + verbose && log_end_msg + +elif [ "$MD_DEVS" != none ]; then + for dev in $MD_DEVS; do + + verbose && log_begin_msg "Assembling MD array $dev" + if $MDADM --assemble --run --auto=yes $dev; then + verbose && log_success_msg "started $dev" + else + log_failure_msg "failed to start $dev" + fi + verbose && log_end_msg + + done +fi + +verbose && log_begin_msg "Executing udevtrigger again" +/sbin/udevtrigger +verbose && log_end_msg + +exit 0 --- mdadm-2.6.2.orig/debian/initramfs/hook +++ mdadm-2.6.2/debian/initramfs/hook @@ -0,0 +1,279 @@ +#!/bin/sh +# +# Copyright © 2006 Martin F. Krafft +# based on the scripts in the initramfs-tools package. +# released under the terms of the Artistic Licence. +# +# $Id: hook 290 2006-12-19 08:18:50Z madduck $ +# + +set -eu + +PREREQ="" + +prereqs() +{ + echo "$PREREQ" +} + +case ${1:-} in + prereqs) + prereqs + exit 0 + ;; +esac + +is_true() +{ + case "${1:-}" in + [Yy]es|[Yy]|1|[Tt]rue|[Tt]) return 0;; + *) return 1; + esac +} + +write() +{ + local PREFIX; PREFIX=$1; shift + echo "${PREFIX}: mdadm: $@" >&2 +} + +info() +{ + is_true ${VERBOSE:-false} && write I "$@" || : +} + +warn() +{ + write W "$@" +} + +err() +{ + write E "$@" +} + +if [ -e /usr/share/initramfs-tools/hooks/md ]; then + warn "initramfs md hook still present, stepping out of its way." >&2 + warn "Please see /usr/share/doc/mdadm/README.initramfs-transition ." >&2 + exit 0 +fi + +if [ -e /etc/initramfs-tools/hooks/md ]; then + warn "I found /etc/initramfs-tools/hooks/md, which may conflict" >&2 + warn "with this version of mdadm. Please see /usr/share/doc/mdadm/README.mdrun" >&2 + warn "and /usr/share/initramfs-tools/hooks/mdadm for reference and update" >&2 + warn "(or remove) the file." >&2 + exit 0 +fi + +MDADM=/sbin/mdadm +[ -x "$MDADM" ] || exit 0 + +[ -r /usr/share/initramfs-tools/hook-functions ] || exit 0 +. /usr/share/initramfs-tools/hook-functions + +# copy the binary as early as possible +copy_exec $MDADM /sbin + +# copy all modules into the initramfs, just for safety. +# we copy raid456 / raid5+raid6 because the hook script just won't do +# anything when the module cannot be found. +modules="linear multipath raid0 raid1 raid456 raid5 raid6 raid10" +for mod in $modules; do manual_add_modules $mod; done + +# read in the configuration +CONFIG=/etc/mdadm/mdadm.conf +ALTCONFIG=/etc/mdadm.conf +[ ! -f $CONFIG ] && [ -f $ALTCONFIG ] && CONFIG=$ALTCONFIG || : + +DEBIANCONFIG=/etc/default/mdadm +INITRDSTART=all +[ -s $DEBIANCONFIG ] && . $DEBIANCONFIG +[ -z "$INITRDSTART" ] && INITRDSTART=none + +DESTMDADMCONF=$DESTDIR/etc/mdadm/mdadm.conf +DESTCONFIG=$DESTDIR/conf/md.conf + +# save the homehost for now, even if we don't use it yet +if [ -f $CONFIG ]; then + homehost="$(sed -ne 's,^[[:space:]]*HOMEHOST[[:space:]]*,,p' $CONFIG)" +fi +if [ -z "${homehost:-}" ] || [ "${homehost:-}" = '' ]; then + homehost="$(hostname)" +fi +echo "MD_HOMEHOST='$homehost'" > $DESTCONFIG + +install_config() +{ + # install the configuration file + mkdir -p ${2%/*} + # only copy ARRAY and DEVICE lines, and merge continuation lines into one + sed -e :a -re '$!N;s/\n[[:space:]]+/ /;ta' -ne '/^(ARRAY|DEVICE)/P;D' $1 > $2 +} + +if [ ! -f $CONFIG ]; then + # there is no configuration file, so let's create one + + if /usr/share/mdadm/mkconf generate $CONFIG; then + # all is well + install_config $CONFIG $DESTMDADMCONF + info "auto-generated the mdadm.conf configuration file." >&2 + else + # we failed to auto-generate, so let the emergency procedure take over + warn "failed to auto-generate the mdadm.conf file." >&2 + warn "please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz ." >&2 + fi + +else + + use_temp=0 + if [ -e /var/lib/mdadm/CONF-UNCHECKED ]; then + # the file comes from an old installation and hence is not guaranteed to + # work. We thus better create one and start all arrays to be sure. + + warn "unchecked configuration file: $CONFIG" >&2 + warn "please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz ." >&2 + + use_temp=1 + elif ! grep -q '^ARRAY' $CONFIG; then + # the file defines no ARRAYs. We better create a temporary file to be + # sure. + + warn "$CONFIG defines no arrays." >&2 + use_temp=1 + + else + # this is the ideal case + install_config $CONFIG $DESTMDADMCONF + info "using configuration file: $CONFIG" >&2 + fi + + if [ $use_temp -eq 1 ]; then + mkdir --parents ${DESTMDADMCONF%/*} + tmpfile="${DESTMDADMCONF}.tmp" + if /usr/share/mdadm/mkconf > $tmpfile; then + # all is well, we now have a temporary configuration file + info "auto-generated temporary mdadm.conf configuration file." >&2 + install_config $tmpfile $DESTMDADMCONF + else + # stuff's really broke, as we failed to generate a temporary file. + # let's hope the unchecked file works, provided it contains at least one + # ARRAY statement... + warn "failed to auto-generate temporary mdadm.conf file." >&2 + if grep -q '^ARRAY' $CONFIG; then + warn "using the unchecked file and hoping for the best..." >&2 + install_config $CONFIG $DESTMDADMCONF + fi + fi + rm -f $tmpfile + fi + +fi + +# if at this point, $DESTMDADMCONF does not exist or it does not contain any +# ARRAY statements, we must let the initramfs handle stuff. +if [ ! -f $DESTMDADMCONF ]; then + warn "no configuration file available." >&2 + warn "falling back to emergency procedure in initramfs." >&2 + exit 0 +elif ! grep -q '^ARRAY' $DESTMDADMCONF; then + warn "no arrays defined in configuration file." >&2 + warn "falling back to emergency procedure in initramfs." >&2 + exit 0 +else + # obtain dev:level pairs from config file, honouring multiline entries + devpairs="$( + while read line; do + case "$line" in + (ARRAY*) :;; + (*) continue;; + esac + for atom in $line; do + case "$atom" in + (/dev*) dev=$atom;; + (level=*) level=${atom#level=};; + (*) :;; + esac + done + [ -n "${dev:-}" ] || continue + echo -n "${dev}:" + if [ -n "${level:-}" ]; then + echo -n "$level" + else + echo -n "$($MDADM --detail $dev | sed -rne 's,[[:space:]]+Raid Level : ,,p')" + fi + echo -n ' ' + done < $DESTMDADMCONF)" +fi + +uniquify() +{ + for i in $@; do echo "$i"; done | sort -u +} + +if [ "$INITRDSTART" != none ] && [ -n "$devpairs" ]; then + echo "MD_DEVPAIRS='${devpairs% }'" >> $DESTCONFIG + + devs=''; levels='' + for i in $devpairs; do + dev=${i%:*} + level=${i##*:} + case "$INITRDSTART" in + all|*${dev}*) + devs="${devs:+$devs }$dev" + levels="${levels:+$levels }$level" + ;; + *) :;; + esac + done + + for i in $INITRDSTART; do + case "$INITRDSTART" in all|none|'') break;; *) :;; esac + case "$devs" in + *${i}*) continue;; + *) :;; + esac + + warn "I am supposed to start $i from the initial ramdisk," >&2 + warn "yet I cannot find the array in the configuration file." >&2 + warn "I am thus reverting to starting all arrays." >&2 + INITRDSTART=all + break + done + + echo "MD_LEVELS='$levels'" >> $DESTCONFIG + if [ "$INITRDSTART" = all ]; then + echo "MD_DEVS=all" >> $DESTCONFIG + else + echo "MD_DEVS='$devs'" >> $DESTCONFIG + fi + + # raid4 is handled by raid5 + modules="$(echo $levels | sed -e 's,raid4,raid5,g')" + + # if raid456 module is present, use it for raid[456] + modprobe --set-version="$version" --show-depends raid456 >/dev/null 2>&1 \ + && modules="$(echo $modules | sed -e 's,raid[456],raid456,g')" + + modules="$(uniquify $modules | tr '\n' ' ')" + echo "MD_MODULES='${modules% }'" >> $DESTCONFIG + + if [ "$INITRDSTART" = all ]; then + info "will start all available MD arrays from the initial ramdisk." >&2 + else + for i in $devs; do + info "will start MD array $i from the initial ramdisk." >&2 + done + fi + +else + echo "MD_DEVS=none" >> $DESTCONFIG + echo "MD_MODULES=''" >> $DESTCONFIG + info "no MD arrays will be started from the initial ramdisk." >&2 +fi + +# only output this on Debian systems +[ -s /etc/default/mdadm ] && \ + info 'use `dpkg-reconfigure --priority=low mdadm` to change this.' >&2 + +exit 0 --- mdadm-2.6.2.orig/debian/mdadm.logcheck.ignore.server +++ mdadm-2.6.2/debian/mdadm.logcheck.ignore.server @@ -0,0 +1,22 @@ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md driver [.[:digit:]]+ MAX_MD_DEVS=[[:digit:]]+, MD_SB_DISKS=[[:digit:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: bitmap version [.[:digit:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+ stopped\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+ still in use\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: cannot remove active disk [[:alnum:]]+ from md[[:digit:]]+ \.\.\. ?$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: raid([01456]|456|10) personality registered for level ([01456]|10)$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: syncing RAID array md[[:digit:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: md[[:digit:]]+: sync done\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: minimum _guaranteed_ reconstruction speed: [[:digit:]]+ KB/sec/disc\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: using maximum available idle IO bandwidth \(but not more than [[:digit:]]+ KB/sec\) for reconstruction\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: delaying resync of md[[:digit:]]+ until md[[:digit:]]+ has finished resync \(they share one or more physical units\)$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: using [[:digit:]]+k window, over a total of [[:digit:]]+ blocks\.$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: (un)?bind<[^>]+>$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: md: export_rdev\([^)]+\)$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: raid[[:digit:]]+: raid set [[:alnum:]]+ active with [[:digit:]]+ out of [[:digit:]]+ mirrors$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel: RAID([01456]|10) conf printout:$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+---( [wrf]d:[[:digit:]]+){2,3}$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:[[:space:]]+disk [[:digit:]]+,( wo:[[:digit:]]+,)? o:[[:digit:]]+, dev:[[:alnum:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm: Rebuild((Start|Finish)ed|[2468]0) event detected on md device /dev/[-_./[:alnum:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm: SpareActive event detected on md device /dev/[-_./[:alnum:]]+, component device /dev/[-_./[:alnum:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm: (New|Degraded)Array event detected on md device /dev/[-_./[:alnum:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm: DeviceDisappeared event detected on md device /dev/[-_./[:alnum:]]+$ --- mdadm-2.6.2.orig/debian/watch +++ mdadm-2.6.2/debian/watch @@ -0,0 +1,4 @@ +version=3 +http://www.cse.unsw.edu.au/~neilb/source/mdadm/mdadm-([.[:digit:]]+).tgz + +# $Id: watch 89 2006-08-08 09:33:05Z madduck $ --- mdadm-2.6.2.orig/debian/README.recipes +++ mdadm-2.6.2/debian/README.recipes @@ -0,0 +1,148 @@ +mdadm recipes +============= + +The following examples/recipes may help you with your mdadm experience. I'll +leave it as an exercise to use the correct device names and parameters in each +case. You can find pointers to additional documentation in the README.Debian +file. + +Enjoy. Submissions welcome. + +The latest version of this document is available here: + http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/README.recipes?op=file&rev=0&sc=0 + +0. create a new array +~~~~~~~~~~~~~~~~~~~~~ + mdadm --create -l1 -n2 -x1 /dev/md0 /dev/sd[abc]1 # RAID 1, 1 spare + mdadm --create -l5 -n3 -x1 /dev/md0 /dev/sd[abcd]1 # RAID 5, 1 spare + mdadm --create -l6 -n4 -x1 /dev/md0 /dev/sd[abcde]1 # RAID 6, 1 spare + +1. create a degraded array +~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --create -l5 -n3 /dev/md0 /dev/sda1 missing /dev/sdb1 + mdadm --create -l6 -n4 /dev/md0 /dev/sda1 missing /dev/sdb1 missing + +2. assemble an existing array +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --assemble --auto=yes /dev/md0 /dev/sd[abc]1 + + # if the array is degraded, it won't be started. use --run: + mdadm --assemble --auto=yes --run /dev/md0 /dev/sd[ab]1 + + # or start it by hand: + mdadm --run /dev/md0 + +3. assemble all arrays in /etc/mdadm/mdadm.conf +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --assemble --auto=yes --scan + +4. assemble a dirty degraded array +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --assemble --auto=yes --force /dev/md0 /dev/sd[ab]1 + mdadm --run /dev/md0 + +4b. assemble a dirty degraded array at boot-time +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + If the array is started at boot time by the kernel (partition type 0xfd), + you can force-assemble it by passing the kernel boot parameter + + md-mod.start_dirty_degraded=1 + +5. stop arrays +~~~~~~~~~~~~~~ + mdadm --stop /dev/md0 + + # to stop all arrays in /etc/mdadm/mdadm.conf + mdadm --stop --scan + +6. hot-add components +~~~~~~~~~~~~~~~~~~~~~ + # on the running array: + mdadm --add /dev/md0 /dev/sdc1 + # if you add more components than the array was setup with, additional + # components will be spares + +7. hot-remove components +~~~~~~~~~~~~~~~~~~~~~~~~ + # on the running array: + mdadm --fail /dev/md0 /dev/sdb1 + # if you have configured spares, watch /proc/mdstat how it fills in + mdadm --remove /dev/md0 /dev/sdb1 + +8. hot-grow a RAID1 by adding new components +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + # on the running array, in either order: + mdadm --grow -n3 /dev/md0 + mdadm --add /dev/md0 /dev/sdc1 + # note: without growing first, additional devices become spares and are + # *not* synchronised after the add. + +9. hot-shrink a RAID1 by removing components +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --fail /dev/md0 /dev/sdc1 + mdadm --remove /dev/md0 /dev/sdc1 + mdadm --grow -n2 /dev/md0 + +10. convert existing filesystem to RAID 1 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + # The idea is to create a degraded RAID 1 on the second partition, move + # data, then hot add the first. This seems safer to me than simply to + # force-add a superblock to the existing filesystem. + # + # Assume /dev/sda1 holds the data (and let's assume it's mounted on + # /home) and /dev/sdb1 is empty and of the same size... + # + mdadm --create /dev/md0 -l1 -n2 /dev/sdb1 missing + mkfs -t /dev/md0 + mount /dev/md0 /mnt + tar -cf- -C /home . | tar -xf- -C /mnt -p + # consider verifying the data + umount /home + umount /mnt + mount /dev/md0 /home # also change /etc/fstab + mdadm --add /dev/md0 /dev/sda1 + +10b. convert existing filesystem to RAID 1 in-place +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + In-place conversion of /dev/sda1 to /dev/md0 is effectively + mdadm --create /dev/md0 -l1 -n2 /dev/sda1 missing + however, do NOT do this, as you risk filesystem corruption. + + If you need to do this, first unmount and shrink the filesystem by + a megabyte (if supported). Then run the above command, then (optionally) + again grow the filesystem as much as possible. + + Do make sure you have backups. If you do not yet, consider method (10) + instead (and make backups anyway!). + +11. convert existing filesystem to RAID 5/6 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + # See (10) for the basics. + mdadm --create /dev/md0 -l5 -n3 /dev/sdb1 /dev/sdc1 missing + #mdadm --create /dev/md0 -l6 -n4 /dev/sdb1 /dev/sdc1 /dev/sdd1 missing + mkfs -t /dev/md0 + mount /dev/md0 /mnt + tar -cf- -C /home . | tar -xf- -C /mnt -p + # consider verifying the data + umount /home + umount /mnt + mount /dev/md0 /home # also change /etc/fstab + mdadm --add /dev/md0 /dev/sda1 + +12. change the preferred minor of an MD array (RAID) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + # you need to manually assemble the array to change the preferred minor + # if you manually assemble, the superblock will be updated to reflect + # the preferred minor as you indicate with the assembly. + # for example, to set the preferred minor to 4: + mdadm --assemble /dev/md4 /dev/sd[abc]1 + + # this only works on 2.6 kernels, and only for RAID levels of 1 and above. + # for other MD arrays, you need to specify --update explicitly: + mdadm --assemble --update=super-minor /dev/md4 /dev/sd[abc]1 + + # see also item 12 in the FAQ contained with the Debian package. + + -- martin f. krafft Fri, 06 Oct 2006 15:39:58 +0200 + +$Id: README.recipes 253 2006-10-31 13:29:35Z madduck $ --- mdadm-2.6.2.orig/debian/mdadm.postrm +++ mdadm-2.6.2/debian/mdadm.postrm @@ -0,0 +1,36 @@ +#! /bin/sh +# Copyright © 2001,2002 Mario Jou/3en +# Copyright © 2006 Martin F. Krafft +# Distributable under the terms of the GNU GPL version 2. +# +# $Id: mdadm.postrm 271 2006-11-11 19:14:36Z madduck $ +# + +set -eu + +case "${1:-}" in + remove) + if command -v update-initramfs >/dev/null 2>&1; then + echo "W: mdadm: I'll update the initramfs, but if you need MD to boot" >&2 + echo "W: mdadm: with initramfs, you'll be screwed!" >&2 + update-initramfs -u -k all + fi + ;; + + purge) + GEN_SENTINEL=/var/lib/mdadm/mdadm.conf-generated + if [ -r $GEN_SENTINEL ]; then + rm -f "$(sed -rne 's,[[:xdigit:]]+ ,,p' $GEN_SENTINEL)" + fi + rm -f /etc/default/mdadm /etc/mdadm.conf /etc/mdadm/mdadm.conf + rm -rf /var/lib/mdadm + ;; + + *) :;; +esac + +# just in case somebody actually purges mdadm, we need this to make debconf +# (added by dh_installdebconf) behave. See #369953 +set +u +#DEBHELPER# +set -u --- mdadm-2.6.2.orig/debian/mdadm.manpages +++ mdadm-2.6.2/debian/mdadm.manpages @@ -0,0 +1,5 @@ +mdadm.8 +md.4 +mdadm.conf.5 +debian/mdrun.8 +debian/mdadm-startall.8 --- mdadm-2.6.2.orig/debian/control +++ mdadm-2.6.2/debian/control @@ -0,0 +1,32 @@ +Source: mdadm +Section: admin +Priority: optional +Maintainer: Debian mdadm maintainers +Uploaders: martin f. krafft , Mario Joussen +Build-Depends: debhelper (>= 5), po-debconf, dpatch, groff-base, docbook-to-man +Standards-Version: 3.7.2 +XS-Vcs-Svn: svn://svn.debian.org/pkg-mdadm/mdadm/trunk + +Package: mdadm +Architecture: any +Depends: ${shlibs:Depends}, makedev, ${misc:Depends}, lsb-base (>= 3.1-6), debconf (>= 1.4.72) +Recommends: mail-transport-agent, module-init-tools +Replaces: mdctl +Conflicts: mdctl (<< 0.7.2), raidtools2 (<< 1.00.3-12.1), initramfs-tools (<< 0.65) +Description: tool to administer Linux MD arrays (software RAID) + mdadm is a program that can be used to create, manage, and monitor MD + arrays (e.g. software RAID, multipath devices). + . + This package automatically configures mdadm to assemble arrays during the + system startup process. If not needed, this functionally can be disabled. + +Package: mdadm-udeb +Section: debian-installer +XC-Package-Type: udeb +Architecture: any +Depends: ${shlibs:Depends} +Description: tool to administer Linux MD arrays (software RAID) + mdadm is a program that can be used to create, manage, and monitor MD + arrays (e.g. software RAID, multipath devices). + . + mdadm-udeb is a minimal package used by the debian-installer. --- mdadm-2.6.2.orig/debian/po/vi.po +++ mdadm-2.6.2/debian/po/vi.po @@ -0,0 +1,305 @@ +# Vietnamese Translation for mdadm. +# Copyright © 2006 Free Software Foundation, Inc. +# Clytie Siddall , 2005-2006. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm 2.5.3.git200608202239-6\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-30 20:40+0930\n" +"Last-Translator: Clytie Siddall \n" +"Language-Team: Vietnamese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=1; plural=0;\n" +"X-Generator: LocFactoryEditor 1.6fc1\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Các mảng MD cần thiết cho hệ thống tập tin gốc:" + +# Variable: don't translate/Biến: đừng dịch +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Hãy nhập danh sách các thiết bị (định giá»›i bằng dấu cách) hay « all » (tất " +"cả) hay « none » (không có gì). Có thể bá» phần « /dev/ » Ä‘i trÆ°á»›c, chỉ nhập " +"(v.d.) « md0 md1 » hay « md/1 md/d0 »." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "để sá»­ dụng ná»™i bá»™ — chỉ cần thiết mô tả dài." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Nếu hệ thống này có hệ thống tập tin gốc nằm trên mảng MD (RAID), nó cần " +"phải được khởi chạy sá»›m trong dãy khởi Ä‘á»™ng. Còn nếu hệ thống tập tin gốc " +"nằm trên khối tin hợp lý (LVM) lần lượt nằm trên MD, má»i mảng hợp thành cần " +"phải được khởi chạy." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Nếu bạn biết chính xác những mảng nào cần thiết để kích hoạt hệ thống tập " +"tin gốc, và bạn muốn hoãn việc khởi chạy các mảng khác tá»›i má»™t Ä‘iểm sau " +"trong dãy khởi Ä‘á»™ng, hãy nhập vào đây các mảng cần khởi chạy. Hoặc nhập « " +"all » (tất cả) để khởi chạy Ä‘Æ¡n giản tất cả các mảng. " + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Nếu bạn không cần hoặc muốn khởi chạy mảng nào cho hệ thống tập tin gốc, hãy " +"bá» trống câu trả lá»i này (hoặc nhập « none » [không có]). TrÆ°á»ng hợp này có " +"thể xảy ra nếu bạn á»­ dụng khả năng khởi Ä‘á»™ng tá»± Ä‘á»™ng hạt nhân (kernel " +"autostart), hoặc không cần mảng nào để khởi Ä‘á»™ng máy tính." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Gặp lá»—i: nút thiết bị không tồn tại" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Gặp lá»—i: không phải là má»™t thiết bị khối" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Gặp lá»—i: không phải là má»™t mảng MD" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Gặp lá»—i: mảng không được liệt kê trong tập tin cấu hình « mdadm.conf »" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "" +"Tiếp tục vá»›i việc khởi chạy các mảng không được liệt kê trong tập tin cấu " +"hình « mdadm.conf » không?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"Mảng bạn đã xác định (${array}) không được liệt kê trong tập tin cấu hình " +"${config}. Vì vậy nó không thể được khởi chạy trong khi khởi Ä‘á»™ng, nếu bạn " +"không sá»­a tập tin cấu hình và tạo lại Ä‘Ä©a RAM đầu tiên." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Hãy tham chiếu đến tài liệu Äá»c Äi « /usr/share/doc/mdadm/README.upgrading-" +"2.5.3.gz » nếu bạn định tiếp tục." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Cảnh báo này chỉ là thích hợp nếu bạn cần thiết mảng được khởi chạy từ Ä‘Ä©a " +"RAM đầu tiên, để có thể khởi Ä‘á»™ng được. Nếu bạn sá»­ dụng khả năng khởi chạy " +"tá»± Ä‘á»™ng hạt nhân (kernel autostart), hoặc không cần mảng nào được khởi chạy " +"càng sá»›m khi nạp Ä‘Ä©a RAM đầu tiên, bạn Ä‘Æ¡n giản có thể tiếp tục lại. Hoặc " +"chá»n không tiếp tục, và nhập « none » (không có) khi được nhắc nhập những " +"mảng nào cần khởi chạy từ Ä‘Ä©a RAM đầu tiên." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Bạn có muốn khởi chạy tá»± Ä‘á»™ng các mảng MD không?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Má»™t khi hệ thống cÆ¡ bản được kích hoạt, mdadm có khả năng khởi chạy má»i mảng " +"MD (RAID) được xác định trong tập tin cấu hinh « /etc/mdadm/mdadm.conf », mà " +"chÆ°a được khởi chạy. Nếu bạn đã không biên dịch khả năng há»— trợ Ä‘a thiết bị " +"(MD) vào hạt nhân và nhãn má»i phân vùng là phần của mảng MD vá»›i kiểu « 0xfd " +"» (vì chúng và chỉ chúng sẽ được khởi chạy tá»± Ä‘á»™ng bởi hạt nhân), trÆ°á»ng hợp " +"này rất có thể là Ä‘iá»u bạn muốn." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "" +"mdadm có nên chạy việc kiểm tra thừa hàng tháng trên những mảng MD không?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Nếu hạt nhân há»— trợ (≥2.6.14), mdadm có thể kiểm tra theo chu kỳ tình thừa " +"của các mảng MD (RAID). Tiến trình này có thể chiếm nhiá»u tài nguyên hệ " +"thống, phụ thuá»™c vào thiết lập, nhÆ°ng nó có thể giúp đỡ ngăn cản trÆ°á»ng hợp " +"mất dữ liệu (ít có). Ghi chú rằng việc kiểm tra này là chỉ Ä‘á»c, nếu không " +"gặp lá»—i; còn nếu gặp lá»—i, mdadm sẽ thá»­ sá»­a chữa, mà có thể gây ra truy cập " +"ghi vào vật chứa." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"Giá trị mặc định, nếu được bật, là chạy những việc kiểm tra vào ngày hôm Chủ " +"Nhật thứ nhất của má»—i tháng, vào lúc 01:06 giá» (giá» ti)." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Bạn có muốn khởi chạy trình ná»n theo dõi MD không?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"Trình ná»n theo dõi MD (RAID) gởi thÆ° thông báo hưởng ứng sá»± kiện MD quan " +"trá»ng (v.d. Ä‘Ä©a bị há»ng). Rất có thể là bạn nên bật chạy nó." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "NgÆ°á»i nhận thÆ° thông báo :" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Hãy nhập địa chỉ thÆ° của ngÆ°á»i dùng nên nhận thÆ° thông báo vá» sá»± kiện MD " +"quan trá»ng nhÆ° vậy." + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "Hãy khởi Ä‘á»™ng siêu khối nếu bạn sá»­ dụng lại Ä‘Ä©a cứng." + +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "CẢNH BÃO : nếu bạn Ä‘ang sá»­ dụng Ä‘Ä©a cứng nào chứa siêu khối RAID từ bản " +#~ "cài đặt trÆ°á»›c nằm trong mảng RAID khác nhau, bạn CẦN PHẢI làm số không " +#~ "má»—i siêu khối _trÆ°á»›c_ khi kích hoạt tính năng khởi chạy tá»± Ä‘á»™ng." + +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "Äể làm nhÆ° thế, đừng khởi chạy tá»± Ä‘á»™ng những thiết bị RAID. TrÆ°á»›c tiên, " +#~ "hãy làm số không siêu khối (« mdadm --zero-superblock /dev/mdX »). Sau " +#~ "đó, chạy lệnh « dpkg-reconfigure mdadm » để kích hoạt tính năng khởi chạy " +#~ "tá»± Ä‘á»™ng." + +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "Tùy chá»n bạn có khả năng khởi chạy các mảng khác (những mảng không phải " +#~ "cần thiết cho hệ thống tập tin gốc) vào lúc sau trong dãy khởi Ä‘á»™ng. Làm " +#~ "nhÆ° thế sẽ cho bạn Ä‘á»™ Ä‘iá»u khiển hÆ¡n vá»›i các mảng bằng tập tin cấu hình " +#~ "mdadm. Tuy nhiên, có thể là an toàn hÆ¡n để khởi chạy má»i mảng vào lúc " +#~ "khởi Ä‘á»™ng." + +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "Nếu bạn chá»n tá»± Ä‘á»™ng khởi Ä‘á»™ng thiết bị RAID, khi hệ thống khởi Ä‘á»™ng, nó " +#~ "tá»± Ä‘á»™ng phát hiện và tập hợp các thiết bị RAID. Bạn chỉ nên sá»­ dụng tùy " +#~ "chá»n này nếu đã biên dịch trình há»— trợ thiết bị md là má»™t mô-Ä‘un. Nếu đã " +#~ "biên dịch nó vào hạt nhân bạn, thì hạt nhân sẽ tá»± Ä‘á»™ng khởi Ä‘á»™ng, vì vậy " +#~ "bạn không nên chá»n tùy chá»n này." + +#~ msgid "" +#~ "When the RAID monitor daemon runs, email notifications are sent when a " +#~ "disk belonging to a RAID array fails or changes its status for some " +#~ "reason." +#~ msgstr "" +#~ "Khi trình ná»n (dæmon) theo dõi RAID chạy thì nó gá»­i thông báo qua thÆ° má»—i " +#~ "lúc má»™t Ä‘Ä©a thuá»™c vá» má»™t mảng RAID có há»ng hóc hoặc thay đổi trạng thái " +#~ "vì má»™t lý do nào đó," --- mdadm-2.6.2.orig/debian/po/gl.po +++ mdadm-2.6.2/debian/po/gl.po @@ -0,0 +1,244 @@ +# Galician translation of mdadm's debconf templates +# This file is distributed under the same license as the mdadm package. +# Jacobo Tarrio , 2007. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2007-02-24 16:04+0100\n" +"Last-Translator: Jacobo Tarrio \n" +"Language-Team: Galician \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Arrays MD necesarios para o sistema de ficheiros raíz" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Introduza unha lista de dispositivos separados por espazos, \"all\" (todos) " +"ou \"none\" (ningún). Pode omitir o \"/dev/\" do principio e introducir só, " +"por exemplo, \"md0 md1\" ou \"md/1 md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "para uso interno - só se precisa da descrición longa." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Se o seu sistema ten o sistema de ficheiros raíz nun array MD (RAID), hai " +"que o iniciar no principio da secuencia de inicio. Se o seu sistema de " +"ficheiros raíz está nun volume lóxico (LVM) que está nun MD, hai que iniciar " +"os arrays constituíntes." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Se sabe exactamente que arrays son necesarios para erguer o sistema de " +"ficheiros raíz, e se quere pospor o inicio dos demáis arrays ata un punto " +"posterior da secuencia de inicio, introduza aquí os arrays a iniciar. " +"Alternativamente, introduza \"all\" para iniciar tódolos arrays dispoñibles." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Se non quere ou precisa de iniciar ningún array para o sistema de ficheiros " +"raíz, deixe a resposta en branco (ou introduza \"none\"). Este pode ser o " +"caso se está a empregar o autoinicio do núcleo ou non precisa de ningún " +"array para o inicio." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Houbo un erro: o nodo do dispositivo non existe" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Houbo un erro: non é un dispositivo de bloques" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Houbo un erro: non é un array MD" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Houbo un erro: o array non figura no ficheiro mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "¿Iniciar os arrays que non figuran en mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"O array que especificou (${array}) non figura no ficheiro de configuración " +"${config}. Polo tanto, non se pode arrincar no inicio do sistema, a menos " +"que corrixa o ficheiro de configuración e volva crear o disco RAM inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Consulte /usr/share/doc/mdadm/README.upgrading-2.5.3.gz se quere continuar." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Este aviso só é relevante se precisa de iniciar arrays desde o disco RAM " +"inicial para poder iniciar o sistema. Se emprega autoinicio do núcleo ou non " +"precisa de iniciar arrays tan pronto como se cargue o disco RAM inicial, " +"pode continuar. De xeito alternativo, escolla non continuar e introduza " +"\"none\" cando se lle pregunte que arrays quere iniciar do disco RAM inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "¿Quere iniciar os arrays MD automaticamente?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Despois do inicio do sistema base, mdadm pode iniciar tódolos arrays MD " +"(RAIDs) especificados en /etc/mdadm/mdadm.conf que non estean aínda " +"iniciados. A menos que teña o soporte de dispositivos múltiples (MD) " +"compilado no núcleo e teña tódalas particións marcadas coma parte de arrays " +"MD de tipo 0xfd (xa que esas, e só esas, as ha iniciar automaticamente o " +"núcleo), isto é, probablemente, o que quere." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "" +"¿Debería mdadm facer comprobacións mensuais de redundancia dos arrays MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Se o seu núcleo ten soporte para iso (>> 2.6.14), mdadm pode facer " +"comprobacións periódicas de redundancia dos seus arrays MD (RAIDs). Este " +"pode ser un proceso intensivo en recursos, dependendo da configuración, pero " +"pode axudar a evitar algúns casos raros de perdas de datos. Teña en conta " +"que esta é unha comprobación de só lectura a menos que se atopen erros; se " +"se atopan erros, mdadm ha tratar de os arranxar, o que pode producir accesos " +"de escritura aos soportes." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"A opción por defecto, se se activa, é facer as comprobacións o primeiro " +"domingo de cada mes ás 01:16." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "¿Quere iniciar o servizo de monitorización de MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"O servizo de monitorización de MD (RAID) envía avisos por email en resposta " +"a eventos importantes de MD (coma fallos nos discos). Seguramente queira " +"activalo." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Destinatario para os avisos por email:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Introduza o enderezo de email do usuario que debe recibir os avisos por " +"email de eventos importantes de MD." --- mdadm-2.6.2.orig/debian/po/pt.po +++ mdadm-2.6.2/debian/po/pt.po @@ -0,0 +1,249 @@ +# Portuguese translation for mdadm debconf messages. +# Copyright (C) 2007 Pedro Ribeiro +# This file is distributed under the same license as the mdadm package. +# Pedro Ribeiro , 2007 +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm 2.5.6\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2007-02-18 10:58+0100\n" +"Last-Translator: Pedro Ribeiro \n" +"Language-Team: Portuguese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Poedit-Language: Portuguese\n" +"X-Poedit-Country: PORTUGAL\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Grupos MD necessários para o sistema de ficheiros raiz:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Por favor, introduza uma lista de dispositivos separados por espaços, 'all' " +"ou 'none'. Pode omitir o '/dev/' inicial e introduzir apenas por ex. \"md0 " +"md1\", ou \"md/1 md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "para uso interno - apenas a descrição longa é necessária" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Se o seu sistema tiver o sistema de ficheiros de raiz num grupo MD (RAID) " +"necessita de ser iniciado mais cedo na sequência de arranque. Se o seu " +"sistema de ficheiros de raiz estiver num volume lógico (LVM) que está no MD, " +"todos os grupos constituintes necessitam de ser iniciados." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Se souber exactamente que grupos são necessários para iniciar o sistema de " +"ficheiros raiz, e quiser adiar o inicio de todos os outros grupos para mais " +"tarde no processo de arranque, introduza os grupos aqui. Alternativamente, " +"introduza 'all' para iniciar todos os grupos disponíveis." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Se não necessita ou deseja iniciar grupos para o sistema de ficheiros raiz, " +"deixe a resposta em branco (ou introduza 'none'). Isto vale no caso de usar " +"o auto-arranque do kernel ou não necessitar de grupos para o arranque do " +"sistema." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Ocorreu um erro: o nó do dispositivo não existe" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Ocorreu um erro: não é um dispositivo de bloco" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Ocorreu um erro: não é um grupo MD" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Ocorreu um erro: o grupo não está listado no ficheiro mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Continuar a iniciar grupos não listados no mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"O grupo especificado (${array}) não está listado no ficheiro de configuração " +"(${config}). Portanto, não pode ser iniciado durante o processo de arranque, " +"a não ser que corrija o ficheiro de configuração e recrie o ramdisk inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Por favor leia o ficheiro /usr/share/doc/mdadm/README.upgrading-2.5.3.gz se " +"quiser continuar." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Este aviso só é relevante se houver necessidade de iniciar grupos a partir " +"do ramdisk durante o arranque do sistema. Se usar o auto-arranque do kernel, " +"ou não necessitar de iniciar os grupos tão cedo no processo de arranque do " +"sistema, pode apenas continuar. Em alternativa, escolha não continuar e " +"introduza 'none' quando perguntado sobre quais grupos iniciar a partir do " +"ramdisk inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Quer iniciar os grupos MD automaticamente?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Após o arranque do sistema de base, o mdadm pode iniciar todos os grupos MD " +"(RAIDs) especificados em /etc/mdadm/mdadm.conf, que ainda não tiverem sido " +"iniciados. A não ser que tenha compilado o suporte para dispositivos " +"múltiplos (MD) no kernel e marcado todas as partições que são parte de " +"grupos MD com o tifo 0xfd (apenas estas serão iniciadas automaticamente pelo " +"kernel), isto é provavelmente o que quer." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "" +"O mdadm deve correr verificações de redundância nos grupos MD mensalmente?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Se o kernel suportar (>> 2.6.14), o mdadm pode verificar periodicamente a " +"redundância dos grupos MD (RAIDs). Isto pode ser um processo que requer " +"muitos recursos, dependendo da sua configuração, mas pode prevenir casos " +"raros de perda de dados. Notar que esta verificação é feita em modo de " +"leitura a não ser que sejam encontrados erros; se forem encontrados erros, o " +"mdadm tenta corrigi-los, o que pode resultar em acessos de escrita aos " +"discos." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"Se ligado, os testes são executados por omissão no primeiro Domingo de cada " +"mês à 01:06." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Quer iniciar o deamon de monitorização do MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"O monitor MD(RAID) envia notificações por email no caso de eventos " +"importantes (tais como falha de um disco). Provavelmente quer activar esta " +"opção." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Destinatário de email para notificações:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Por favor, introduza o endereço de email do destinatário das mensagens de " +"notificação dos eventos MD." --- mdadm-2.6.2.orig/debian/po/pt_BR.po +++ mdadm-2.6.2/debian/po/pt_BR.po @@ -0,0 +1,319 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-24 19:22-0300\n" +"Last-Translator: Felipe Augusto van de Wiel (faw) \n" +"Language-Team: l10n portuguese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"pt_BR utf-8\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Dispositivos MD necessários para o sistema de arquivos raiz:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Por favor, informe uma lista separada por espaços dos dispositivos, 'all' ou " +"'none'. Você pode omitir a parte inicial '/dev/' e apenas informar, por " +"exemplo, \"md0 md1\", ou \"md/1 md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "para uso interno - apenas a descrição longa é necessária." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Se o seu sistema tem o sistema de arquivos raiz em um dispositivo MD (RAID), " +"este precisa ser iniciado mais cedo durante a seqüência de inicialização. Se " +"o sistema de arquivos raiz está em um volume lógico (LVM), que está em um " +"MD, todos os dispositivos que o constituem precisam ser iniciados." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Se você sabe exatamente quais dispositivos são necessários para ativar o " +"sistema de arquivos raiz, e você deseja adiar o início de todos os outros " +"dispositivos para um ponto posterior na seqüência de inicialização, informe " +"os dispositivos a serem iniciados aqui. Como alternativa, informe 'all' para " +"simplesmente iniciar todos os dispositivos disponíveis." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Se você não precisa ou não quer iniciar quaisquer dispositivos para o " +"sistema de arquivos raiz, deixe a resposta em branco (ou informe 'none'). " +"Este pode ser o caso se você está usando \"kernel autostart\" ou não precisa " +"de quaisquer dispositivos para a inicialização." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Um erro ocorreu: o dispositivo (\"device node\") não existe" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Um erro ocorreu: não é um dispositivo de blocos" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Um erro ocorreu: não é um dispositivo MD" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Um erro ocorreu: dispositivo não listado no arquivo mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Continuar com o início de dispositivos não listados no mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"O dispositivo que você especificou (${array}) não está listado no arquivo de " +"configuração ${config}. Portanto não pode ser iniciado durante a " +"inicialização, a menos que você corrija o arquivo de configuração e recrie o " +"\"ramdisk\" inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Por favor, veja /usr/share/doc/mdadm/README.upgrading-2.5.3.gz se você " +"pretende continuar." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Este aviso só é relevante se você precisa de dispositivos que sejam " +"iniciados a partir do \"ramdisk\" inicial para que seja possível inicializar " +"o computador. Se você usa \"kernel autostarting\", ou não precisa de " +"quaisquer dispositivos sendo iniciados tão logo o \"ramdisk\" inicial seja " +"carregado, você pode simplesmente continuar. Alternativamente, escolha não " +"continuar e informe 'none' quando perguntado quais dispositivos iniciar a " +"partir do \"ramdisk\" inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Você deseja iniciar os dispositivos MD automaticamente?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Uma vez que o sistema básico esteja disponível, mdadm pode iniciar todos os " +"dispositivos MD (RAID) especificados em /etc/mdadm/mdadm.conf, que ainda não " +"foram iniciados. A menos que você tenha compilado o suporte a múltiplos " +"dispositivos (MD) embutido no kernel e marcado todas as partições que fazem " +"parte de dispositivos MD com o tipo 0xfd (como as únicas a serem iniciadas " +"automaticamente pelo kernel), você provavelmente quer ativar esta opção." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "O mdadm deve, mensalmente, executar checagens de redundância dos " +"dispositivos MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Se o seu kernel suporta isto (>> 2.6.14), mdadm pode periodicamente checar a " +"redundância dos seus dispositivos MD (RAIDs). Isto pode ser um processo " +"com uso intensivo dos recursos, dependendo da sua configuração, mas pode " +"ajudar a previnir casos raros de perdas de dados. Note que esta é uma " +"checagem somente-leitura a menos que erros sejam encontrados; se erros são " +"encontrados, mdadm tentará corrigí-los, o que poderá resultar em acesso de " +"escrita na mídia." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"O padrão, se ativado, é executar checagens no primeiro Domingo de cada mês " +"às 01:06 em ponto." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Você deseja iniciar o \"daemon\" de monitoramento MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"O \"daemon\" de monitoramento MD (RAID) envia e-mails de notificações em " +"resposta a eventos MD importantes (como uma falha de disco). Você " +"provavelmente quer habilitar esta opção." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Destinatário para os e-mails de notificações:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Por favor, informe o endereço de e-mail do usuário que deverá receber os e-" +"mails de notificações para estes eventos MD importantes." + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "Inicialize o superbloco caso você reutilize discos rígidos" + +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "AVISO! Se você estiver usando discos rígidos que já contêm superblocos " +#~ "RAID de instalações anteriores em \"arrays\" RAID diferentes, você DEVE " +#~ "zerar o superbloco *antes* de ativar o recurso de \"autostart\"." + +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "Para fazê-lo, não inicie os dispositivos RAID automaticamente. Primeiro, " +#~ "zere os superblocos (mdadm --zero-superblock /dev/mdX). Em seguida, use " +#~ "`dpkg-reconfigure mdadm` para reativar o recurso de \"autostart\"." + +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "Você tem a opção de iniciar todos os \"arrays\" (aqueles que não são " +#~ "necessários pelo sistema de arquivos raiz) posteriormente na seqüência de " +#~ "inicialização. Fazendo isto, você terá um controle maior sobre os \"arrays" +#~ "\" com o arquivo de configuração mdadm. No entanto, iniciar todos os " +#~ "\"arrays\" durante a inicialização pode ser mais seguro." + +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "Caso os dispositivos RAID sejam iniciados automaticamente, todos os " +#~ "dispositivos RAID serão detectados e montados automaticamente na " +#~ "inicialização do sistema operacional. Esta opção deverá ser usada somente " +#~ "caso o driver md esteja compilado como módulo. Caso o mesmo esteja " +#~ "compilado embutido em seu kernel, a inicialização automática será " +#~ "executada em tempo de inicialização pelo próprio kernel e, portanto, você " +#~ "não deverá e nem precisará escolher esta opção." + +#~ msgid "" +#~ "When the RAID monitor daemon runs, email notifications are sent when a " +#~ "disk belonging to a RAID array fails or changes its status for some " +#~ "reason." +#~ msgstr "" +#~ "Quando o daemon monitorador RAID é executado, notificações via e-mail são " +#~ "enviadas quando um disco pertencente a uma array RAID falha ou muda seu " +#~ "status por qualquer razão." + +#~ msgid "Which user should get the email notification?" +#~ msgstr "Qual usuário deve receber o e-mail de notificação ?" --- mdadm-2.6.2.orig/debian/po/nl.po +++ mdadm-2.6.2/debian/po/nl.po @@ -0,0 +1,255 @@ +# translation of mdadm_2.5.3_nl.po to Dutch +# translation of mdadm_2.5.2-2.po to Dutch +# translation of mdadm_nl.po to Dutch +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans# +# Developers do not need to manually edit POT or PO files. +# Frans Pop , 2005, 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm_2.5.3_nl\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-10-01 13:25+0200\n" +"Last-Translator: Frans Pop \n" +"Language-Team: Dutch \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.9.1\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Voor het basisbestandssysteem benodigde RAID-reeksen:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Geef de apparaatbestanden (gescheiden door spaties), 'all' (alle) of 'none' (geen) in. " +"U kunt volstaan met het ingeven van bijvoorbeeld \"md0 md1\" (en dus '/dev/...' " +"weglaten)." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "Voor intern gebruik - alleen de lange omschrijving wordt gebruikt." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Als het basisbestandssysteem van uw systeem zich op een RAID-volume bevindt, " +"dient dit vroeg in de opstartcyclus geactiveerd te worden. Als uw " +"basisbestandssysteem zich op een logisch volume (LVM) op RAID bevindt, " +"dienen alle betrokken reeksen geactiveerd te worden." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Als u exact weet welke reeksen nodig zijn om het basisbestandssysteem te " +"activeren en u het opstarten van alle overige reeksen wilt uitstellen tot later " +"in de opstartprocedure, geef deze dan hier in. Anders kunt u 'all' ingeven " +"om alle beschikbare reeksen te activeren." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Als u geen reeksen hoeft of wenst te activeren voor het basisbestandssysteem, laat dan " +"het antwoord leeg (of geef 'none' in). Dit kan het geval zijn als u \"kernel autostart\" gebruikt " +"of geen reeksen nodig heeft om op te starten." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Er is een fout opgetreden: apparaatbestand bestaat niet" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Er is een fout opgetreden: geen blokapparaat" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Er is een fout opgetreden: geen RAID reeks" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Er is een fout opgetreden: reeks komt niet voor in bestand mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Vervolgen met het opstarten van reeksen die niet in mdadm.conf voorkomen?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"De reeks die u heeft opgegeven (${array}) komt niet voor in het configuratiebestand " +"${config}. Tenzij u het configuratiebestand corrigeert en de initiële ramdisk opnieuw " +"creëert, kan de array tijdens het opstarten van het systeem niet worden geactiveerd." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Zie /usr/share/doc/mdadm/README.upgrading-2.5.3.gz als u van plan bent " +"verder te gaan." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Deze waarschuwing is alleen relevant als de reeksen geactiveerd moeten worden " +"vanuit een initiële ramdisk om het systeem te kunnen opstarten. Als u \"kernel " +"autostart\" gebruikt of er geen reeksen zijn die vanuit de initiële ramdisk gestart " +"moeten worden, kunt u gewoon doorgaan. Kies anders nu om niet door te gaan en " +"geef 'none' in bij de vraag welke reeksen vanuit de initiële ramdisk gestart " +"moeten worden." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "RAID-apparaten automatisch activeren?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Nadat het basissysteem eenmaal is opgestart, kan mdadm zorgdragen voor het " +"activeren van alle RAID-reeksen die voorkomen in /etc/mdadm/mdadm.conf, maar " +"nog niet zijn geactiveerd. Normaal gesproken zal u deze optie willen selecteren, " +"tenzij \"multiple device\" (MD) ondersteuning is meegecompileerd in de kernel en " +"alle partities die deel uitmaken van RAID-reeksen zijn gedefinieerd als type 0xfd " +"(aangezien ze alleen dan automatisch door de kernel gestart zullen worden)." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Maandelijkse redundantiecontrole van RAID-reeksen uitvoeren?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Als uw kernel dit ondersteunt (>> 2.6.14), kan mdadm periodiek de redundantie " +"van uw RAID reeksen controleren. Afhankelijk van uw configuratie kan dit een intensief " +"proces zijn, maar het kan wel helpen om uitzonderlijke gevallen van gegevensverlies " +"te voorkomen. Zolang geen fouten worden gevonden, zal het proces alleen gegevens " +"lezen; als echter wel fouten worden gevonden zal mdadm deze proberen te corrigeren." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"Standaard wordt de controle, indien geactiveerd, uitgevoerd om 01:06 op elke " +"eerste zondag van de maand." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Wilt u de achtergronddienst voor de RAID-monitor starten?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"De achtergronddienst voor de RAID-monitor stuurt per e-mail berichten bij " +"belangrijke gebeurtenissen die betrekking hebben op RAID (zoals een falende " +"harde schijf). Aangeraden wordt deze in te schakelen." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Adres voor e-mailberichten:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Geef het e-mailadres in van de gebruiker die een e-mailbericht dient te " +"ontvangen voor belangrijke gebeurtenissen met betrekking tot RAID." + --- mdadm-2.6.2.orig/debian/po/es.po +++ mdadm-2.6.2/debian/po/es.po @@ -0,0 +1,233 @@ +# mdadm po-debconf translation to spanish +# Copyright (C) 2006 Software in the Public Interest, SPI Inc. +# This file is distributed under the same license as the mdadm package. +# +# Changes: +# - Initial translation +# Javier Fernández-Sanguino , 2006 +# - Revision +# Fernando Cerezal +# +# +# Traductores, si no conoce el formato PO, merece la pena leer la +# documentación de gettext, especialmente las secciones dedicadas a este +# formato, por ejemplo ejecutando: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Equipo de traducción al español, por favor lean antes de traducir +# los siguientes documentos: +# +# - El proyecto de traducción de Debian al español +# http://www.debian.org/intl/spanish/ +# especialmente las notas y normas de traducción en +# http://www.debian.org/intl/spanish/notas +# +# - La guía de traducción de po's de debconf: +# /usr/share/doc/po-debconf/README-trans +# o http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Si tiene dudas o consultas sobre esta traducción consulte con el último +# traductor (campo Last-Translator) y ponga en copia a la lista de +# traducción de Debian al español () +# +# Notas: +# - 'array' no está traducido aán. La traducción como 'arreglo' suena +# fatal (y es poco conocida) [ cambiar cuando se cambie en d-i ] +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm 2.5.6-6\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-12-09 00:38+0100\n" +"Last-Translator: Javier Fernández-Sanguino \n" +"Language-Team: Debian Spanish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-15\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Arrays MD necesarios para el sistema de ficheros raíz:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +# No se traduce «all» y «none» porque no aparecen en la plantilla para traducir los elementos individuales +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "Introduzca una lista de dispositivos separados por espacios, «all» (todos) o «none» (ninguno). No tiene que preceder los nombres de dispositivos con «/dev», puede sólo introducir, por ejemplo: «md0 md1» o «md/1 md/d0»." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "para uso interno. Sólo se utiliza la descripción larga." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "Si su sistema tiene su sistema de ficheros raíz en un array MD (RAID) tiene que inicializarse antes durante de la secuencia de arranque. Si su sistema de ficheros raíz está en un volumen lógico (LVM) que está definido sobre un MD, todos los arrays que lo forman tienen que haberse inicializado." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "Introduzca los arrays a iniciar aquí, si sabe con exactitud cuáles son necesarios para arrancar el sistema de ficheros raíz y quiere posponer el arranque de todos los demás arrays a un punto posterior de la secuencia de arranque. También puede introducir «all» (todos) para, sencillamente, iniciar todos los arrays disponibles." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "Puede dejar la respuesta en blanco (o introducir «none») si no necesita o desea arrancar los arrays para el sistema de ficheros raíz. Este puede ser su caso si está utilizando el autoarranque del núcleo o no necesita ningún array para el arranque." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Se produjo un error: el nodo de dispositivo no existe" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Se produjo un error: no es un dispositivo de bloques" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Se produjo un error: no es un array MD" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Se produjo un error: el array no está en la lista definida en el archivo mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "¿Desea proceder con el arranque de los arrays no listados en mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "El array que ha especificado (${array}) no está listado en el fichero de configuración ${config}. Este array no podrá iniciarse durante el arranque del sistema a no ser que corrija el fichero de configuración y regenere el disco de ram inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "Si desea continuar debería leer «/usr/share/doc/mdadm/README.upgrading-2.5.3.gz»." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "Este aviso sólo es relevante si necesita que los arrays se inicien en el disco de RAM inicial para poder arrancar el sistema. Si utiliza el autoarranque del núcleo o no necesita que los arrays estén arrancados tan pronto como se cargue el disco de RAM, puede continuar simplemente. También puede decidir no continuar e introducir «none» cuando se le pregunte qué arrays deberían arrancarse del disco de RAM inicial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "¿Desea iniciar los arrays MD de forma automática?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "Mdadm puede iniciar todos los arrays MD (RAIDs) especificados en «/etc/mdadm/mdadm.conf» una vez se haya arrancado el sistema base, siempre que éstos no se hayan arrancado aún. Esto es probablemente lo que desea a no ser que haya compilado el soporte de dispositivos múltiples (MD, «multiple devices») en el núcleo y marcado todas las particiones que son parte de los arrays MD con el tipo «0xfd» (ya que éstas, y sólo éstas, se arrancarán de forma automática por el núcleo." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "¿Debería mdadm ejecutar comprobaciones de redundancia mensuales de los arrays MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "Mdadm puede comprobar de forma periódica la redundancia de sus arrays MD (RAIDs) si su núcleo lo soporta (si su versión es superior a la 2.6.14). Esto puede ser un proceso que consuma muchos recursos, dependiendo de su configuración, pero podría ayudar a prevenir casos raros de pérdida de datos. Tenga en cuenta que estas comprobaciones se hacen en modo lectura salvo que se detecten errores, en cuyo caso mdadm necesitará corregirlos, lo que significa que será necesario tener acceso de escritura a los medios físicos." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "Si se activa, por omisión, ejecutará las comprobaciones el primer Domingo de cada mes a las 01:06 am." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "¿Desea arrancar el demonio de monitorización MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "El demonio de monitorización MD (RAID) envía notificaciones por correo electrónico cuando se producen eventos importantes en los dispositivos MD (como pueda ser el caso de un fallo de un disco). Posiblemente desee habilitarlo." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Destinatario de las notificaciones por correo:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "Introduzca la dirección de correo electrónico del usuario que debería recibir las notificaciones por correo de eventos relevantes en los dispositivos MD." --- mdadm-2.6.2.orig/debian/po/templates.pot +++ mdadm-2.6.2/debian/po/templates.pot @@ -0,0 +1,201 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=CHARSET\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" --- mdadm-2.6.2.orig/debian/po/de.po +++ mdadm-2.6.2/debian/po/de.po @@ -0,0 +1,274 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-10-01 15:47+0200\n" +"Last-Translator: Mario Joussen \n" +"Language-Team: German \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-1\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Für das Wurzeldateisystem benötigte RAID Verbünde:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "Bitte geben Sie eine leerzeichenseparierte Geräteliste oder \"all\" ein. Sie können das führende \"/dev/\" weglassen und z.B. nur \"md0 md1\" oder \"md/1 md/d0\" eingeben." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "für internen Gebrauch - es wird nur die ausführliche Beschreibung benötigt." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Wenn das Wurzeldateisystem Ihres Systems auf einem RAID Verbund liegt, muß " +"es früh während des Bootvorgangs gestartet werden. Wenn sich Ihr " +"Wurzeldateisystem auf einem logischen Laufwerk (LVM) befindet, das sich " +"wiederum auf RAID Verbünden befindet, müssen alle zugehörigen Verbünde " +"gestartet werden." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "Wenn Sie genau wissen welche Verbünde benötigt werden, um das Wurzeldateisystem zu starten, und Sie den Start der anderen Verbünde auf einen späteren Zeitpunkt in der Bootreihenfolge verschieben wollen, geben Sie die zu startenden Verbünde hier ein. Alternativ geben Sie \"all\" ein, um alle verfügbaren Verbünde zu starten." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "Falls Sie keine RAID Verbünde für das Wurzeldateisystem benötigen oder starten wollen, lassen Sie die Antwort leer (oder geben 'none' ein). Dies könnte der Fall sein, wenn Sie entweder die Autostartfunktion des Kernels verwenden oder keine RAID Verbünde zum Booten benötigen." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Ein Fehler ist aufgetreten: Geräteknoten existiert nicht" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Ein Fehler ist aufgetreten: kein Blockgerät" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Ein Fehler ist aufgetreten: kein RAID Verbund" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Ein Fehler ist aufgetreten: Verbund nicht in der Datei mdadm.conf aufgeführt" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Mit dem Starten der nicht in mdadm.conf aufgeführten Verbünde fortfahren?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "Der von Ihnen angegebene Verbund (${array}) ist in der Konfigurationsdatei ${config} nicht aufgeführt. Deshalb kann er während des Bootvorgangs nicht gestartet werden, es sei denn Sie korrigieren die Konfigurationsdatei und erzeugen die initiale Ramdisk neu." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "Bitte lesen Sie /usr/share/doc/mdadm/README.upgrading-2.5.3.gz falls Sie beabsichtigen fortzufahren." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "Diese Warnung ist nur von Bedeutung wenn Sie RAID Verbünde, die von der initialen Ramdisk gestartet werden, benötigen, um booten zu können. Falls Sie die Autostartfunktion des Kernels verwenden oder kein RAID Verbund zum frühen Zeitpunkt des Ladens der initialen Ramdisk gestartet werden muß, können Sie einfach fortfahren. Alternativ wählen Sie nicht fortfahren und geben 'none' ein, wenn Sie gefragt werden, welche RAID Verbünde von der initialen Ramdisk gestartet werden sollen." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Möchten Sie die RAID Verbünde automatisch starten?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "Sobald das Grundsystem hochgefahren ist, kann mdadm alle in /etc/mdadm/mdadm.conf angegebenen RAID Verbünde starten, die noch nicht gestartet worden sind. Falls Sie nicht die RAID Unterstützung in den Kernel einkompiliert haben und alle Partitionen, die zu einem RAID Verbund gehören, mit dem Typ 0xfd markiert haben (weil diese und nur diese automatisch vom Kernel gestartet werden), ist dies wahrscheinlich das, was Sie wollen." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Soll mdadm monatlich die Redundanzüberprüfung auf den RAID Verbünden ausführen?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "Falls Ihr Kernel es unterstützt (>> 2.6.14) kann mdadm regelmäßig die Redundanz Ihrer RAID Verbünde überprüfen. Dies kann abhängig von Ihrer Installation ein resourcenintensiver Vorgang sein, der aber helfen kann, seltene Fälle von Datenverlust zu vermeiden. Bemerken Sie bitte, daß diese Überprüfung nur lesend erfolgt, solange keine Fehler gefunden werden. Falls Fehler gefunden werden, wird mdadm versuchen diese zu beheben, was zu schreibendem Zugriff auf das Medium führen kann." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "Die Voreinstellung ist, falls eingeschaltet, die Überprüfung am ersten Sonntag jedes Monats um 01:06 Uhr durchzuführen." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Möchten Sie den RAID Überwachungsdämon starten?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"Der RAID Überwachungsdämon verschickt Benachrichtigungen als Reaktion auf " +"wichtige RAID Ereignisse (wie zum Beispiel Festplattenausfälle). Sie werden " +"diese Option wahrscheinlich aktivieren wollen." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Empfänger der Emailbenachrichtungen:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "Geben Sie bitte die Emailadresse des Benutzers an, der die Emailbenachrichtigung für wichtige RAID Ereignisse erhalten soll." + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "" +#~ "Initialisieren Sie den Superblock, wenn Sie Festplatten wieder verwenden." + +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "WARNUNG! Wenn Sie Festplatten verwenden, die bereits einen md Superblock " +#~ "von einer vorherigen Installation in einem anderen RAID Verbund besitzen, " +#~ "so MÜSSEN Sie diesen löschen, *bevor* Sie die Autostart Funktion " +#~ "aktivieren." + +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "Dazu starten Sie die RAID Laufwerke nicht automatisch und löschen dann " +#~ "erst den Superblock (mdadm --zero-superblock /dev/mdX). Danach können Sie " +#~ "mit \"dpkg-reconfigure mdadm\" die Autostart Funktion aktivieren." + +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "Sie haben die Option alle anderen Verbünde (diese die nicht für das " +#~ "Wurzeldateisystem benötigt werden) später während des Bootvorgangs zu " +#~ "starten. Damit haben Sie größere Kontrolle über die Verbünde mit Hilfe " +#~ "der mdadm Konfigurationsdatei. Es ist jedoch sicherer, alle Verbünde beim " +#~ "Booten zu starten." + +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "Wenn die RAID Laufwerke automatisch gestartet werden, werden alle RAID " +#~ "Laufwerke beim Systemstart automatisch gefunden und gestartet. Diese " +#~ "Option sollte nur benutzt werden, falls der md Treiber als Modul " +#~ "kompiliert wurde. Falls er in den Kernel einkompiliert wurde, führt der " +#~ "Kernel den automatischen Start beim Booten durch und Sie sollten diese " +#~ "Option deshalb nicht auswählen." + +#~ msgid "" +#~ "When the RAID monitor daemon runs, email notifications are sent when a " +#~ "disk belonging to a RAID array fails or changes its status for some " +#~ "reason." +#~ msgstr "" +#~ "Wird der RAID-Überwachungsdämon gestartet, so werden Email-" +#~ "Benachrichtigungen verschickt, falls ein zum RAID gehörendes Laufwerk " +#~ "ausfällt oder den Status ändert." --- mdadm-2.6.2.orig/debian/po/cs.po +++ mdadm-2.6.2/debian/po/cs.po @@ -0,0 +1,297 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-23 20:45+0200\n" +"Last-Translator: Miroslav Kure \n" +"Language-Team: Czech \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "MD pole vyžadovaná pro koÅ™enový souborový systém:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Zařízení zadejte jako mezerami oddÄ›lený seznam, případnÄ› 'all' nebo 'none'. " +"PoÄáteÄní '/dev/' můžete vynechat a zadat jen napÅ™. \"md0 md1\" nebo \"md/1 " +"md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "pro vnitÅ™ní použití - pouze kvůli zobrazení dlouhého popisu." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Pokud má váš systém svůj koÅ™enový souborový systém umístÄ›n na MD (RAID) " +"svazku, musí být tento spuÅ¡tÄ›n bÄ›hem zavádÄ›ní systému co nejdříve. Pokud se " +"váš koÅ™enový souborový systém nachází na logickém svazku LVM, který je " +"vytvoÅ™en nad MD polem, musí se spustit vÅ¡echna související pole." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Jestliže pÅ™esnÄ› víte, která pole jsou potÅ™eba pro pÅ™ipojení koÅ™enového " +"souborového systému a zároveň chcete pozdržet spuÅ¡tÄ›ní ostatních polí na " +"pozdÄ›jší dobu, zadejte zde prosím pole, která se mají spustit. Chcete-li " +"spustit vÅ¡echna dostupná pole, můžete zadat 'all'." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"NepotÅ™ebujete-li nebo nechcete-li spouÅ¡tÄ›t pole pro koÅ™enový souborový " +"systém, ponechte odpovÄ›Ä prázdnou, případnÄ› zadejte 'none'. To může nastat " +"tÅ™eba v případÄ›, že používáte automatický start přímo v jádÅ™e, nebo pokud k " +"zavedení systému žádná pole nepotÅ™ebujete." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Vyskytla se chyba: uzel zařízení neexistuje" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Vyskytla se chyba: není blokovým zařízením" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Vyskytla se chyba: není MD polem" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Vyskytla se chyba: pole není uvedeno v souboru mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "PokraÄovat ve spouÅ¡tÄ›ní polí neuvedených v mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"Zadané pole (${array}) není uvedeno v konfiguraÄním souboru ${config} a tím " +"pádem nemůže být spuÅ¡tÄ›no pÅ™i zavádÄ›ní systému. Napravit to můžete opravou " +"konfiguraÄního souboru a znovuvytvoÅ™ením poÄáteÄního ramdisku." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Hodláte-li pokraÄovat, pÅ™eÄtÄ›te si prosím /usr/share/doc/mdadm/README." +"upgrading-2.5.3.gz." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Toto varování je relevantní pouze pokud k zavedení systému potÅ™ebujete, aby " +"se pole spustila z poÄáteÄního ramdisku. Používáte-li automatické spouÅ¡tÄ›ní " +"přímo v jádÅ™e, nebo pokud nepotÅ™ebujete pouÅ¡tÄ›t žádná pole jeÅ¡tÄ› z " +"poÄáteÄního ramdisku, můžete jednoduÅ¡e pokraÄovat. Jinou možností je " +"nepokraÄovat dále a pÅ™i dotazu na seznam polí, která se mají spouÅ¡tÄ›t z " +"poÄáteÄního ramdisku, zadat 'none'." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Chcete spouÅ¡tÄ›t MD pole automaticky?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Po zavedení základního systému může mdadm spustit vÅ¡echna dosud nespuÅ¡tÄ›ná " +"MD (RAID) pole uvedená v souboru /etc/mdadm/mdadm.conf. Pokud nemáte " +"zakompilovanou podporu multiple device (MD) přímo v jádÅ™e (kdy se vÅ¡echna " +"MD pole oznaÄená typem oblasti 0xfd spustí zcela automaticky), pravdÄ›podobnÄ› " +"budete chtít tuto možnost povolit." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Má mdadm spouÅ¡tÄ›t mÄ›síÄní kontroly redundance MD polí?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Pokud to vaÅ¡e jádro podporuje (>> 2.6.14), může mdadm pravidelnÄ› kontrolovat " +"redundanci MD polí (RAIDů). Podle konfigurace poÄítaÄe to může být proces " +"velmi nároÄný na prostÅ™edky, ovÅ¡em může pÅ™edejít vzácným případům ztráty dat. " +"Pokud nejsou nalezeny chyby, používá tato kontrola v zásadÄ› jen Ätecí " +"operace. PÅ™i nalezení chyb se je mdadm pokusí opravit, což může znamenat " +"zápis na médium." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"Pokud kontroly povolíte, budou se dle výchozího nastavení spouÅ¡tÄ›t každou " +"první nedÄ›li v mÄ›síci v 01:06 ráno." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Chcete spustit daemon pro monitorování MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"Daemon pro monitorování MD (RAIDu) zasílá emailová upozornÄ›ní na významné MD " +"události, jako je selhání disku. Je rozumné tuto možnost povolit." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Příjemce emailových upozornÄ›ní:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Zadejte prosím emailovou adresu uživatele, který má dostávat emailová " +"upozornÄ›ní pÅ™i výskytu významných MD událostí." + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "PÅ™i znovupoužití starších disků inicializujte superblok" + +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "VAROVÃNÃ! Používáte-li pevné disky, které obsahují RAID superbloky z " +#~ "dřívÄ›jší instalace v jiném RAID poli, MUSÃTE vÅ¡echny superbloky pÅ™ed " +#~ "použitím automatického spouÅ¡tÄ›ní vynulovat." + +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "Chcete-li to provést, nespouÅ¡tÄ›jte RAID zařízení automaticky. Nejprve " +#~ "vynulujte superblok příkazem 'mdadm --zero-superblock /dev/mdX' a teprve " +#~ "poté můžete povolit automatické spouÅ¡tÄ›ní RAIDu příkazem 'dpkg-" +#~ "reconfigure mdadm'." + +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "VÅ¡echna ostatní pole (ta, která nejsou potÅ™eba pro koÅ™enový souborový " +#~ "systém) můžete spustit pozdÄ›ji. Pokud tak uÄiníte, budete mít v " +#~ "konfiguraÄním souboru mdadm nad poli vÄ›tší kontrolu. Na druhou stranu je " +#~ "spouÅ¡tÄ›ní vÅ¡ech polí hned na zaÄátku zavádÄ›ní o nÄ›co jistÄ›jší volbou." + +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "Jestliže jsou RAID zařízení spouÅ¡tÄ›na automaticky, jsou vÅ¡echna RAID " +#~ "zařízení rozpoznána a poskládána automaticky pÅ™i zavádÄ›ní systému. Tuto " +#~ "volbu byste mÄ›li použít pouze v případÄ›, že jste ovladaÄ md zakompilovali " +#~ "jako modul. Pokud jste jej zakompilovali přímo do jádra, o automatické " +#~ "spuÅ¡tÄ›ní se postará samotné jádro a tedy tuto možnost nepotÅ™ebujete." --- mdadm-2.6.2.orig/debian/po/POTFILES.in +++ mdadm-2.6.2/debian/po/POTFILES.in @@ -0,0 +1 @@ +[type: gettext/rfc822deb] mdadm.templates --- mdadm-2.6.2.orig/debian/po/fr.po +++ mdadm-2.6.2/debian/po/fr.po @@ -0,0 +1,264 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +# Éric Madesclair , 2005, 2006. +# Florentin Duneau , 2006. +# Jean-Luc Coulon (f5ibh) , 2006. +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-30 17:56+0200\n" +"Last-Translator: Florentin Duneau \n" +"Language-Team: French \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=ISO-8859-15\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=(n > 1);\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "Ensembles MD requis par le système de fichiers racine :" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Veuillez indiquer une liste de périphériques, séparés par des espaces, " +"« all » ou « none ». Vous pouvez omettre « /dev/ » et simplement indiquer " +"par exemple, « md0 md1 » ou « md/1 md/d0 »." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "pour utilisation interne - seule la description longue est nécessaire" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"Si le système de fichiers racine se trouve sur un ensemble MD (RAID), il " +"doit être lancé au début de la procédure de démarrage. Si le système de " +"fichiers racine se trouve sur un volume logique (« LVM »), qui se trouve " +"aussi sur un volume MD, tous les composants de l'ensemble doivent être " +"démarrés." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"Si vous savez exactement quels sont les ensembles RAID nécessaires au " +"démarrage du système de fichiers racine et si vous souhaitez différer le " +"démarrage de tous les autres ensembles, veuillez les indiquer ici. Vous " +"pouvez aussi indiquer « all » pour démarrer tous les ensembles existants." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"Si vous n'avez pas besoin ou ne souhaitez pas démarrer d'ensemble RAID pour " +"le système de fichiers racine, veuillez laissez l'entrée vide (ou indiquez " +"« none »). Ceci peut être le cas si vous utilisez l'option autostart " +"démarrage ou si vous n'avez besoin d'aucun ensemble pour démarrer." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Erreur : périphérique inconnu" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Erreur : ce n'est pas un périphérique en mode bloc" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Erreur : ce n'est pas un ensemble RAID" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Erreur : ensemble non mentionné dans le fichier mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "" +"Faut-il continuer et démarrer les ensembles RAID non mentionnés dans " +"mdadm.conf ?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"L'ensemble (${array}) que vous avez spécifié n'est pas mentionné dans le " +"fichier de configuration ${config}. Il ne sera donc pas démarré à moins que " +"vous corrigiez le fichier de configuration et que vous génériez de nouveau " +"le disque mémoire initial (« ramdisk »)." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"Veuillez consulter /usr/share/doc/mdadm/README.upgrading-2.5.3.gz si vous " +"souhaitez continuer." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Cet avertissement n'a de signification que s'il est nécessaire que " +"l'ensemble RAID soit lancé à partir du disque mémoire initial afin de pouvoir " +"démarrer le système. Si vous utilisez le démarrage automatique par le noyau, " +"ou si vous n'avez pas besoin de lancer d'ensemble RAID en même temps que le " +"disque mémoire initial, vous pouvez simplement poursuivre. Vous pouvez aussi " +"choisir de ne pas poursuivre et entrer « none » lorsque vous sera demandé le " +"nom des ensembles RAID à démarrer à partir du disque mémoire initial." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Faut-il démarrer automatiquement les ensembles RAID ?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"Lorsque le système de base a démarré, mdadm peut démarrer tous les ensembles " +"(RAID) indiqués dans /etc/mdadm/mdadm.conf qui n'ont pas encore été démarrés. " +"Cela est recommandé, sauf si la gestion MD a été compilée dans le noyau et " +"que toutes les partitions faisant partie d'un ensemble RAID ont été marquées " +"avec le type 0xfd (car seul ce type de partition sera démarré automatiquement " +"par le noyau), ce qui est probablement ce que vous désirez." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Faut-il vérifier chque mois la redondance des ensembles RAID ?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"Si le noyau le gère (à partir de la version 2.6.14), mdadm peut vérifier " +"périodiquement la redondance des périphériques RAID. Cette action peut " +"demander beaucoup de ressources selon la configuration, mais cela aide à " +"prévenir les rares cas de pertes de données. Notez que ce test est réalisé " +"en lecture seule à moins que des erreurs ne soient rencontrées. Si des " +"erreurs sont détectées, mdadm essayera de les corriger, ce qui entraînera " +"des écritures sur le média." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"Par défaut, la vérification s'effectuera tous les premiers dimanche du mois " +"à 01 h 06." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Faut-il démarrer le démon de surveillance MD ?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"Le démon de surveillance MD envoie des notifications par courriel lors " +"d'importants événements MD (comme une panne de disque dur). Il est " +"recommandé de l'activer." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Destinataire des notifications par courriel :" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Veuillez indiquer l'adresse électronique de l'utilisateur qui doit recevoir " +"les notifications lors d'importants événements MD." --- mdadm-2.6.2.orig/debian/po/ru.po +++ mdadm-2.6.2/debian/po/ru.po @@ -0,0 +1,254 @@ +# translation of mdadm-2.5.3.git200608202239-6_ru.po to Russian +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans# +# Developers do not need to manually edit POT or PO files. +# +# Yuri Kozlov , 2006. +msgid "" +msgstr "" +"Project-Id-Version: mdadm_2.5.3.git200608202239-6\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-23 23:54+0400\n" +"Last-Translator: Yuri Kozlov \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"X-Generator: KBabel 1.11.2\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "MD маÑÑивы, нужные Ð´Ð»Ñ ÐºÐ¾Ñ€Ð½ÐµÐ²Ð¾Ð¹ файловой ÑиÑтемы:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"Введите ÑпиÑок уÑтройÑтв через пробел, Ñлово 'all' или 'none'. Ð’Ñ‹ можете не " +"указывать начальную чаÑÑ‚ÑŒ пути типа '/dev/', а проÑто вводить имена " +"уÑтройÑтв, например \"md0 md1\" или \"md/1 md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "Ð´Ð»Ñ Ð²Ð½ÑƒÑ‚Ñ€ÐµÐ½Ð½ÐµÐ³Ð¾ Ð¿Ð¾Ð»ÑŒÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ - нужно иÑпользовать только длинное опиÑание." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"ЕÑли в ÑиÑтеме ÐºÐ¾Ñ€Ð½ÐµÐ²Ð°Ñ Ñ„Ð°Ð¹Ð»Ð¾Ð²Ð°Ñ ÑиÑтема раÑположена на MD маÑÑиве (RAID), " +"он должен быть запущен в Ñамом начале процеÑÑа загрузки. ЕÑли ÐºÐ¾Ñ€Ð½ÐµÐ²Ð°Ñ " +"Ñ„Ð°Ð¹Ð»Ð¾Ð²Ð°Ñ ÑиÑтема раÑположена на логичеÑком томе (LVM), который раÑположен " +"на MD, то должны быть запущены вÑе компоненты маÑÑивов." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"ЕÑли вы точно знаете какие маÑÑивы требуютÑÑ Ð´Ð»Ñ Ð¿Ð¾Ð»ÑƒÑ‡ÐµÐ½Ð¸Ñ Ñ€Ð°Ð±Ð¾Ñ‚Ð¾ÑпоÑобной " +"корневой файловой ÑиÑтемы и хотите отложить запуÑк оÑтальных маÑÑивов на " +"более поздний момент в процеÑÑе загрузки, то введите их здеÑÑŒ. Иначе, введите " +"Ñлово 'all', чтобы проÑто запуÑтить вÑе доÑтупные маÑÑивы." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"ЕÑли вам Ñто не нужно, или вы хотите запуÑкать вÑе маÑÑивы Ð´Ð»Ñ ÐºÐ¾Ñ€Ð½ÐµÐ²Ð¾Ð¹ " +"файловой ÑиÑтемы, оÑтавьте Ñто поле пуÑтым (или введите Ñлово 'none'). " +"Этот вариант подходит, еÑли вы иÑпользуете автоматичеÑкий запуÑк " +"из Ñдра или еÑли Ð´Ð»Ñ Ð·Ð°Ð³Ñ€ÑƒÐ·ÐºÐ¸ маÑÑивы не нужны." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Произошла ошибка: нода узла не ÑущеÑтвует" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Произошла ошибка: уÑтройÑтво не ÑвлÑетÑÑ Ð±Ð»Ð¾Ñ‡Ð½Ñ‹Ð¼" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Произошла ошибка: Ñто не MD маÑÑив" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Произошла ошибка: маÑÑив не опиÑан в файле mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Продолжить запуÑк маÑÑивов не опиÑанных в mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"Указанный вами маÑÑив (${array}) не опиÑан в конфигурационном файле " +"${config}. ПоÑтому он не может быть запущен при Ñтарте машины, пока вы не " +"иÑправите конфигурационный файл и не переÑоздадите первоначальный ramdisk." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"ЕÑли вы намерены продолжить, прочитайте /usr/share/doc/mdadm/README." +"upgrading-2.5.3.gz." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"Данное предупреждение умеÑтно только, еÑли вам требуетÑÑ Ð·Ð°Ð¿ÑƒÑкать " +"маÑÑивы из первоначального ramdisk Ð´Ð»Ñ Ð·Ð°Ð³Ñ€ÑƒÐ·ÐºÐ¸ машины. ЕÑли вы иÑпользуете " +"автоматичеÑкий запуÑк из Ñдра или вам не нужны маÑÑивы Ð´Ð»Ñ Ð·Ð°Ð³Ñ€ÑƒÐ·ÐºÐ¸ на " +"Ñтапе загрузки первоначального ramdisk, вы можете проÑто продолжить. " +"Иначе, выберите не продолжать и введите 'none', когда вам предложат " +"выбрать маÑÑивы Ð´Ð»Ñ Ð·Ð°Ð¿ÑƒÑка из первоначального ramdisk." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "ЗапуÑкать MD маÑÑивы автоматичеÑки?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"ПоÑле Ñтарта базовой ÑиÑтемы mdadm может запуÑтить вÑе MD маÑÑивы (RAIDÑ‹), " +"указанные в файле /etc/mdadm/mdadm.conf, которые ещё не запущены. Ðужно " +"ответить утвердительно, еÑли вы не включили поддержку MD в Ñдре (в " +"противном Ñлучае Ñдро Ñамо выполнÑет автоматичеÑкий запуÑк MD маÑÑивов " +"из разделов Ñ Ñ‚Ð¸Ð¿Ð¾Ð¼ 0xfd (и только Ñ Ñтим))." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Должен ли mdadm запуÑкать ежемеÑÑчную проверку избыточноÑти на MD маÑÑивах?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"ЕÑли Ñто поддерживаетÑÑ Ñдром (>> 2.6.14), mdadm может периодичеÑки " +"проверÑÑ‚ÑŒ избыточноÑÑ‚ÑŒ MD маÑÑивов. Это может Ñтать реÑурÑоёмким " +"процеÑÑом в завиÑимоÑти от наÑтройки, но он может помочь предотвратить " +"редкие Ñлучаи потерь данных. Заметим, что пока не обнаружено ошибок, работа " +"ведётÑÑ Ð² режиме только чтение; еÑли обнаруживаетÑÑ Ð¾ÑˆÐ¸Ð±ÐºÐ°, mdadm попытаетÑÑ " +"иÑправить её, что может потребовать прав запиÑи на ноÑитель." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"ЕÑли ответить утвердительно, то по умолчанию проверка выполнÑетÑÑ Ð² первое " +"воÑкреÑенье каждого меÑÑца в 01:06." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "ЗапуÑкать демон-монитор MD?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"Демон-монитор MD (RAID) поÑылает почтовые ÑƒÐ²ÐµÐ´Ð¾Ð¼Ð»ÐµÐ½Ð¸Ñ Ð² Ñлучае " +"Ð²Ð¾Ð·Ð½Ð¸ÐºÐ½Ð¾Ð²ÐµÐ½Ð¸Ñ Ð²Ð°Ð¶Ð½Ñ‹Ñ… Ñобытий Ñ MD (таких как отказ диÑка). Лучше его включить." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Получатель уведомительных пиÑем:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"Введите Ð°Ð´Ñ€ÐµÑ Ñлектронной почты пользователÑ, который будет получать " +"почтовые ÑƒÐ²ÐµÐ´Ð¾Ð¼Ð»ÐµÐ½Ð¸Ñ Ð¾ важных изменениÑÑ… в ÑоÑтоÑнии MD." + --- mdadm-2.6.2.orig/debian/po/sv.po +++ mdadm-2.6.2/debian/po/sv.po @@ -0,0 +1,217 @@ +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# Developers do not need to manually edit POT or PO files. +# , fuzzy +# +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm 1.12.0-1\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-09-23 16:37+0100\n" +"Last-Translator: Daniel Nylander \n" +"Language-Team: Swedish \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=iso-8859-1\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "MD-kedjor som behövs för rotfilsystemet:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "Please enter a space-separated list of devices, 'all', or 'none'. You may omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "Ange en blankstegsseparerad lista på enheter, \"all\" eller \"none\". Du kan utesluta den inledande \"/dev\" och bara ange t.ex. \"md0 md1\", eller \"md/1 md/d0\"." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "för intern användning - endast den långa beskrivningen behövs." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "If your system has its root filesystem on an MD array (RAID), it needs to be started early during the boot sequence. If your root filesystem is on a logical volume (LVM), which is on MD, all constituent arrays need to be started." +msgstr "Om ditt system har sitt rotfilsystem på en MD-kedja (RAID) behöver den startas upp tidigt under uppstartssekvensen. Om ditt rotfilsystem finns på en logisk volym (LVM), vilket är på MD, behöver alla bestående kedjor startas." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "If you know exactly which arrays are needed to bring up the root filesystem, and you want to postpone starting all other arrays to a later point in the boot sequence, enter the arrays to start here. Alternatively, enter 'all' to simply start all available arrays." +msgstr "Om du vet exakt vilka kedjor som behövs för att ta upp rotfilsystemet, och du vill skjuta upp uppstarten för alla andra kedjor till en senaste tidspunkt i uppstartssekvens, ange vilka kedjor som ska starta här. Alternativt, ange \"all\" för att helt enkelt starta alla tillgängliga kedjor." + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "If you do not need or want to start any arrays for the root filesystem, leave the answer blank (or enter 'none'). This may be the case if you are using kernel autostart or do not need any arrays to boot." +msgstr "Om du inte behöver eller vill starta några kedjor för rotfilsystemet, lämna svaret blankt (eller ange \"none\"). Det kan vara så om du använder kärnans automatstart eller inte behöver några kedjor för att starta upp." + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "Ett fel inträffade: enhetsnoden finns inte" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "Ett fel inträffade: inte en blockenhet" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "Ett fel inträffade: inte en MD-kedja" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "Ett fel inträffade: kedjan är inte listad i filen mdadm.conf" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "Fortsätt med uppstarten av kedjor som inte är listade i mdadm.conf?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "The array you have specified (${array}) is not listed in the configuration file ${config}. Therefore it cannot be started during boot, unless you correct the configuration file and recreate the initial ramdisk." +msgstr "Kedjan du har angivit (${array}) är inte listad i konfigurationsfilen ${config}. Därför kan den inte startas under systemets uppstart, såvida du inte rättar till konfigurationsfilen och återskapar den initiala ramdisken." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend to continue." +msgstr "Referera till /usr/share/doc/mdadm/README.upgrading-2.5.3.gz om du tänker fortsätta." + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "This warning is only relevant if you need arrays to be started from the initial ramdisk to be able to boot. If you use kernel autostarting, or do not need any arrays to be started as early as the initial ramdisk is loaded, you can simply continue. Alternatively, choose not to continue and enter 'none' when prompted which arrays to start from the initial ramdisk." +msgstr "Den här varningen är endast relevant om du behöver kedjor som ska startas från den initiala ramdisken för att kunna starta upp systemet. Om du använder kärnans automatstart, eller inte behöver starta några kedjor så tidigt som när de initiala ramdisken läses in, kan du helt enkelt fortsätta. Alternativt, välj att inte fortsätta och ange \"none\" när frågan om vilka kedjor som ska startas från den initiala ramdisken ställs." + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "Vill du starta MD-kedjor automatiskt?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Once the base system has come up, mdadm can start all MD arrays (RAIDs) specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless you have compiled multiple device (MD) support into the kernel and marked all partitions part of MD arrays with type 0xfd (as those and only those will be started automatically by the kernel), this is probably what you want." +msgstr "När grundsystemet har startats upp kan mdadm starta alla MD-kedjor som har angivits i /etc/mdadm/mdadm.conf och som ännu inte har startats. Såvida du har byggt in stöd för multipla enheter (MD) i kärnan och markerat alla partitioner som del av MD-kedjor med typen 0xfd (och de och endast de kommer att startas upp automatiskt av kärnan), är antagligen detta något som du vill göra." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "Ska mdadm köra månatliga redundanskontroller av MD-kedjorna?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "If your kernel supports it (>> 2.6.14), mdadm can periodically check the redundancy of your MD arrays (RAIDs). This may be a resource-intensive process, depending on your setup, but it could help prevent rare cases of data loss. Note that this is a read-only check unless errors are found; if errors are found, mdadm will try to correct them, which may result in write access to the media." +msgstr "Om din kärna (>> 2.6.14) har stöd för det kan mdadm periodvis kontrollera redundansen för dina MD-kedjor (RAID). Det här kan vara en resurskrävande process, beroende på din konfiguration, men den kan hjälpa till att förhindra ovanliga fall av dataförluster. Observera att det är en skrivskyddad kontroll såvida inte fel påträffas; om fel hittas kan mdadm försöka att rätta till dem, vilket kan leda till skrivåtkomst till mediet." + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "The default, if turned on, is to run the checks on the first Sunday of every month at 01:06 o'clock." +msgstr "Standardvärdet, om påslagen, är att köra kontrollerna på den första söndagen i varje månad klockan 01.06." + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "Vill du starta MD-övervakningsdemonen?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "The MD (RAID) monitor daemon sends email notifications in response to important MD events (such as a disk failure). You probably want to enable it." +msgstr "MD-övervakningsdemonen (RAID) skickar e-postnotifieringar för viktiga MD-händelser (såsom ett diskfel). Du vill antagligen aktivera denna funktion." + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "Mottagare av e-postnotifieringar:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Please enter the email address of the user who should get the email notification for important MD events." +msgstr "Ange e-postadressen till den användare som ska ta emot e-postnotifieringar för dessa viktiga MD-händelser." + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "Initiera superblocket om du ?teranv?nder h?rddiskar" +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "VARNING! Om du anv?nder h?rddiskar som har RAID-superblock fr?n tidigare " +#~ "installationer i andra RAID-kedjor M?STE du nollst?lla superblocket " +#~ "*innan* du aktiverar autostartfunktionen." +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "F?r att g?ra detta, starta inte RAID-enheterna automatiskt. Nollst?ll f?" +#~ "rst superblocket (mdadm --zero-superblock /dev/mdX), anv?nd sedan \"dpkg-" +#~ "reconfigure mdadm\" f?r att ?teraktivera autostartfunktionen." +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "Du har alternativet att starta alla andra kedjor (de som inte beh?vs f?r " +#~ "rotfilsystemet) senare i uppstartssekvensen. Att g?ra det ger dig st?rre " +#~ "kontroll ?ver kedjorna med mdadms konfigurationsfil. Starta alla kedjor " +#~ "vid uppstart kan dock vara s?krare." +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "Om RAID-enheter startas automatiskt kommer alla RAID-enheter att uppt?" +#~ "ckas och s?ttas ihop automatiskt vid systemets uppstart. Denna funktion b?" +#~ "r bara anv?ndas om md-drivaren ?r byggd som en modul. Om den ?r inbyggd i " +#~ "din k?rna kommer den automatiska uppstarten att g?ras av k?rnan vid " +#~ "systemets uppstart och d?rf?r b?r du inte v?lja denna funktion h?r." +#~ msgid "" +#~ "When the RAID monitor daemon runs, email notifications are sent when a " +#~ "disk belonging to a RAID array fails or changes its status for some " +#~ "reason." +#~ msgstr "" +#~ "N?r RAID-?vervakningsdaemonen k?r kommer e-postnotifieringar att skickas " +#~ "n?r en disk som tillh?r en RAID-array fallerar eller ?ndrar status av n?" +#~ "gon anledning." + --- mdadm-2.6.2.orig/debian/po/ja.po +++ mdadm-2.6.2/debian/po/ja.po @@ -0,0 +1,303 @@ +# +# Translators, if you are not familiar with the PO format, gettext +# documentation is worth reading, especially sections dedicated to +# this format, e.g. by running: +# info -n '(gettext)PO Files' +# info -n '(gettext)Header Entry' +# +# Some information specific to po-debconf are available at +# /usr/share/doc/po-debconf/README-trans +# or http://www.debian.org/intl/l10n/po-debconf/README-trans +# +# Developers do not need to manually edit POT or PO files. +# +# +msgid "" +msgstr "" +"Project-Id-Version: mdadm 2.5.5-1\n" +"Report-Msgid-Bugs-To: pkg-mdadm-devel@lists.alioth.debian.org\n" +"POT-Creation-Date: 2006-09-16 13:03+0200\n" +"PO-Revision-Date: 2006-10-15 13:52+0900\n" +"Last-Translator: Hideki Yamane (Debian-JP) \n" +"Language-Team: Japanese \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "MD arrays needed for the root filesystem:" +msgstr "root ファイルシステムã«å¿…è¦ãª MD アレイ:" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "${msg}" +msgstr "${msg}" + +#. Type: string +#. Description +#: ../mdadm.templates:1001 +msgid "" +"Please enter a space-separated list of devices, 'all', or 'none'. You may " +"omit the leading '/dev/' and just enter e.g. \"md0 md1\", or \"md/1 md/d0\"." +msgstr "" +"デãƒã‚¤ã‚¹ã®ãƒªã‚¹ãƒˆã‚’スペースã§åŒºåˆ‡ã£ã¦å…¥åŠ›ã€ã‚ã‚‹ã„㯠'all' ã¾ãŸã¯ 'none' ã¨å…¥åŠ›ã—ã¦" +"ãã ã•ã„。å‰ã® '/dev/' ã‚’çœç•¥ã—ã¦ã€å˜ã« \"md0 md1\" ã‚ã‚‹ã„㯠\"md/1 md/d0\" ãªã©" +"ã¨ã—ã¦ã‚‚構ã„ã¾ã›ã‚“。" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "for internal use - only the long description is needed." +msgstr "内部ã§ã®åˆ©ç”¨ã«ã¤ã„㦠- ã§ã‚‚ã€é•·ã„説明ãŒå¿…è¦ã§ã™ã€‚" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If your system has its root filesystem on an MD array (RAID), it needs to be " +"started early during the boot sequence. If your root filesystem is on a " +"logical volume (LVM), which is on MD, all constituent arrays need to be " +"started." +msgstr "" +"ã‚ãªãŸã®ã‚·ã‚¹ãƒ†ãƒ ã§ root ファイルシステムを MD アレイ (RAID) 上ã«é…ç½®ã—ã¦ã„ã‚‹ãª" +"らã°ã€ãƒ–ートシーケンスã®åˆæœŸæ®µéšŽã§ MD アレイを開始ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚root ファイ" +"ルシステム㌠MD 上ã®è«–ç†ãƒœãƒªãƒ¥ãƒ¼ãƒ  (LVM) 上ã«ã‚ã‚‹å ´åˆã€æ§‹æˆã—ã¦ã„るアレイ全ã¦ã®" +"開始ãŒå¿…è¦ã§ã™ã€‚" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you know exactly which arrays are needed to bring up the root filesystem, " +"and you want to postpone starting all other arrays to a later point in the " +"boot sequence, enter the arrays to start here. Alternatively, enter 'all' to " +"simply start all available arrays." +msgstr "" +"ã©ã®ã‚¢ãƒ¬ã‚¤ãŒ root ファイルシステムã®ç«‹ã¡ä¸Šã’ã«å¿…è¦ã‹ã‚’正確ã«çŸ¥ã£ã¦ãŠã‚Šã€ãƒ–ート" +"シーケンスã®å¾Œã®æ™‚点ã¾ã§æ„図ã—ã¦ã„ã‚‹ã‚‚ã®ä»¥å¤–å…¨ã¦ã®ã‚¢ãƒ¬ã‚¤èµ·å‹•ã‚’é…らã›ãŸã„å ´åˆã€" +"ã“ã“ã§æœ€åˆã«èµ·å‹•ã™ã‚‹ã‚¢ãƒ¬ã‚¤ã‚’入力ã—ã¦ãã ã•ã„。ãã†ã§ãªã„å ´åˆã€'all' ã¨å…¥åŠ›ã—ã¦" +"å˜ã«å…¨ã¦ã®åˆ©ç”¨å¯èƒ½ãªã‚¢ãƒ¬ã‚¤ã‚’最åˆã«ç«‹ã¡ä¸Šã’ã¦ãã ã•ã„。" + +#. Type: text +#. Description +#: ../mdadm.templates:2001 +msgid "" +"If you do not need or want to start any arrays for the root filesystem, " +"leave the answer blank (or enter 'none'). This may be the case if you are " +"using kernel autostart or do not need any arrays to boot." +msgstr "" +"root ファイルシステムã®ãŸã‚ã«ã€ã©ã®ã‚¢ãƒ¬ã‚¤ã‚‚å¿…è¦ãªã„ã€ã‚ã‚‹ã„ã¯ã©ã®ã‚¢ãƒ¬ã‚¤ã‚‚èµ·å‹•ã—ãŸã" +"ã¯ç„¡ã„ã¨ã„ã†å ´åˆã¯ã€ç©ºç™½ã®ã¾ã¾ã« (ã‚ã‚‹ã„㯠'none' ã¨å…¥åŠ›) ã—ã¦ãã ã•ã„。" +"ã“ã‚Œã¯ã€ã‚«ãƒ¼ãƒãƒ«ã§è‡ªå‹•çš„ã«èµ·å‹•ã•ã‚Œã‚‹å ´åˆã‚„起動時ã«ã¯ã‚¢ãƒ¬ã‚¤ã¯ä¸è¦ã§ã‚ã‚‹ã¨ã„ã†" +"å ´åˆã§ã™ã€‚" + +#. Type: text +#. Description +#: ../mdadm.templates:3001 +msgid "An error occurred: device node does not exist" +msgstr "エラーãŒç™ºç”Ÿã—ã¾ã—ãŸ: デãƒã‚¤ã‚¹ãƒŽãƒ¼ãƒ‰ãŒå­˜åœ¨ã—ã¾ã›ã‚“" + +#. Type: text +#. Description +#: ../mdadm.templates:4001 +msgid "An error occurred: not a block device" +msgstr "エラーãŒç™ºç”Ÿã—ã¾ã—ãŸ: ブロックデãƒã‚¤ã‚¹ã§ã¯ã‚ã‚Šã¾ã›ã‚“" + +#. Type: text +#. Description +#: ../mdadm.templates:5001 +msgid "An error occurred: not an MD array" +msgstr "エラーãŒç™ºç”Ÿã—ã¾ã—ãŸ: MD アレイã§ã¯ã‚ã‚Šã¾ã›ã‚“" + +#. Type: text +#. Description +#: ../mdadm.templates:6001 +msgid "An error occurred: array not listed in mdadm.conf file" +msgstr "エラーãŒç™ºç”Ÿã—ã¾ã—ãŸ: mdadm.conf ファイルã«è¨˜è¿°ã•ã‚Œã¦ã„ãªã„アレイã§ã™" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "Proceed with starting arrays not listed in mdadm.conf?" +msgstr "mdadm.conf ã«è¨˜è¿°ã•ã‚Œã¦ã„ãªã„アレイã®èµ·å‹•ã‚’続行ã—ã¾ã™ã‹?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"The array you have specified (${array}) is not listed in the configuration " +"file ${config}. Therefore it cannot be started during boot, unless you " +"correct the configuration file and recreate the initial ramdisk." +msgstr "" +"指定ã—ãŸã‚¢ãƒ¬ã‚¤ (${array}) ã¯è¨­å®šãƒ•ã‚¡ã‚¤ãƒ« ${config} ã«è¨˜è¿°ã•ã‚Œã¦ã„ã¾ã›ã‚“。" +"ãã®ãŸã‚ã€è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«ã‚’修正ã—㦠initrd ã‚’å†ç”Ÿæˆã—ãªã‘ã‚Œã°ãƒ–ート時ã«èµ·å‹•ã§ãã¾ã›ã‚“。" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend " +"to continue." +msgstr "" +"続行ã—ãŸã„å ´åˆã¯ã€/usr/share/doc/mdadm/README.upgrading-2.5.3.gz " +"ã‚’å‚ç…§ã—ã¦ãã ã•ã„。" + +#. Type: boolean +#. Description +#: ../mdadm.templates:7001 +msgid "" +"This warning is only relevant if you need arrays to be started from the " +"initial ramdisk to be able to boot. If you use kernel autostarting, or do " +"not need any arrays to be started as early as the initial ramdisk is loaded, " +"you can simply continue. Alternatively, choose not to continue and enter " +"'none' when prompted which arrays to start from the initial ramdisk." +msgstr "" +"ã“ã®è­¦å‘Šã¯ã€ãƒ–ートã§ãるよã†ã«ã‚¢ãƒ¬ã‚¤ã‚’ initrd ã‹ã‚‰èµ·å‹•ã™ã‚‹å¿…è¦ãŒã‚ã‚‹å ´åˆã ã‘関係" +"ã—ã¾ã™ã€‚カーãƒãƒ«ã§è‡ªå‹•çš„ã«ã‚¢ãƒ¬ã‚¤ã‚’èµ·å‹•ã™ã‚‹ã‚ˆã†ã«ã—ã¦ã„ã‚‹å ´åˆã€ã‚ã‚‹ã„㯠initrd ãŒ" +"ロードã•ã‚Œã‚‹ç¨‹æ—©ã„段階ã§ã©ã®ã‚¢ãƒ¬ã‚¤ã‚‚èµ·å‹•ã—ãŸãã¯ãªã„å ´åˆã¯ãã®ã¾ã¾ç¶šè¡Œã§ãã¾ã™ã€‚" +"ä»–ã®é¸æŠžè‚¢ã¨ã—ã¦ã¯ã€èµ·å‹•ã®ç¶šè¡Œã‚’中止ã—ã€ã©ã®ã‚¢ãƒ¬ã‚¤ã‚’ initrd ã‹ã‚‰èµ·å‹•ã™ã‚‹ã‹ã‚’" +"å°‹ã­ã‚‰ã‚ŒãŸéš›ã« 'none' ã¨å…¥åŠ›ã—ã¾ã™ã€‚" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "Do you want to start MD arrays automatically?" +msgstr "MD アレイを自動的ã«èµ·å‹•ã—ã¾ã™ã‹?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:8001 +msgid "" +"Once the base system has come up, mdadm can start all MD arrays (RAIDs) " +"specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless " +"you have compiled multiple device (MD) support into the kernel and marked " +"all partitions part of MD arrays with type 0xfd (as those and only those " +"will be started automatically by the kernel), this is probably what you want." +msgstr "" +"一旦ベースシステムãŒèµ·å‹•ã™ã‚‹ã¨ã€mdadm 㯠/etc/mdadm/mdadm.conf ã§æŒ‡å®šã•ã‚ŒãŸ" +"ã¾ã èµ·å‹•ã—ã¦ã„ãªã„å…¨ã¦ã® MD アレイ (RAID) ã‚’èµ·å‹•ã§ãã¾ã™ã€‚複数ã®ãƒ‡ãƒã‚¤ã‚¹ (MD) " +"をサãƒãƒ¼ãƒˆã™ã‚‹ã‚ˆã†ã«ã‚«ãƒ¼ãƒãƒ«ã‚’コンパイルã—ã¦ãŠã‚Šã€MD アレイã®ã™ã¹ã¦ã®ãƒ‘ーティション" +"をパーティションタイプ 0xfd ã¨è¨­å®šã—ãªã„é™ã‚Šã€ã“れを推奨ã—ã¾ã™ (ã“ã®ã‚ˆã†ã«ã—ãŸå ´åˆã€" +"ãã—ã¦ã“ã®è¨­å®šã®å ´åˆã®ã¿ã€ã‚¢ãƒ¬ã‚¤ã¯è‡ªå‹•çš„ã«ã‚«ãƒ¼ãƒãƒ«ã‹ã‚‰èµ·å‹•ã•ã‚Œã¾ã™) 。" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "Should mdadm run monthly redundancy checks of the MD arrays?" +msgstr "mdadm ã¯ã€æ¯Žæœˆ MD アレイã®å†—長性ãƒã‚§ãƒƒã‚¯ã‚’è¡Œã„ã¾ã™ã‹?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"If your kernel supports it (>> 2.6.14), mdadm can periodically check the " +"redundancy of your MD arrays (RAIDs). This may be a resource-intensive " +"process, depending on your setup, but it could help prevent rare cases of " +"data loss. Note that this is a read-only check unless errors are found; if " +"errors are found, mdadm will try to correct them, which may result in write " +"access to the media." +msgstr "" +"カーãƒãƒ«ãŒã‚µãƒãƒ¼ãƒˆã—ã¦ã„ã‚‹å ´åˆ (2.6.14 以é™)ã€mdadm ã¯å®šæœŸçš„ã« MD アレイ (RAID) " +"ã®å†—長性ãƒã‚§ãƒƒã‚¯ã‚’ã™ã‚‹ã“ã¨ãŒå¯èƒ½ã§ã™ã€‚ã“ã‚Œã¯ã€è¨­å®šã«ä¾å­˜ã—ã¾ã™ãŒãƒªã‚½ãƒ¼ã‚¹ã‚’集中的ã«" +"使用ã™ã‚‹å‹•ä½œã§ã™ã€‚ã—ã‹ã—ã€ç¨€ãªãƒ‡ãƒ¼ã‚¿æ¶ˆå¤±ã‚’ã‚らã‹ã˜ã‚é¿ã‘ã‚‹ã®ã«å½¹ç«‹ã¤ã§ã—ょã†ã€‚" +"ã“ã‚Œã¯ã€ã‚¨ãƒ©ãƒ¼ãŒè¦‹ã¤ã‹ã‚‰ãªã„é™ã‚Šã¯èª­ã¿è¾¼ã¿ãƒã‚§ãƒƒã‚¯ã®ã¿ã§ã‚ã‚‹ã®ã«æ³¨æ„ã—ã¦ãã ã•ã„。" +"エラーãŒç™ºè¦‹ã•ã‚ŒãŸå ´åˆã€mdadm ã¯ä¿®æ­£ã—よã†ã¨ã—ã¦ã€çµæžœçš„ã«ãƒ¡ãƒ‡ã‚£ã‚¢ã¸æ›¸ãè¾¼ã¿ã‚’" +"è¡Œã„ã¾ã™ã€‚" + +#. Type: boolean +#. Description +#: ../mdadm.templates:9001 +msgid "" +"The default, if turned on, is to run the checks on the first Sunday of every " +"month at 01:06 o'clock." +msgstr "" +"有効ã«ã—ãŸå ´åˆã€ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã§ã¯æ¯Žæœˆç¬¬ä¸€æ—¥æ›œ 01:06 ã«ãƒã‚§ãƒƒã‚¯ãŒå®Ÿè¡Œã•ã‚Œã¾ã™ã€‚" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "Do you want to start the MD monitoring daemon?" +msgstr "MD 監視デーモンを起動ã—ã¾ã™ã‹?" + +#. Type: boolean +#. Description +#: ../mdadm.templates:10001 +msgid "" +"The MD (RAID) monitor daemon sends email notifications in response to " +"important MD events (such as a disk failure). You probably want to enable it." +msgstr "" +"MD (RAID) 監視デーモンã¯ã€é‡å¤§ãª MD 関連ã®ã‚¤ãƒ™ãƒ³ãƒˆ (ディスク障害ãªã©) ã«å¯¾ã—ã¦" +"メールã§é€šçŸ¥ã‚’é€ã‚Šã¾ã™ã€‚有効ã«ã™ã‚‹ã®ã‚’推奨ã—ã¾ã™ã€‚。" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "Recipient for email notifications:" +msgstr "メール通知ã®å®›å…ˆ:" + +#. Type: string +#. Description +#: ../mdadm.templates:11001 +msgid "" +"Please enter the email address of the user who should get the email " +"notification for important MD events." +msgstr "" +"MD 関連ã®é‡å¤§ãªã‚¤ãƒ™ãƒ³ãƒˆãŒç™ºç”Ÿã—ãŸéš›ã€ãƒ¡ãƒ¼ãƒ«ã§ã®é€šçŸ¥ã‚’å—ã‘å–ã‚‹å¿…è¦ãŒã‚るユー" +"ザã®ãƒ¡ãƒ¼ãƒ«ã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’入力ã—ã¦ãã ã•ã„。" + +#~ msgid "Initialise the superblock if you reuse hard disks" +#~ msgstr "ãƒãƒ¼ãƒ‰ãƒ‡ã‚£ã‚¹ã‚¯ã‚’å†åˆ©ç”¨ã™ã‚‹å ´åˆã¯ superblock ã‚’åˆæœŸåŒ–ã—ã¦ãã ã•ã„" + +#~ msgid "" +#~ "WARNING! If you are using hard disks which have RAID superblocks from " +#~ "earlier installations in different RAID arrays, you MUST zero each " +#~ "superblock *before* activating the autostart feature." +#~ msgstr "" +#~ "警告! 以å‰ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã«ã‚ˆã£ã¦ä»–ã® RAID アレイã«å¯¾ã™ã‚‹ RAID superblock " +#~ "ã‚’ä¿æŒã—ã¦ã„ã‚‹ãƒãƒ¼ãƒ‰ãƒ‡ã‚£ã‚¹ã‚¯ã‚’使ã£ã¦ã„ã‚‹å ´åˆã€è‡ªå‹•èµ·å‹•æ©Ÿèƒ½ã‚’有効ã«ã™ã‚‹" +#~ "「å‰ã€ã«ã€ãã® superblock をゼロã§ä¸Šæ›¸ãã™ã‚‹ã“ã¨ãŒã€Œå¿…è¦ã€ã§ã™ã€‚" + +#~ msgid "" +#~ "To do this, do not start the RAID devices automatically. First, zero the " +#~ "superblock (mdadm --zero-superblock /dev/mdX). Next, use `dpkg-" +#~ "reconfigure mdadm` to reactivate the autostart feature." +#~ msgstr "" +#~ "ã“れを行ã†ã«ã¯ã€RAID デãƒã‚¤ã‚¹ã‚’自動的ã«èµ·å‹•ã—ã¦ã¯ã„ã‘ã¾ã›ã‚“。ã¾ãšã€ " +#~ "superblock をゼロã§ä¸Šæ›¸ãã—ã¾ã™ (mdadm --zero-superblock /dev/xxx)。 ãã—" +#~ "ã¦ã€è‡ªå‹•èµ·å‹•æ©Ÿèƒ½ã‚’有効ã«ã™ã‚‹ãŸã‚ã€'dpkg-reconfigure mdadm' コマンドを実行" +#~ "ã—ã¾ã™ã€‚" + +#~ msgid "" +#~ "You have the option to start all other arrays (those not needed for the " +#~ "root filesystem) later in the boot sequence. Doing so will give you " +#~ "greater control over the arrays with the mdadm configuration file. " +#~ "Starting all arrays at boot-time may be safer though." +#~ msgstr "" +#~ "ブートシーケンスã®å¾Œã‚ã®æ–¹ã§ (root ファイルシステムã«ã¯å¿…è¦ãªã„) ä»–ã®ã‚¢ãƒ¬" +#~ "イ全ã¦ã‚’èµ·å‹•ã™ã‚‹ã¨ã„ã†é¸æŠžè‚¢ã‚‚ã‚ã‚Šã¾ã™ã€‚ã“れをé¸ã¹ã°ã€mdadm ã®è¨­å®šãƒ•ã‚¡ã‚¤ãƒ«" +#~ "を使ã£ã¦ã€ã‚¢ãƒ¬ã‚¤ã«ã¤ã„ã¦æ§˜ã€…ãªè¨­å®šãŒå‡ºæ¥ã‚‹ã‚ˆã†ã«ãªã‚‹ã§ã—ょã†ã€‚ã‚‚ã£ã¨ã‚‚ã€èµ·" +#~ "動時ã«å…¨ã¦ã®ã‚¢ãƒ¬ã‚¤ã‚’èµ·å‹•ã™ã‚‹ã»ã†ãŒå®‰å…¨ã§ã¯ã‚ã‚Šã¾ã™ã€‚" + +#~ msgid "" +#~ "If RAID devices are started automatically, all RAID devices are " +#~ "discovered and assembled automatically at system startup. This option " +#~ "should only be used if the md driver is compiled as a module. If it is " +#~ "compiled into your kernel, the automatic startup will be performed at " +#~ "boot time by the kernel and therefore you should not choose this option." +#~ msgstr "" +#~ "RAID デãƒã‚¤ã‚¹ãŒè‡ªå‹•çš„ã«èµ·å‹•ã™ã‚‹ã‚ˆã†ã«ã™ã‚‹ã¨ã€ã‚·ã‚¹ãƒ†ãƒ èµ·å‹•æ™‚ã«å…¨ã¦ã® RAID " +#~ "デãƒã‚¤ã‚¹ãŒæ¤œå‡ºã•ã‚Œã€è‡ªå‹•çš„ã«æ§‹æˆã•ã‚Œã¾ã™ã€‚ã“ã®ã‚ªãƒ—ション㯠md ドライãƒãŒãƒ¢" +#~ "ジュールã¨ã—ã¦ã‚³ãƒ³ãƒ‘イルã•ã‚Œã¦ã„ã‚‹å ´åˆã®ã¿ã«åˆ©ç”¨ã—ã¾ã™ã€‚カーãƒãƒ«ã«çµ„ã¿è¾¼ã‚“" +#~ "ã§ã‚³ãƒ³ãƒ‘イルã—ã¦ã„ãŸå ´åˆã€ã‚·ã‚¹ãƒ†ãƒ èµ·å‹•æ™‚ã«ã‚«ãƒ¼ãƒãƒ«ã«ã‚ˆã£ã¦è‡ªå‹•èµ·å‹•ãŒå®Ÿè¡Œã•" +#~ "れるã®ã§ã€ã“ã®ã‚ªãƒ—ションã§ã®é¸æŠžã¯ã§ãã¾ã›ã‚“。" + +#~ msgid "" +#~ "When the RAID monitor daemon runs, email notifications are sent when a " +#~ "disk belonging to a RAID array fails or changes its status for some " +#~ "reason." +#~ msgstr "" +#~ "RAID 監視デーモンãŒå‹•ä½œã—ã¦ã„ã‚‹å ´åˆã€RAID アレイã«å±žã—ã¦ã„るディスクãŒæ•…éšœ" +#~ "ã™ã‚‹ã‹ä½•ã‚‰ã‹ã®ç†ç”±ã§å¤‰åŒ–ã—ãŸéš›ã«ãƒ¡ãƒ¼ãƒ«ã§é€šçŸ¥ãŒé€ã‚‰ã‚Œã¾ã™ã€‚" --- mdadm-2.6.2.orig/debian/mdrun +++ mdadm-2.6.2/debian/mdrun @@ -0,0 +1,189 @@ +#!/bin/sh + +# mdrun, (c) Eduard Bloch 2003 + +# Usage: +# Without arguments: autodetect all RAID partitions and activate MDs +# Arguments: [ DEVDIR ] NUMBER UUID [ ... ] +# a number of number/uuid pairs, where NUMBER is the one from /dev/md/* +# Argument: LIST +# lists all raids in the syntax needed for the pairs (see above) + +# IMPORTANT: create /dev/fs directory if you have devfs support in the kernel +# but do not want to mount it over /dev. Usage of /dev/fs directory will keep +# mdrun away from /dev. + +# If the first argument is a directory, it will be used as a writeable +# temporary directory for device nodes. mdrun needs mknod to create them +# on-the-fly + +# Environment: +# MORERAIDVOLUMES (list of strings) : additional raid disks to scan, +# eg. loop devices + +is_true() +{ + case "$1" in + [Yy]es|[Yy]|1|[Tt]rue) return 0;; + *) return 1; + esac +} + +warn() +{ + echo "$@" >&2 +} + +[ -f /etc/default/mdadm ] && . /etc/default/mdadm +# disabled until the transition is complete +if false && ! is_true $USE_DEPRECATED_MDRUN; then + warn + warn ========================= + warn mdrun deprecation warning + warn ========================= + warn + warn If you are seeing this during boot, please upgrade to a newer + warn version of the initramfs-tools package and ignore the rest of + warn this message. + warn + warn You are running $0, or your system is not properly configured + warn such that $0 is used as a fallback. Due to technical limitations, + warn $0 is deprecated and will be removed in a future relese of mdadm. + warn Please see /usr/share/doc/mdadm/README.mdrun for more info. + warn + + TIMEOUT=15 + if [ -r /dev/stdin ]; then + # cannot use -t or -n, which is not POSIX + read -p'Please hit return to continue...' resp < /dev/stdin >&2 + warn + else + warn "Pausing for $TIMEOUT seconds..." >&2 + sleep $TIMEOUT + fi +fi + +if ! test -e /proc/partitions ; then + echo "/proc not mounted!" + exit 1 +fi + +DEVDIR=/dev + +if [ -d "$1" ] ; then + AUTOCREATE=true + DEVDIR="$1" + shift +fi + +# For people that compile the kernel with devfs (means: different +# proc/partitions content), but without auto-mounting it +if ! uname -r | grep "^2.6" 1>/dev/null && [ -z "$AUTOCREATE" ] && grep " devfs" /proc/filesystems >/dev/null 2>&1 && ! grep "^devfs" /proc/mounts >/dev/null 2>&1 ; then + + mkdir /dev/fs 2>/dev/null + # if we can do it - good, we will use it. Otherwise, use /dev even if it is ugly + + # mount devfs for now to make the device names match, umount later + if [ -d /dev/fs ] ; then + DEVDIR=/dev/fs + fi + mount none $DEVDIR -tdevfs + UMNTDEVFS="umount $DEVDIR" +fi + +# arr(array, index): return contents in array[index]; as with Bourne shell +# in general, there is no easy way to distinguish between index not +# existing and empty string assigned. +arr() { sa_i=`arr_index $2`; eval "echo \"\$$1_${sa_i}\""; unset sa_i; } + +# seterr(array, index, value): assign the given value to array[index]. +setarr() { sa_i=`arr_index $2`; eval "$1_${sa_i}=\"$3\""; unset sa_i; } + +# arr_index(index): make sure the given index is valid for use. +arr_index() { echo $1 | sed -e 's/:/_/g' | sed 's;/;_;g'; } + + +BASE=$DEVDIR/md +export BASE +#devfs +test -d $BASE && BASE=$BASE/ + +next_free_md() { + for raidnr in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24; do + if ! mdadm -D $BASE$raidnr >/dev/null 2>&1 ; then + echo $BASE$raidnr + return 0 + fi + done + return 1 +} + +listpairs() { + for NUMBER in `cat /proc/mdstat | grep "^md. : active" | sed -e 's/^md\(.\) :.*/\1/'`; do + echo $NUMBER + mdadm -D ${BASE}$NUMBER 2>/dev/null |grep UUID | sed 's/.*: \(.*\)/\1/' + done +} + +if [ "$1" = LIST ] ; then + echo `listpairs` + $UMNTDEVFS + exit 0 +fi + +DEVDIRESC=$(echo $DEVDIR | sed -e 's!/!\\/!g') +if [ "$AUTOCREATE" ] ; then + CREATECMD=$(sed -e "s/.*major.*//; s/.*\ \([:0-9:]\+\)\ \+\ \([:0-9:]\+\)\ \+\ [:0-9:]\+\ \+\([:a-z0-9\/:]\+\).*/mknod \3 b \1 \2 ; / ; s/\//_/g" < /proc/partitions) + export CREATECMD + export DEVDIR + # and we need array nodes, of course + ( + cd $DEVDIR ; + eval $CREATECMD ; + for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ; do + mknod ${BASE}$x b 9 $x + done + ) + PARTLIST=$(sed -e "s/.*major.*//; s/.*\ \([:0-9:]\+\)\ \+\ \([:0-9:]\+\)\ \+\ [:0-9:]\+\ \+\([:a-z0-9\/:]\+\).*/DEVDIR\3 /; s/\//_/g ; s/DEVDIR/$DEVDIRESC\//;" < /proc/partitions) +else + PARTLIST=$(sed -e "s/.*major.*//; s/^[:0-9 :]* \([:a-z:].[:a-z0-9\/:]*\).*/\1/; s/^\([:a-z:].*\)/$DEVDIRESC\/\1/g" < /proc/partitions) +fi + +for SRC in $PARTLIST $MORERAIDVOLUMES ; do + SUM=$(mdadm -E $SRC 2>/dev/null | grep UUID | sed 's/.*: \(.*\)/\1/') + for x in $SUM; do + UUIDS="$UUIDS $SUM" + setarr MDS $SUM "`arr MDS $SUM` $SRC" + done +done + +if [ "$#" -gt 1 ] ; then + NUMBER=${BASE}$1 + MD=$2 + shift ; shift + if [ "`arr MDS $MD`" != "started" ] ; then + mdadm -A -a yes $NUMBER -f `arr MDS $MD` && setarr MDS $MD "started" + # just to be sure + ln /dev/md/$NUMBER /dev/md$NUMBER 2>/dev/null + fi +fi + +# and process the rest, if it exists +# do not touch active arrays +#dropactive() { + for NUMBER in `cat /proc/mdstat | grep "^md. : active" | sed -e 's/^md\(.\) :.*/\1/'`; do + setarr MDS `mdadm -D ${BASE}$NUMBER 2>/dev/null |grep UUID | sed 's/.*: \(.*\)/\1/'` "started" + done +#} + + +for MD in $UUIDS; do + if [ "`arr MDS $MD`" != "started" ] ; then + NUMBER=`next_free_md` + mdadm -A -a yes $NUMBER -f `arr MDS $MD` && setarr MDS $MD "started" + # just to be sure + ln /dev/md/$NUMBER /dev/md$NUMBER 2>/dev/null + fi +done + +$UMNTDEVFS --- mdadm-2.6.2.orig/debian/README.mdrun +++ mdadm-2.6.2/debian/README.mdrun @@ -0,0 +1,45 @@ +mdadm for Debian -- notes on mdrun +================================== + +mdadm for Debian ships with /sbin/mdrun, which is a sledgehammer approach to +assembling MD arrays (RAIDs) during boot. Unfortunately, the script has several +problems (see e.g. #354705) and can cause major headaches. + +Fortunately, mdadm has since added all the functionality needed to replace +mdrun. Thus, with mdadm 2.5, mdrun has been deprecated in Debian, and will be +removed in a future release (but not before etch). + +mdrun may be used in three cases, and the following list includes what you can +do to rid yourself of mdrun: + + initramfs: + upgrade to the latest version of initramfs (and see + README.initramfs-transition for now). + + custom scripts / command line use: + the command to replace mdrun is: + + mdadm --assemble --scan --auto=yes + + to be able to run this command, you need to ensure that + /etc/mdadm/mdadm.conf (or /etc/mdadm.conf, which is less preferred) + properly describes your MD arrays. You can use the output generated + by the script /usr/share/mdadm/mkconf to help you migrate an existing + configuration or to create a new configuration file. + + You can find more information in the mdadm(8) and mdadm.conf(5) manpages. + + custom init.d scripts: + while this release includes init.d scripts that do not use mdrun, you may + still have custom scripts around. Please consider whether they are still + needed. If they do things that the mdadm init.d scripts do not do, + consider whether it would be useful to file a wishlist bug. + + Please note that you also need to a correct mdadm.conf file, as described + above. + +Have fun, + + -- martin f. krafft Mon, 31 Jul 2006 14:35:08 +0100 + +$Id: README.mdrun 159 2006-09-11 16:34:53Z madduck $ --- mdadm-2.6.2.orig/debian/copyright +++ mdadm-2.6.2/debian/copyright @@ -0,0 +1,21 @@ +This package was debianized by Mario Jou/3en on +Wed, 26 Dec 2001 17:07:09 +0100. +Martin F. Krafft took over on +Tue, 16 May 2006 13:21:06 -0500 + +The mdadm source was downloaded from + http://www.cse.unsw.edu.au/~neilb/source/mdadm/ + +Upstream Author: Neil Brown + +Copyright © 2001-2006 Neil Brown +Packaging copyright © 2001-2005 Mario Jou/3en +Packaging copyright © 2005-2006 Martin F. Krafft + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or +(at your option) any later version. + +On Debian GNU/Linux systems, the complete text of the GNU General +Public License can be found in '/usr/share/common-licenses/GPL'. --- mdadm-2.6.2.orig/debian/mdadm.docs +++ mdadm-2.6.2/debian/mdadm.docs @@ -0,0 +1,10 @@ +TODO +debian/README.recipes +debian/README.initramfs-transition +debian/README.upgrading-2.5.3 +debian/README.mdrun +debian/README.checkarray +debian/FAQ +md.txt +rootraiddoc.97.html +RAID5_versus_RAID10.txt --- mdadm-2.6.2.orig/debian/mdadm-startall.sgml +++ mdadm-2.6.2/debian/mdadm-startall.sgml @@ -0,0 +1,115 @@ + manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + + + The docbook-to-man binary is found in the docbook-to-man package. + Please remember that if you create the nroff version in one of the + debian/rules file targets (such as build), you will need to include + docbook-to-man in your Build-Depends control field. + + --> + + + Eduard"> + Bloch"> + + April 3, 2007"> + + 8"> + blade@debian.org"> + + mdadm-startall"> + + + Debian"> + GNU"> + GPL"> +]> + + + +
+ &dhemail; +
+ + &dhfirstname; + &dhsurname; + + + 2007 + &dhusername; + + &dhdate; + + + &dhucpackage; + + &dhsection; + + + &dhucpackage; + + helper script to start all known arrays + + + + &dhucpackage; + + + + DESCRIPTION + + The &dhucpackage; script scans the system for + arrays and writes a configuration file matching the current state. It then + starts all arrays it found. If a configuration file already exists and + defines arrays, it is used instead. + + + + SEE ALSO + + mdadm (8), mdadm.conf(5) + + + AUTHOR + + This manual page was written by &dhusername; &dhemail; for + the &debian; system (but may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the &gnu; General Public License, Version 2 any + later version published by the Free Software Foundation. + + + On Debian systems, the complete text of the GNU General Public + License can be found in /usr/share/common-licenses/GPL. + + + + + + + + --- mdadm-2.6.2.orig/debian/mdadm.templates +++ mdadm-2.6.2/debian/mdadm.templates @@ -0,0 +1,100 @@ +Template: mdadm/initrdstart +Type: string +Default: all +_Description: MD arrays needed for the root filesystem: + ${msg} + . + Please enter a space-separated list of devices, 'all', or 'none'. You may + omit the leading '/dev/' and just enter e.g. "md0 md1", or "md/1 md/d0". + +Template: mdadm/initrdstart_msg_intro +Type: text +_Description: for internal use - only the long description is needed. + If your system has its root filesystem on an MD array (RAID), it needs to be + started early during the boot sequence. If your root filesystem is on + a logical volume (LVM), which is on MD, all constituent arrays need to be + started. + . + If you know exactly which arrays are needed to bring up the root filesystem, + and you want to postpone starting all other arrays to a later point in the + boot sequence, enter the arrays to start here. Alternatively, enter 'all' to + simply start all available arrays. + . + If you do not need or want to start any arrays for the root filesystem, leave + the answer blank (or enter 'none'). This may be the case if you are using + kernel autostart or do not need any arrays to boot. + +Template: mdadm/initrdstart_msg_errexist +Type: text +_Description: + An error occurred: device node does not exist + +Template: mdadm/initrdstart_msg_errblock +Type: text +_Description: + An error occurred: not a block device + +Template: mdadm/initrdstart_msg_errmd +Type: text +_Description: + An error occurred: not an MD array + +Template: mdadm/initrdstart_msg_errconf +Type: text +_Description: + An error occurred: array not listed in mdadm.conf file + +Template: mdadm/initrdstart_notinconf +Type: boolean +Default: false +_Description: Proceed with starting arrays not listed in mdadm.conf? + The array you have specified (${array}) is not listed in the configuration + file ${config}. Therefore it cannot be started during boot, unless you + correct the configuration file and recreate the initial ramdisk. + . + Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if you intend + to continue. + . + This warning is only relevant if you need arrays to be started from the + initial ramdisk to be able to boot. If you use kernel autostarting, or do not + need any arrays to be started as early as the initial ramdisk is loaded, you + can simply continue. Alternatively, choose not to continue and enter 'none' + when prompted which arrays to start from the initial ramdisk. + +Template: mdadm/autostart +Type: boolean +Default: true +_Description: Do you want to start MD arrays automatically? + Once the base system has come up, mdadm can start all MD arrays (RAIDs) + specified in /etc/mdadm/mdadm.conf, which have not yet been started. Unless + you have compiled multiple device (MD) support into the kernel and marked all + partitions part of MD arrays with type 0xfd (as those and only those will be + started automatically by the kernel), this is probably what you want. + +Template: mdadm/autocheck +Type: boolean +Default: true +_Description: Should mdadm run monthly redundancy checks of the MD arrays? + If your kernel supports it (>> 2.6.14), mdadm can periodically check the + redundancy of your MD arrays (RAIDs). This may be a resource-intensive process, + depending on your setup, but it could help prevent rare cases of data loss. + Note that this is a read-only check unless errors are found; if errors are + found, mdadm will try to correct them, which may result in write access to + the media. + . + The default, if turned on, is to run the checks on the first Sunday of every + month at 01:06 o'clock. + +Template: mdadm/start_daemon +Type: boolean +Default: true +_Description: Do you want to start the MD monitoring daemon? + The MD (RAID) monitor daemon sends email notifications in response to + important MD events (such as a disk failure). You probably want to enable it. + +Template: mdadm/mail_to +Type: string +Default: root +_Description: Recipient for email notifications: + Please enter the email address of the user who should get the email + notification for important MD events. --- mdadm-2.6.2.orig/debian/FAQ +++ mdadm-2.6.2/debian/FAQ @@ -0,0 +1,526 @@ +Frequently asked questions -- Debian mdadm +========================================== + +Also see /usr/share/doc/mdadm/README.recipes.gz . + +The latest version of this FAQ is available here: + http://svn.debian.org/wsvn/pkg-mdadm/mdadm/trunk/debian/FAQ?op=file&rev=0&sc=0 + +0. What does MD stand for? +~~~~~~~~~~~~~~~~~~~~~~~~~~ + MD is an abbreviation for "multiple device" (also often called "multi- + disk"). The Linux MD implementation implements various strategies for + combining multiple physical devices into single logical ones. The most + common use case is commonly known as "Software RAID". Linux supports RAID + levels 1, 4, 5, 6, and 10, as well as the "pseudo-redundant" RAID level 0. + In addition, the MD implementation covers linear and multipath + configurations. + + Most people refer to MD as RAID. Since the original name of the RAID + configuration software is "md"adm, I chose to use MD consistently instead. + +1. How do I overwrite ("zero") the superblock? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + mdadm --zero-superblock /dev/mdX + + Note that this is a destructive operation. It does not actually delete any + data, but the device will have lost its "authority". You cannot assemble the + array with it anymore, and if you add the device to another array, the + synchronisation process *will* *overwrite* all data on the device. + + Nevertheless, sometimes it is necessary to zero the superblock: + + - If you are reusing a disk that has been part of an array with an different + superblock version and/or location. In this case you zero the superblock + before you assemble the array, or add the device to an array. + + - If you are trying to prevent a device from being recognised as part of an + array. Say for instance you are trying to change an array spanning sd[ab]1 + to sd[bc]1 (maybe because sda is failing or too slow), then automatic + (scan) assembly will still recognise sda1 as a valid device. You can limit + the devices to scan with the DEVICE keyword in the configuration file, but + this may not be what you want. Instead, zeroing the superblock will + (permanently) prevent a device from being considered as part of an array. + +2. How do I change the preferred minor of an MD array (RAID)? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + See item 12 in /usr/share/doc/mdadm/README.recipes.gz and read the mdadm + manpage (search for 'preferred'). + +3. How does mdadm determine which /dev/mdX or /dev/md/X to use? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + The logic used by mdadm to determine the device node name in the mdadm + --examine output (which is used to generate mdadm.conf) depends on several + factors. Here's how mdadm determines it: + + It first checks the superblock version of a given array (or each array in + turn when iterating all of them). Run + + mdadm --detail /dev/mdX | sed -ne 's,.*Version : ,,p' + + to determine the superblock version of a running array, or + + mdadm --examine /dev/sdXY | sed -ne 's,.*Version : ,,p' + + to determine the superblock version from a component device of an array. + + Version 0 superblocks (00.90.XX) + '''''''''''''''''''''''''''''''' + You need to know the preferred minor number stored in the superblock, + so run either of + + mdadm --detail /dev/mdX | sed -ne 's,.*Preferred Minor : ,,p' + mdadm --examine /dev/sdXY | sed -ne 's,.*Preferred Minor : ,,p' + + Let's call the resulting number MINOR. Also see FAQ 2 further up. + + Given MINOR, mdadm will output /dev/md if the device node + /dev/md exists. + Otherwise, it outputs /dev/md/ + + Version 1 superblocks (01.XX.XX) + '''''''''''''''''''''''''''''''' + Version 1 superblocks actually seem to ignore preferred minors and instead + use the value of the name field in the superblock. Unless specified + explicitly during creation (-N|--name) the name is determined from the + device name used, using the following regexp: 's,/dev/md/?(.*),$1,', thus: + + /dev/md0 -> 0 + /dev/md/0 -> 0 + /dev/md_d0 -> _d0 (d0 in later versions) + /dev/md/d0 -> d0 + /dev/md/name -> name + (/dev/name does not seem to work) + + mdadm will append the name to '/dev/md/', so it will always output device + names under the /dev/md/ directory. Newer versions can create a symlink + from /dev/mdX. See the symlinks option in mdadm.con(5) and mdadm(8). + + If you want to change the name, you can do so during assembly: + + mdadm -A -U name -N newname /dev/mdX /dev/sd[abc]X + + I know this all sounds inconsistent and upstream has some work to do. + We're on it. + +4. Which RAID level should I use? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Please read /usr/share/doc/mdadm/RAID5_versus_RAID10.txt.gz . + + Many people seem to prefer RAID4/5/6 because it makes more efficient use of + space. For example, if you have disks of size X, then in order to get 2X + storage, you need 3 disks for RAID5, but 4 if you use RAID10 or RAID1+0 (or + RAID6). + + This gain in usable space comes at a price: performance; RAID1/10 can be up + to four times faster than RAID4/5/6. + + At the same time, however, RAID4/5/6 provide somewhat better redundancy in + the event of two failing disks. In a RAID10 configuration, if one disk is + already dead, the RAID can only survive if any of the two disks in the other + RAID1 array fails, but not if the second disk in the degraded RAID1 array + fails (see next item, 4b). A RAID6 across four disks can cope with any two + disks failing. However, RAID6 is noticeably slower than RAID5. RAID5 and + RAID4 do not differ much, but can only handle single-disk failures. + + If you can afford the extra disks (storage *is* cheap these days), I suggest + RAID1/10 over RAID4/5/6. If you don't care about performance but need as + much space as possible, go with RAID4/5/6, but make sure to have backups. + Heck, make sure to have backups whatever you do. + + Let it be said, however, that I thoroughly regret putting my primary + workstation on RAID5. Anything disk-intensive brings the system to its + knees; I will have to migrate to RAID10 at one point. + +4b. Can a 4-disk RAID10 survive two disk failures? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + I am assuming that you are talking about a setup with two copies of each + block, so --layout=near2/far2/offset2: + + In half of the cases, yes [0], and it does not matter which layout you use. + When you assemble 4 disks into a RAID10, you essentially stripe a RAID0 + across two RAID1, so the four disks A,B,C,D become two pairs: A,B and C,D. + If A fails, the RAID6 can only survive if the second failing disk is either + C or D; If B fails, your array is dead. + + Thus, if you see a disk failing, replace it as soon as possible! + + If you need to handle two failing disks out of a set of four, you have to + use RAID6, or store more than two copies of each block (see the --layout + option in the mdadm(8) manpage). + + See also question 18 further down. + + 0. it's actually 1/(n-1), where n is the number of disks. I am not + a mathematician, see http://aput.net/~jheiss/raid10/ + +5. How to convert RAID5 to RAID10? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + To convert RAID5 to RAID10, you need a spare disk (either a spare, forth + disk in the array, or a new one). Then you remove the spare and one of the + three disks from the RAID5, create a degraded RAID10 across them, create + the filesystem and copy the data (or do a raw copy), then add the other two + disks to the new RAID10. However, mdadm cannot assemble a RAID10 with 50% + missing devices the way you might like it: + + mdadm --create -l 10 -n4 -pn2 /dev/md1 /dev/sd[cd] missing missing + + For reasons that may be answered by question 20 further down, mdadm actually + cares about the order of devices you give it. If you intersperse the missing + keywords with the physical drives, it should work: + + mdadm --create -l 10 -n4 -pn2 /dev/md1 /dev/sdc missing /dev/sdd missing + + or even + + mdadm --create -l 10 -n4 -pn2 /dev/md1 missing /dev/sd[cd] missing + + Also see item (4b) further up, and this thread: + http://marc.theaimsgroup.com/?l=linux-raid&m=116004333406395&w=2 + +6. What is the difference between RAID1+0 and RAID10? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + RAID1+0 is a form of RAID in which a RAID0 is striped across two RAID1 + arrays. To assemble it, you create two RAID1 arrays and then create a RAID0 + array with the two md arrays. + + The Linux kernel provides the RAID10 level to do pretty much exactly the + same for you, but with greater flexibility (and somewhat improved + performance). While RAID1+0 makes sense with 4 disks, RAID10 can be + configured to work with only 3 disks. Also, RAID10 has a little less + overhead than RAID1+0, which has data pass the md layer twice. + + I prefer RAID10 over RAID1+0. + +6b. What's the difference between RAID1+0 and RAID0+1? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + In short: RAID1+0 concatenates two mirrored arrays while RAID0+1 mirrors two + concatenated arrays. However, the two are also often switched. + + The linux MD driver supports RAID10, which is equivalent to the above + RAID1+0 definition. + + RAID1+0/10 has a greater chance to survive two disk failures, its + performance suffers less when in degraded state, and it resyncs faster after + replacing a failed disk. + + See http://aput.net/~jheiss/raid10/ for more details. + +7. Which RAID10 layout scheme should I use +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + RAID10 gives you the choice between three ways of laying out the blocks on + the disk. Assuming a simple 4 drive setup with 2 copies of each block, then + if A,B,C are data blocks, a,b their parts, and 1,2 denote their copies, the + following would be a classic RAID1+0 where 1,2 and 3,4 are RAID0 pairs + combined into a RAID1: + + near=2 would be (this is the classic RAID1+0) + + hdd1 Aa1 Ba1 Ca1 + hdd2 Aa2 Ba2 Ca2 + hdd3 Ab1 Bb1 Cb1 + hdd4 Ab2 Bb2 Cb2 + + offset=2 would be + + hdd1 Aa1 Bb2 Ca1 Db2 + hdd2 Ab1 Aa2 Cb1 Ca2 + hdd3 Ba1 Ab2 Da1 Cb2 + hdd4 Bb1 Ba2 Db1 Da2 + + far=2 would be + + hdd1 Aa1 Ca1 .... Bb2 Db2 + hdd2 Ab1 Cb1 .... Aa2 Ca2 + hdd3 Ba1 Da1 .... Ab2 Cb2 + hdd4 Bb1 Db1 .... Ba2 Da2 + + Where the second set start half-way through the drives. + + The advantage of far= is that you can easily spread a long sequential read + across the drives. The cost is more seeking for writes. offset= can + possibly get similar benefits with large enough chunk size. Neither upstream + nor the package maintainer have tried to understand all the implications of + that layout. It was added simply because it is a supported layout in DDF and + DDF support is a goal. + +8. (One of) my RAID arrays is busy and cannot be stopped. What gives? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + It is perfectly normal for mdadm to report the array with the root + filesystem to be busy on shutdown. The reason for this is that the root + filesystem must be mounted to be able to stop the array (or otherwise + /sbin/mdadm does not exist), but to stop the array, the root filesystem + cannot be mounted. Catch 22. The kernel actually stops the array just before + halting, so it's all well. + + If mdadm cannot stop other arrays on your system, check that these arrays + aren't used anymore. Common causes for busy/locked arrays are: + + * The array contains a mounted filesystem (check the `mount' output) + * The array is used as a swap backend (check /proc/swaps) + * The array is used by the device-mapper (check with `dmsetup') + * LVM + * dm-crypt + * EVMS + * The array is used by a process (check with `lsof') + +9. Should I use RAID0 (or linear)? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + No. Unless you know what you're doing and keep backups, or use it for data + that can be lost. + +9b. Why not? +~~~~~~~~~~~~ + RAID0 has zero redundancy. If you stripe a RAID0 across X disks, you + increase the likelyhood of complete loss of the filesystem by a factor of X. + + The same applies to LVM by the way. + + If you want/must used LVM or RAID0, stripe it across RAID1 arrays + (RAID10/RAID1+0, or LVM on RAID1), and keep backups! + +10. Can I cancel a running array check (checkarray)? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + See the -x option in the `/usr/share/mdadm/checkarray --help` output. + +11. mdadm warns about duplicate/similar superblocks; what gives? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + In certain configurations, especially if your last partition extends all the + way to the end of the disk, mdadm may display a warning like: + + mdadm: WARNING /dev/hdc3 and /dev/hdc appear to have very similar + superblocks. If they are really different, please --zero the superblock on + one. If they are the same or overlap, please remove one from the DEVICE + list in mdadm.conf. + + There are two ways to solve this: + + (a) recreate the arrays with version-1 superblocks, which is not always an + option -- you cannot yet upgrade version-0 to version-1 superblocks for + existing arrays. + + (b) instead of 'DEVICE partitions', list exactly those devices that are + components of MD arrays on your system. So in the above example: + + - DEVICE partitions + + DEVICE /dev/hd[ab]* /dev/hdc[123] + +12. mdadm -E / mkconf report different arrays with the same device + name / minor number. What gives? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + In almost all cases, mdadm updates the super-minor field in an array's + superblock when assembling the array. It does *not* do this for RAID0 + arrays. Thus, you may end up seeing something like this when you run + mdadm -E or mkconf: + + ARRAY /dev/md0 level=raid0 num-devices=2 UUID=abcd... + ARRAY /dev/md0 level=raid1 num-devices=2 UUID=dcba... + + Note how the two arrays have different UUIDs but both appear as /dev/md0. + + The solution in this case is to explicitly tell mdadm to update the + superblock of the RAID0 array. Assuming that the RAID0 array in the above + example should really be /dev/md1: + + mdadm --stop /dev/md1 + mdadm --assemble --update=super-minor --uuid=abcd... /dev/md1 + + See question 2 of this FAQ, and also http://bugs.debian.org/386315 and + recipe #12 in README.recipes . + +13. Can a MD array be partitioned? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + For a MD array to be able to hold partitions, it must be created as + a "partitionable array", using the configuration auto=part on the command + line or in the configuration file, or by using the standard naming scheme + (md_d* or md/d*) for partitionable arrays: + + mdadm --create --auto=yes ... /dev/md_d0 ... + # see mdadm(8) manpage about the values of the --auto keyword + +14. When would I use partitionable arrays? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + This answer by Doug Ledford is shamelessly adapted from [0] (with + permission): + + First, not all MD types make sense to be split up, e.g. multipath. For + those types, when a disk fails, the *entire* disk is considered to have + failed, but with different arrays you won't switch over to the next path + until each MD array has attempted to access the bad path. This can have + obvious bad consequences for certain array types that do automatic + failover from one port to another (you can end up getting the array in + a loop of switching ports repeatedly to satisfy the fact that one array + failed over during a path down, then the path came back up, and another + array stayed on the old path because it didn't send any commands during + the path down time period). + + Second, convenience. Assume you have a 6 disk RAID5 array. If a disk + fails and you are using a partitioned MD array, then all the partitions on + the disk will already be handled without using that disk. No need to + manually fail any still active array members from other arrays. + + Third, safety. Again with the raid5 array. If you use multiple arrays on + a single disk, and that disk fails, but it only failed on one array, then + you now need to manually fail that disk from the other arrays before + shutting down or hot swapping the disk. Generally speaking, that's not + a big deal, but people do occasionally have fat finger syndrome and this + is a good opportunity for someone to accidentally fail the wrong disk, and + when you then go to remove the disk you create a two disk failure instead + of one and now you are in real trouble. + + Forth, to respond to what you wrote about independent of each other -- + part of the reason why you partition. I would argue that's not true. If + your goal is to salvage as much use from a failing disk as possible, then + OK. But, generally speaking, people that have something of value on their + disks don't want to salvage any part of a failing disk, they want that + disk gone and replaced immediately. There simply is little to no value in + an already malfunctioning disk. They're too cheap and the data stored on + them too valuable to risk loosing something in an effort to further + utilize broken hardware. This of course is written with the understanding + that the latest MD RAID code will do read error rewrites to compensate for + minor disk issues, so anything that will throw a disk out of an array is + more than just a minor sector glitch. + + 0. http://marc.theaimsgroup.com/?l=linux-raid&m=116117813315590&w=2 + +15. How can I start a dirty degraded array? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + A degraded array (e.g. a RAID5 with only two disks) that has not been + properly stopped cannot be assembled just like that; mdadm will refuse and + complain about a "dirty degraded array", for good reasons. + + The solution might be to force-assemble it, and then to start it. Please see + recipes 4 and 4b of /usr/share/doc/mdadm/README.recipes.gz and make sure you + know what you're doing. + +16. How can I influence the speed with which an array is resynchronised? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + For each array, the MD subsystem exports parameters governing the + synchronisation speed via sysfs. The values are in kB/sec. + + /sys/block/mdX/md/sync_speed -- the current speed + /sys/block/mdX/md/sync_speed_max -- the maximum speed + /sys/block/mdX/md/sync_speed_min -- the guaranteed minimum speed + +17. When I create a new array, why does it resynchronise at first? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + See the mdadm(8) manpage: + When creating a RAID5 array, mdadm will automatically create a degraded + array with an extra spare drive. This is because building the spare into + a degraded array is in general faster than resyncing the parity on + a non-degraded, but not clean, array. This feature can be over-ridden with + the --force option. + + This also applies to RAID levels 4 and 6. + + It does not make much sense for RAID levels 1 and 10 and can thus be + overridden with the --force and --assume-clean options, but it is not + recommended. Read the manpage. + +18. How many failed disks can a RAID10 handle? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + (see also question 4b) + + The following table shows how many disks you can lose and still have an + operational array. In some cases, you *can* lose more than the given number + of disks, but there is no guarantee that the array survives. Thus, the + following is the guaranteed number of failed disks a RAID10 array survives + and the maximum number of failed disks the array can (but is not guaranteed + to) handle, given the number of disks used and the number of data block + copies. Note that 2 copies means original + 1 copy. Thus, if you only have + one copy (the original), you cannot handle any failures. + + 1 2 3 4 (# of copies) + 1 0/0 0/0 0/0 0/0 + 2 0/0 1/1 1/1 1/1 + 3 0/0 1/1 2/2 2/2 + 4 0/0 1/2 2/2 3/3 + 5 0/0 1/2 2/2 3/3 + 6 0/0 1/3 2/3 3/3 + 7 0/0 1/3 2/3 3/3 + 8 0/0 1/4 2/3 3/4 + (# of disks) + + Note: I have not really verified the above information. Please don't count + on it. If a disk fails, replace it as soon as possible. Corrections welcome. + +19. What should I do if a disk fails? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Replace it as soon as possible: + + mdadm --remove /dev/md0 /dev/sda1 + halt + + mdadm --add /dev/md0 /dev/sda1 + +20. So how do I find out which other disk(s) can fail without killing the + array? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Did you read the previous question and its answer? + + For cases when you have two copies of each block, the question is easily + answered by looking at the output of /proc/mdstat. For instance on a four + disk array: + + md3 : active raid10 sdg7[3] sde7[0] sdh7[2] sdf7[1] + + you know that sde7/sdf7 form one pair and sdg7/sgh7 the other. + + If sdh now fails, this will become + + md3 : active raid10 sdg7[3] sde7[0] sdh7[4](F) sdf7[1] + + So now the second pair is broken; the array could take another failure in + the first pair, but if sdg now also fails, you're history. + + Now go and read question 19. + + For cases with more copies per block, it becomes more complicated. Let's + think of a seven disk array with three copies: + + md5 : active raid10 sdg7[6] sde7[4] sdb7[5] sdf7[2] sda7[3] sdc7[1] sdd7[0] + + Each mirror now has 7/3 = 2.33 disks to it, so in order to determine groups, + you need to round up. Note how the disks are arranged in increasing order of + their indices (the number in brackes in /proc/mdstat): + + disk: -sdd7- -sdc7- -sdf7- -sda7- -sde7- -sdb7- -sdg7- + group: [ one ][ two ][ three ] + + Basically this means that after two disk failed, you need to make sure that + the third failed disk doesn't destroy all copies of any given block. And + that's not always easy as it depends on the layout chosen: whether the + blocks are near (same offset within each group), far (spread apart in a way + to maximise the mean distance), or offset (offset by size/n within each + block). + + I'll leave it up to you to figure things out. Now go read question 19. + +21. Why does the kernel speak of 'resync' when using checkarray? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Please see README.checkarray and + http://www.mail-archive.com/linux-raid@vger.kernel.org/msg04835.html . + + In short: it's a bug. checkarray is actually not a resync, but the kernel + does not distinguish between them. + +22. Can I prioritise the sync process and sync certain arrays before others? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Upon start, md will resynchronise any unclean arrays, starting in somewhat + random order. Sometimes it's desirable to sync e.g. /dev/md3 first (because + it's the most important), but while /dev/md1 is synchronising, /dev/md3 will + be DELAYED (see /proc/mdstat; only if they share the same physical + components. + + It is possible to delay the synchronisation via /sys: + + echo idle >/sys/block/md1/md/sync_action + + This will cause md1 to go idle and md to synchronise md3 (or whatever is + queued next; repeat the above for other devices if necessary). md will also + realise that md1 is still not in sync and queue it for resynchronisation, + so it will sync automatically when its turn has come. + + -- martin f. krafft Thu, 13 Jan 2007 14:17:03 +0200 + +$Id: FAQ 299 2007-01-13 13:18:11Z madduck $ --- mdadm-2.6.2.orig/debian/bugscript +++ mdadm-2.6.2/debian/bugscript @@ -0,0 +1,89 @@ +#!/bin/sh +# +# mdadm bug submission control script +# +# allows Debian's bug tools to include relevant information in bug reports. +# +# Copyright © martin f. krafft +# distributed under the terms of the Artistic Licence 2.0 +# +# $Id: bugscript 292 2007-01-08 01:04:21Z madduck $ +# +set -eu + +if [ ! -r /proc/mdstat ]; then + echo "The local system does not have MD (RAID) support: no drivers loaded." + echo "Without MD support, I cannot collect as much information as I'd like." + + #yesno "Are you sure you want to report a bug at this time? " yep + yesno "Hit any key to continue..." + #[ "$REPLY" = yep ] || exit 1 +fi + +echo "--- mount output" >&3 +mount >&3 +echo >&3 + +echo "--- mdadm.conf" >&3 +if [ -r /etc/mdadm/mdadm.conf ]; then + cat /etc/mdadm/mdadm.conf >&3 +else + echo no mdadm.conf file. >&3 +fi +echo >&3 + +echo "--- /proc/mdstat:" >&3 +cat /proc/mdstat >&3 2>&3 || : +echo >&3 + +echo "--- /proc/partitions:" >&3 +cat /proc/partitions >&3 2>&3 || : +echo >&3 + +echo "--- initrd.img-$(uname -r):" >&3 +if [ -r /boot/initrd.img-$(uname -r) ]; then + zcat /boot/initrd.img-$(uname -r) 2>&3 | cpio -t 2>&3 | egrep '/md[a/]' >&3 +fi +echo >&3 + +if [ -r /proc/modules ]; then + echo "--- /proc/modules:" >&3 + egrep '(dm_|raid|linear|multipath|faulty)' < /proc/modules >&3 || : + echo >&3 +fi + +if [ -r /var/log/syslog ]; then + echo "--- /var/log/syslog:" >&3 + egrep "^\w{3} [ :[:digit:]]{11} ($(hostname)|localhost) (kernel: md|mdadm): " /var/log/syslog >&3 || : + echo >&3 +fi + +echo "--- volume detail:" >&3 +for dev in /dev/[hs]d[a-z]*; do mdadm -E $dev 2>/dev/null && echo -- || :; done >&3 +echo >&3 + +if [ -r /proc/cmdline ]; then + echo "--- /proc/cmdline" >&3 + cat /proc/cmdline >&3 + echo >&3 +fi + +if [ -f /boot/grub/menu.lst ]; then + echo "--- grub:" >&3 + if [ -r /boot/grub/menu.lst ]; then + grep '^[^#].*root=' /boot/grub/menu.lst >&3 || : + else + echo menu.lst file not readable. >&3 + fi + echo >&3 +fi + +if [ -f /etc/lilo.conf ]; then + echo "--- lilo:" >&3 + if [ -r /etc/lilo.conf ]; then + egrep '^([^#].*)?root=' /etc/lilo.conf >&3 || : + else + echo lilo.conf file not readable. >&3 + fi + echo >&3 +fi --- mdadm-2.6.2.orig/debian/NEWS +++ mdadm-2.6.2/debian/NEWS @@ -0,0 +1,52 @@ +mdadm (2.5.3.git200608201206-1) unstable; urgency=low + + This version makes mdadm.conf mandatory. If you do not have such a file, it + will be created for you. + + You must verify the contents of this file and ensure that it represents your + local configuration. See /usr/share/doc/mdadm/README.upgrading-2.5.3.gz for + more information. + + -- martin f. krafft Sun, 20 Aug 2006 21:58:43 +0100 + +mdadm (2.5-1) unstable; urgency=low + + mdrun has been (finally) obsoleted, and an appropriate warning message is + written to the console if you (or a script) attempts to run it. If you + cannot live without mdrun, you can disable the warning by setting + USE_DEPRECATED_MDRUN=1 in /etc/default/mdadm. Note that mdrun will *not* be + supported. Please also see /usr/share/doc/mdadm/README.mdrun . + + -- martin f. krafft Tue, 30 May 2006 23:25:13 +0200 + +mdadm (2.4.1-5) unstable; urgency=low + + This version drops the automatic generation of the /etc/mdadm/mdadm.conf + file on every boot (if it was missing). This means that you need to ensure + that you have a valid configuration file. If none is present during package + configuration, mdadm *will* try to generate one, but it will only contain + information about arrays that were running at the time of package + configuration. Arrays not listed in the configuration file will *not* be + started automatically after boot (with the exception of the root partition). + + If you want to recreate your configuration file, either figure out what it + should contain from the mdadm.conf(5) manpage, or simply assemble and run + all the arrays the way you like it, then run + /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf + + -- martin f. krafft Sat, 03 Jun 2006 17:45:47 +0200 + +mdadm (2.4.1-1) unstable; urgency=low + + As of version 2.3, mdadm uses /etc/mdadm.conf as its main configuration + file, and falls back to /etc/mdadm/mdadm.conf if the former is not found. + Since Debian uses /etc/mdadm/mdadm.conf as the configuration file path, this + order was reverted: Debian's mdadm reads /etc/mdadm/mdadm.conf as its main + file and falls back to /etc/mdadm.conf if the former is not found. + + An incompatible change in the reshaping of RAID 5 arrays was made in this + upstream release. If you want to reshape a RAID 5 array with a version-1 + superblock, please make sure to use mdadm 2.4.1 and at least a 2.6.17-rc2 + kernel. + + -- martin f. krafft Tue, 16 May 2006 13:07:49 -0500 --- mdadm-2.6.2.orig/debian/mdadm-udeb.dirs +++ mdadm-2.6.2/debian/mdadm-udeb.dirs @@ -0,0 +1,2 @@ +sbin +usr/share/lintian/overrides