linux/mdadm
1
0
Fork 0
Code Issues Activity

Adding debian version 4.2-5.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-14 05:52:43 +01:00
parent 4fd4995b67
commit 866376462c
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
77 changed files with 9174 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

669
debian/FAQ vendored Normal file
View file

@ -0,0 +1,669 @@
Frequently asked questions -- Debian mdadm
==========================================
Also see /usr/share/doc/mdadm/README.recipes.gz .
The latest version of this FAQ is available here:
http://anonscm.debian.org/gitweb/?p=pkg-mdadm/mdadm.git;a=blob_plain;f=debian/FAQ;hb=HEAD
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 (typically but not necessarily physical) block 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" 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/sdXY
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 want ot re-use a device (e.g. a HDD or SSD) that has been part of an
array (with an different superblock version and/or location) in another one.
In this case you zero the superblock before you assemble the array or add
the device to a new 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.
WARNING: Depending on which superblock version you use, it won't work to just
overwrite the first few MiBs of the block device with 0x0 (e.g. via
dd), since the superblock may be at other locations (especially the
end of the device).
Therefore always use mdadm --zero-superblock .
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(8)
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<MINOR> if the device node
/dev/md<MINOR> exists.
Otherwise, it outputs /dev/md/<MINOR>
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?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Many people seem to prefer RAID4/5/6 because it makes more efficient use of
space. For example, if you have devices of size X, then in order to get 2X
storage, you need 3 devices for RAID5, but 4 if you use RAID10 or RAID1+ (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 devices. In a RAID10 configuration, if one device is
already dead, the RAID can only survive if any of the two devices in the other
RAID1 array fails, but not if the second device in the degraded RAID1 array
fails (see next item, 4b). A RAID6 across four devices can cope with any two
devices failing. However, RAID6 is noticeably slower than RAID5. RAID5 and
RAID4 do not differ much, but can only handle single-device failures.
If you can afford the extra devices (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 device-intensive brings the system to its
knees; I will have to migrate to RAID10 at one point.
Please also consult /usr/share/doc/mdadm/RAID5_versus_RAID10.txt.gz,
https://en.wikipedia.org/wiki/Standard_RAID_levels and perhaps even
https://en.wikipedia.org/wiki/Non-standard_RAID_levels .
4b. Can a 4-device RAID10 survive two device failures?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am assuming that you are talking about a setup with two copies of each
block, so --layout=near2/far2/offset2:
In two thirds of the cases, yes[0], and it does not matter which layout you
use. When you assemble 4 devices into a RAID10, you essentially stripe a RAID0
across two RAID1, so the four devices A,B,C,D become two pairs: A,B and C,D.
If A fails, the RAID10 can only survive if the second failing device is either
C or D; if B fails, your array is dead.
Thus, if you see a device failing, replace it as soon as possible!
If you need to handle two failing devices 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 (n-2)/(n-1), where n is the number of devices. I am not
a mathematician, see http://aput.net/~jheiss/raid10/, which gives the
chance of *failure* as 1/(n-1), so the chance of success is 1-1/(n-1), or
(n-2)/(n-1), or 2/3 in the four device example.
(Thanks to Per Olofsson for clarifying this in #493577).
5. How to convert RAID5 to RAID10?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To convert 3 device RAID5 to RAID10, you need a spare device (either a hot
spare, fourth device in the array, or a new one). Then you remove the spare
and one of the three devices 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 devices 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 devices, 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://thread.gmane.org/gmane.linux.raid/13469/focus=13472
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 devices, RAID10 can be
configured to work with only 3 devices. 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 device failures, its
performance suffers less when in degraded state, and it resyncs faster after
replacing a failed device.
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 chunks on the
devices: near, far and offset.
The examples below explain the chunk distribution for each of these layouts
with 2 copies per chunk, using either an even number of devices (fewer than 4)
or an odd number (fewer than 5).
For simplicity we assume that the chunk size matches the block size of the
underlying devices and also the RAID10 device exported by the kernel
(e.g. /dev/md/name). The chunk numbers map therefore directly to the block
addresses in the exported RAID10 device.
The decimal numbers below (0, 1, 2, …) are the RAID10 chunks. Due to the
foregoing assumption they are also the block addresses in the exported RAID10
device. Identical numbers refer to copies of a chunk or block, but on different
underlying devices. The hexadecimal numbers (0x00, 0x01, 0x02, …) refer to the
block addresses in the underlying devices.
"near" layout with 2 copies per chunk (--layout=n2):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The chunk copies are placed "as close to each other as possible".
With an even number of devices, they lie at the same offset on the each device.
It is a classic RAID1+0 setup, i.e. two groups of mirrored devices, with both
forming a striped RAID0.
device1 device2 device3 device4 device1 device2 device3 device4 device5
─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ───────
0 0 1 1 0x00 0 0 1 1 2
2 2 3 3 0x01 2 3 3 4 4
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯
⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯
254 254 255 255 0x80 317 318 318 319 319
╰──────┬──────╯ ╰──────┬──────╯
RAID1 RAID1
╰──────────────┬──────────────╯
RAID0
"far" layout with 2 copies per chunk (--layout=f2):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The chunk copies are placed "as far from each other as possible".
Here, a complete sequence of chunks is striped over all devices. Then a second
sequence of chunks is placed next to them. More copies are added as the number
2 goes up.
It is undesirable, however, to place copies of the same chunks on the same
devices. That is prevented by a cyclic permutation of each such stripe.
device1 device2 device3 device4 device1 device2 device3 device4 device5
─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ───────
0 1 2 3 0x00 0 1 2 3 4 ╮
4 5 6 7 0x01 5 6 7 8 9 ├ ▒
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ┆
⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ┆
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ┆
252 253 254 255 0x40 315 316 317 318 319 ╯
3 0 1 2 0x41 4 0 1 2 3 ╮
7 4 5 6 0x42 9 5 6 7 8 ├ ▒ₚ
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ┆
⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ┆
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ┆
255 252 253 254 0x80 319 315 316 317 318 ╯
Each ▒ in the diagram represents a complete sequence of chunks. ▒ₚ is a cyclic
permutation.
A major advantage of the "far" layout is that sequential reads can be spread
out over different devices, which makes the setup similar to RAID0 in terms of
speed. For writes, there is a cost of seeking. They are substantially slower.
"offset" layout with 2 copies per chunk (--layout=o2):
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here, a number of consecutive chunks are bundled on each device during the
striping operation. The number of consecutive chunks equals the number of
devices. Next, a copy of the same chunks is striped in a different pattern.
More copies are added as the number 2 goes up.
A cyclic permutation in the pattern prevents copies of the same chunks
landing on the same devices.
device1 device2 device3 device4 device1 device2 device3 device4 device5
─────── ─────── ─────── ─────── ─────── ─────── ─────── ─────── ───────
0 1 2 3 0x00 0 1 2 3 4 ) AA
3 0 1 2 0x01 4 0 1 2 3 ) AAₚ
4 5 6 7 0x02 5 6 7 8 9 ) AB
7 4 5 6 0x03 9 5 6 7 8 ) ABₚ
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ) ⋯
⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮ ⋮
⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ⋯ ) ⋯
251 252 253 254 0x79 314 315 316 317 318 ) EX
254 251 252 253 0x80 318 314 315 316 317 ) EXₚ
With AA, AB, …, AZ, BA, … being the sets of consecutive chunks and
AAₚ, ABₚ, …, AZₚ, BAₚ, … their cyclic permutations.
The read characteristics are probably similar to the "far" layout when a
suitably large chunk size is chosen, but with less seeking for writes.
Upstream and the Debian maintainer do not understand all the nuances and
implications. The "offset" layout was only added because the Common
RAID Data Disk Format (DDF) supports it, and standard compliance is our
goal.
See the md(4) manpage for more details.
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 contains a swap partition used for suspend-to-ram
(check /etc/initramfs-tools/conf.d/resume)
* 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 devices, you
increase the likelyhood of complete loss of the filesystem by a factor of X.
The same applies to LVM by the way (when LVs are placed over X PVs).
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 device, mdadm may display a warning like:
mdadm: WARNING /dev/sdXY and /dev/sdX 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 istead of:
DEVICE partitions
for example:
DEVICE /dev/sd[ab]* /dev/sdc[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?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Since kernel 2.6.28, MD arrays can be partitioned like any other block
device.
Prior to 2.6.28, 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 partition an array?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 device fails, the *entire* device 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 device RAID5 array. If a device
fails and you are using a partitioned MD array, then all the partitions on
the device will already be handled without using that device. 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 device, and that device fails, but it only failed on one array, then
you now need to manually fail that device from the other arrays before
shutting down or hot swapping the device. 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 device, and
when you then go to remove the device you create a two device 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 device as possible, then
OK. But, generally speaking, people that have something of value on their
devices don't want to salvage any part of a failing device, they want that
device gone and replaced immediately. There simply is little to no value in
an already malfunctioning device. 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 device issues, so anything that will throw a device out of an array is
more than just a minor sector glitch.
[0] http://thread.gmane.org/gmane.linux.raid/13594/focus=13597
15. How can I start a dirty degraded array?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A degraded array (e.g. a RAID5 with only two devices) 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 devics can a RAID10 handle?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(see also question 4b)
The following table shows how many devices you can lose and still have an
operational array. In some cases, you *can* lose more than the given number
of devices, but there is no guarantee that the array survives. Thus, the
following is the guaranteed number of failed devices a RAID10 array survives
and the maximum number of failed devices the array can (but is not guaranteed
to) handle, given the number of devices 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 devices)
Note: I have not really verified the above information. Please don't count
on it. If a device fails, replace it as soon as possible. Corrections welcome.
19. What should I do if a device fails?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Replace it as soon as possible.
In case of physical devices with no hot-swap capabilities, for example via:
mdadm --remove /dev/md0 /dev/sda1
poweroff
<replace device and start the machine>
mdadm --add /dev/md0 /dev/sda1
20. So how do I find out which other device(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 4 device
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 degraded; 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 7 device 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 devices to it, so in order to determine groups,
you need to round up. Note how the devices are arranged in decreasing order of
their indices (the number in brackes in /proc/mdstat):
device: -sdd7- -sdc7- -sdf7- -sda7- -sde7- -sdb7- -sdg7-
group: [ one ][ two ][ three ]
Basically this means that after two devices failed, you need to make sure that
the third failed device 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://thread.gmane.org/gmane.linux.raid/11864 .
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.
23. mdadm's init script fails because it cannot find any arrays. What gives?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This does not happen anymore, if no arrays present in config file, no arrays
will be started.
24. What happened to mdrun? How do I replace it?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mdrun used to be the sledgehammer approach to assembling arrays. It has
accumulated several problems over the years (e.g. Debian bug #354705) and
thus has been deprecated and removed with the 2.6.7-2 version of this package.
If you are still using mdrun, please ensure that you have a valid
/etc/mdadm/mdadm.conf file (run /usr/share/mdadm/mkconf --generate to get
one), and run
mdadm --assemble --scan --auto=yes
instead of mdrun.
25. Why are my arrays marked auto-read-only in /proc/mdstat?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Arrays are kept read-only until the first write occurs. This allows md to
skip lengthy resynchronisation for arrays that have not been properly shut
down, but which also not have changed.
26. Why doesn't mdadm find arrays specified in the config file and causes the
boot to fail?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
My boot process dies at an early stage and drops me into the busybox shell.
The last relevant output seems to be from mdadm and is something like
"/dev/md2 does not exist"
or
"No devices listed in conf file found"
Why does mdadm break my system?
Short answer: It doesn't, the underlying devices aren't yet available yet
when mdadm runs during the early boot process.
Long answer: It doesn't, but the drivers of those devices incorrectly
communicate to the kernel that the devices are ready, when in fact they are
not. I consider this a bug in those drivers. Please consider reporting it.
Workaround: there is nothing mdadm can or will do against this. Fortunately
though, initramfs provides a method, documented at
http://wiki.debian.org/InitramfsDebug. Please append rootdelay=10 (which sets
a delay of 10 seconds before trying to mount the root filesystem) to the
kernel command line and try if the boot now works.
-- martin f. krafft <madduck@debian.org> Wed, 13 May 2009 09:59:53 +0200

107
debian/NEWS vendored Normal file
View file

@ -0,0 +1,107 @@
mdadm (3.2.2-1) unstable; urgency=low
Metadata format change requires recent Grub
The following only applies to users who want to let the grub-pc bootloader
load the kernel directly off a RAID device created with mdadm 3.x and
default values, or when the metadata version is explicitly set using -e.
Specifically, this includes all arrays created during or after the
installation of Debian squeeze (mdadm-3.1.4+8efb9d1). Arrays created with
older mdadm versions, and RAIDs created with the command-line option
-e 0.9 are not affected.
Versions of grub-pc older than 1.98+20100720-1 will not be able to boot
directly off a RAID with the 1.x metadata formats (the new default is 1.2).
To ensure a bootable system, please make sure to use grub-pc 1.98+20100720-1
or later, which is provided by Debian squeeze. An unbootable system may be
rescued with Super Grub2 Disk (http://www.supergrubdisk.org/super-grub2-disk/)
or grml (http://grml.org/).
-- Scott Schaefer <saschaefer@neurodiverse.org> Wed, 27 Jul 2011 20:21:50 -0400
mdadm (3.1.4-1+8efb9d1) unstable; urgency=low
Default metadata format for newly created arrays has changed from
0.90 to 1.2. Location of the superblock is now 4Kb from the start
of the device, instead of at the end of the device for 0.90.
The change from 0.9 to 1.x lifted many restrictions of the old
metadata format, and change in location (from end to 4k after
start for 1.2) reduced chances to confuse a raid array with
filesystem inside it. It is now less easy to mount a component
device as separate filesystem by incident, thus destroying the
array.
Also, chunk size by default is 512K (was 64K) and bitmap chunk size
is 64Mb.
-- Michael Tokarev <mjt@tls.msk.ru> Sat, 10 Sep 2011 13:35:12 +0400
mdadm (2.6.7-2) unstable; urgency=low
/dev/disk symlinks:
mdadm now creates symlinks in /dev/disk/by-id, using the template
md-uuid-* for the array UUIDs and md-name-* for any names assigned to
arrays (version-1 superblocks only). Thanks to Suse for the udev rules
file.
mdrun removed:
This version also removes mdrun once and for all. If you are still using
mdrun, please ensure that you have a valid /etc/mdadm/mdadm.conf file (run
/usr/share/mdadm/mkconf --generate to get one), and run
mdadm --assemble --scan --auto=yes
-- martin f. krafft <madduck@debian.org> Wed, 02 Jul 2008 10:57:32 +0200
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 <madduck@debian.org> 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 <madduck@debian.org> 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 <madduck@debian.org> 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 <madduck@debian.org> Tue, 16 May 2006 13:07:49 -0500

33
debian/README.checkarray vendored Normal file
View file

@ -0,0 +1,33 @@
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.
Cron will try to run the check at "idle I/O priority" (see ionice(1)), so that
the check does not overload the system too much. Note that this will only
work if all the component devices of the array employ the (default) "cfq" I/O
scheduler. See the kernel documentation[0] for information on how to verify
and modify the scheduler. checkarray does not verify this for you.
0. http://www.kernel.org/doc/Documentation/block/switching-sched.txt
If you manually invoke checkarray, it runs with default I/O priority. Should
you need to run a check at a higher (or lower) I/O priority, then have a look
at the --idle, --slow, --fast, and --realtime options.
'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 <madduck@debian.org> Thu, 02 Sep 2010 10:27:29 +0200

168
debian/README.recipes vendored Normal file
View file

@ -0,0 +1,168 @@
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://git.debian.org/?p=pkg-mdadm/mdadm.git;a=blob;f=debian/README.recipes;hb=HEAD
The short options used here are:
-l Set RAID level.
-n Number of active devices in the array.
-x Specify the number of spare (eXtra) devices in the initial array.
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 <type> /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
Warren Togami has a document explaining how to convert a filesystem on
a remote system via SSH: http://togami.com/~warren/guides/remoteraidcrazies/
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 <type> /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 <madduck@debian.org> Fri, 06 Oct 2006 15:39:58 +0200

29
debian/TODO vendored Normal file
View file

@ -0,0 +1,29 @@
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/<arrayname>.
- 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

219
debian/bug-submission/script vendored Executable file
View file

@ -0,0 +1,219 @@
#!/bin/bash
#
# mdadm bug submission control script
#
# allows Debian's bug tools to include relevant information in bug reports.
#
# Copyright © martin f. krafft <madduck@debian.org>
# distributed under the terms of the Artistic Licence 2.0
#
# we need /bin/bash for readline and -n capabalities in the prompt(s)
#
# maximise information output even in the case of errors
set +eu
if ! command -v yesno >/dev/null; then
if [ -r /usr/share/reportbug/handle_bugscript ]; then
exec /usr/share/reportbug/handle_bugscript ". $0" /dev/stdout
fi
yesno() {
read -n1 -p"$1" REPLY
case "$REPLY" in
[yY]) REPLY=yep;;
[nN]) REPLY=nop;;
('') REPLY="$2";;
esac
}
exec 3>&1
fi
# do not let people ctrl-c out of the bugscript
trap : INT
if [ $(id -u) != 0 ]; then
if [ -x "$(command -v sudo)" ]; then
yesno "Gather system information as root using sudo? (Y/n) " yep
if [ "$REPLY" = yep ]; then
echo running sudo "$0" "$@"...
sudo "$0" "$@" >&3 && exit 0
echo "sudo invocation failed, trying /bin/su..."
fi
fi
yesno "Gather system information as root using su? (Y/n) " yep
if [ "$REPLY" = yep ]; then
ARGS=
for i in "$@"; do ARGS="${ARGS:+$ARGS }'$1'"; shift; done
echo "running su root -s '/bin/sh -c $0${ARGS:+ $ARGS}'..."
su root -s /bin/sh -c "$0 $ARGS" >&3 && exit 0
unset ARGS
echo "su invocation failed."
fi
# arrive here only if neither sudo nor su worked:
yesno "Will you provide system information in the bug report yourself? (N/y) " nop
if [ "$REPLY" = yep ]; then
cat <<_eof >&3
IMPORTANT:
please do not forget to include all relevant system information with this
bug report. You could run
/usr/share/bug/mdadm/script 3>&1
as root and attach or include the output.
_eof
exit 0
fi
# try our best
cat <<_eof >&3
WARNING:
the following output was not generated by the root user. If you can, please
replace the following up until "-- System Information:" with the output of
/usr/share/bug/mdadm/script 3>&1
run as root. Thanks!
_eof
fi
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..." yep
#[ "$REPLY" = yep ] || exit 1
fi
echo "--- mdadm.conf" >&3
if [ -r /etc/mdadm/mdadm.conf ]; then
grep '^[^#]' /etc/mdadm/mdadm.conf >&3
elif [ -r /etc/mdadm.conf ]; then
grep '^[^#]' /etc/mdadm.conf >&3
else
echo no mdadm.conf file. >&3
fi
echo >&3
echo "--- /etc/default/mdadm" >&3
if [ -r /etc/default/mdadm ]; then
grep '^[^#]' /etc/default/mdadm >&3
else
echo no /etc/default/mdadm 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 "--- LVM physical volumes:" >&3
if [ -x "$(command -v pvs)" ]; then
pvs >&3
else
echo "LVM does not seem to be used." >&3
fi
echo "--- mount output" >&3
mount >&3
echo >&3
echo "--- initrd.img-$(uname -r):" >&3
if [ -r /boot/initrd.img-$(uname -r) ]; then
TEMPDIR=$(mktemp -d)
OLDPWD="$PWD"
cd "$TEMPDIR"
zcat /boot/initrd.img-$(uname -r) 2>&3 | cpio -i 2>&3
find -regex '.*/md[a/].+' -type f -exec md5sum {} \; >&3
echo >&3
echo "--- initrd's /conf/conf.d/md:" >&3
if [ -r conf/conf.d/md ]; then
cat conf/conf.d/md >&3
else
echo "no conf/md file." >&3
fi
cd "$OLDPWD"
rm -rf "$TEMPDIR"
unset TEMPDIR
else
echo "no initrd.img-$(uname -r) found." >&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 [ -f /var/log/syslog ]; then
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
else
echo "syslog not readable by user." >&3
fi
fi
echo "--- volume detail:" >&3
for dev in /dev/[hsv]d[a-z]*; do
[ ! -r $dev ] && echo "$dev not readable by user." && continue
mdadm -E $dev 2>/dev/null && echo -- || echo "$dev is not recognised by mdadm."
done >&3
echo >&3
if [ -r /proc/cmdline ]; then
echo "--- /proc/cmdline" >&3
cat /proc/cmdline >&3
echo >&3
fi
if [ -f /boot/grub/grub.cfg ]; then
echo "--- grub2:" >&3
if [ -r /boot/grub/grub.cfg ]; then
egrep '^[^#].*\<(root=|raid)' /boot/grub/grub.cfg >&3 || :
else
echo grub.cfg file not readable. >&3
fi
echo >&3
fi
if [ -f /boot/grub/menu.lst ]; then
echo "--- grub legacy:" >&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
echo "--- udev:" >&3
COLUMNS=70 dpkg -l udev | grep '\<udev\>' >&3
md5sum /etc/udev/rules.d/*md* /lib/udev/rules.d/*md* >&3 2>/dev/null
echo >&3
echo "--- /dev:" >&3
ls -l /dev/md* /dev/disk/by-* >&3
echo >&3
echo "Auto-generated on $(date -R) by mdadm bugscript" >&3

2240
debian/changelog vendored Normal file
View file

File diff suppressed because it is too large Load diff

221
debian/checkarray vendored Executable file
View file

@ -0,0 +1,221 @@
#!/bin/sh
#
# checkarray -- initiates a check run of an MD array's redundancy information.
#
# Copyright © martin f. krafft <madduck@debian.org>
# distributed under the terms of the Artistic Licence 2.0
#
set -eu
PROGNAME=${0##*/}
about()
{
echo "\
$PROGNAME -- MD array (RAID) redundancy checker tool
Copyright © martin f. krafft <madduck@debian.org>
Released under the terms of the Artistic Licence 2.0"
}
usage()
{
about
echo "
Usage: $PROGNAME [options] [arrays]
Valid options are:
-a|--all check all assembled arrays (ignores arrays in command line).
-s|--status print redundancy check status of devices.
-x|--cancel queue a request to cancel a running redundancy check.
-r|--repair repair instead of check
-i|--idle perform check in a lowest scheduling class (idle)
-l|--slow perform check in a lower-than-standard scheduling class
-f|--fast perform check in higher-than-standard scheduling class
--realtime perform check in real-time scheduling class (DANGEROUS!)
-c|--cron honour AUTOCHECK setting in /etc/default/mdadm.
-q|--quiet suppress informational messages
(use twice to suppress error messages too).
-h|--help show this output.
-V|--version show version information.
Examples:
$PROGNAME --all --idle
$PROGNAME --quiet /dev/md[123]
$PROGNAME -sa
$PROGNAME -x --all
Devices can be specified in almost any format. The following are equivalent:
/dev/md0, md0, /dev/md/0, /sys/block/md0
You can also control the status of a check/repair with /proc/mdstat file."
}
SHORTOPTS=achVqQsxrilf
LONGOPTS=all,cron,help,version,quiet,real-quiet,status,cancel,repair,idle,slow,fast,realtime
eval set -- $(getopt -o $SHORTOPTS -l $LONGOPTS -n $PROGNAME -- "$@")
arrays=''
cron=0
all=0
quiet=0
status=0
action=check
ionice=
for opt in $@; do
case "$opt" in
-a|--all) all=1;;
-s|--status) action=status;;
-x|--cancel) action=idle;;
-r|--repair) action=repair;;
-i|--idle) ionice=idle;;
-l|--slow) ionice=low;;
-f|--fast) ionice=high;;
--realtime) ionice=realtime;;
-c|--cron) cron=1;;
-q|--quiet) quiet=$(($quiet+1));;
-Q|--real-quiet) quiet=$(($quiet+2));; # for compatibility
-h|--help) usage; exit 0;;
-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. Try --help." >&2; exit 1;;
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
if [ $quiet -lt 2 ] && [ $cron != 1 ]; then
echo "$PROGNAME: W: no active MD arrays found." >&2
echo "$PROGNAME: W: (maybe uninstall the mdadm package?)" >&2
fi
exit 0
fi
if [ -z "$(ls /sys/block/md*/md/level 2>/dev/null)" ]; then
[ $quiet -lt 2 ] && echo "$PROGNAME: E: 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: E: 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
MDBASE=/sys/block/$array/md
if [ ! -e $MDBASE/sync_action ]; then
[ $quiet -lt 1 ] && echo "$PROGNAME: I: skipping non-redundant array $array." >&2
continue
fi
cur_status="$(cat $MDBASE/sync_action)"
if [ $action = status ]; then
echo "$array: $cur_status"
continue
fi
if [ ! -w $MDBASE/sync_action ]; then
[ $quiet -lt 2 ] && echo "$PROGNAME: E: $MDBASE/sync_action not writeable." >&2
exit 4
fi
if [ "$(cat $MDBASE/array_state)" = 'read-auto' ]; then
[ $quiet -lt 1 ] && echo "$PROGNAME: W: array $array in auto-read-only state, skipping..." >&2
continue
fi
case "$action" in
idle)
echo $action > $MDBASE/sync_action
[ $quiet -lt 1 ] && echo "$PROGNAME: I: cancel request queued for array $array." >&2
;;
check|repair)
if [ "$cur_status" != idle ]; then
[ $quiet -lt 2 ] && echo "$PROGNAME: W: array $array not idle, skipping..." >&2
continue
fi
# check if the array created recently and skip test if it is
created=$(mdadm --detail /dev/$array 2>/dev/null |
sed -n 's/.*Creation Time *://p' )
if [ -n "$created" ]; then
created=$(date +%s -d "$created" 2>/dev/null)
fi
if [ -n "$created" ]; then
now=$(date +%s)
if [ "$created" -lt "$now" -a \
"$created" -gt "$(($now - 14 * 24 * 60 * 60))" ]; then
[ $quiet -lt 2 ] && echo "$PROGNAME: I: array $array created recently, skipping..." >&2
continue
fi
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 arrays.
echo $action > $MDBASE/sync_action
[ $quiet -lt 1 ] && echo "$PROGNAME: I: $action queued for array $array." >&2
case "$ionice" in
idle) ioarg='-c3'; renice=15;;
low) ioarg='-c2 -n7'; renice=5;;
high) ioarg='-c2 -n0'; renice=0;;
realtime) ioarg='-c1 -n4'; renice=-5;;
*) continue;;
esac
resync_pid= wait=5
while [ $wait -gt 0 ]; do
wait=$((wait - 1))
resync_pid=$(ps -ef | awk -v dev=$array 'BEGIN { pattern = "^\\[" dev "_resync]$" } $8 ~ pattern { print $2 }')
if [ -n "$resync_pid" ]; then
[ $quiet -lt 1 ] && echo "$PROGNAME: I: selecting $ionice I/O scheduling class and $renice niceness for resync of $array." >&2
ionice -p "$resync_pid" $ioarg 2>/dev/null || :
renice -n $renice -p "$resync_pid" 1>/dev/null 2>&1 || :
break
fi
sleep 1
done
;;
esac
done
exit 0

50
debian/control vendored Normal file
View file

@ -0,0 +1,50 @@
Source: mdadm
Section: admin
Priority: optional
Maintainer: Daniel Baumann <daniel.baumann@progress-linux.org>
Build-Depends:
debhelper-compat (= 13),
libudev-dev,
groff-base,
po-debconf
Standards-Version: 4.6.1
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/debian/mdadm.git -b debian/master
Vcs-Browser: https://salsa.debian.org/debian/mdadm
Homepage: https://raid.wiki.kernel.org/index.php/Linux_Raid
Package: mdadm
Architecture: linux-any
Pre-Depends:
${misc:Pre-Depends}
Depends:
${misc:Depends},
${shlibs:Depends},
debconf,
lsb-base,
udev
Recommends:
${mta:Recommends},
kmod | module-init-tools
Suggests:
${mta:Suggests},
dracut-core
Description: Tool to administer Linux MD arrays (software RAID)
The mdadm utility can be used to create, manage, and monitor MD
(multi-disk) arrays for software RAID or multipath I/O.
.
This package automatically configures mdadm to assemble arrays during the
system startup process. If not needed, this functionality can be disabled.
Package: mdadm-udeb
Section: debian-installer
Package-Type: udeb
Architecture: linux-any
Depends:
${shlibs:Depends},
${misc:Depends}
Description: Tool to administer Linux MD arrays (software RAID)
The mdadm utility can be used to create, manage, and monitor MD
(multi-disk) arrays for software RAID or multipath I/O.
.
This is a minimal package used by the debian-installer.

25
debian/copyright vendored Normal file
View file

@ -0,0 +1,25 @@
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: mdadm
Upstream-Contact: Neil Brown <neilb@suse.de>
Source: https://www.kernel.org/pub/linux/utils/raid/mdadm/
Files: *
Copyright:
© 2001-2006 Neil Brown <neilb@suse.de>
License: GPL-2+
Files: debian/*
Copyright:
© 2001-2005 Mario Jou/3en <joussen@debian.org>
© 2005-2008 Martin F. Krafft <madduck@debian.org>
© 2020 Felix Lechner <felix.lechner@lease-up.com>
License: GPL-2+
License: GPL-2+
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-2'.

61
debian/initramfs/scripts/local-block/mdadm vendored Executable file
View file

@ -0,0 +1,61 @@
#!/bin/sh
PREREQ="multipath"
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
# Poor man's mdadm-last-resort@.timer
# That kicks in 2/3rds into the ROOTDELAY
if [ ! -f /run/count.mdadm.initrd ]
then
COUNT=0
# Unfortunately raid personalities can be registered _after_ block
# devices have already been added, and their rules processed, try
# triggering again. See #830770
udevadm trigger --action=add -s block || true
wait_for_udev 10
else
COUNT=$(cat /run/count.mdadm.initrd)
fi
COUNT=$((COUNT + 1))
echo $COUNT > /run/count.mdadm.initrd
# Run pure assemble command, even though we default to incremental
# assembly it is supported for users to export variables via
# param.conf such as IMSM_NO_PLATFORM. See #830300
mdadm -q --assemble --scan --no-degraded || true
MAX=30
if [ ${ROOTDELAY:-0} -gt $MAX ]; then
MAX=$ROOTDELAY
fi
MAX=$((MAX*2/3))
if [ "$COUNT" = "$MAX" ]
then
# Poor man's mdadm-last-resort@.service for incremental devices
mdadm -q --run /dev/md?*
# And last try for all others
mdadm -q --assemble --scan --run
rm -f /run/count.mdadm.initrd
fi
exit 0

3
debian/initramfs/scripts/local-bottom/mdadm vendored Executable file
View file

@ -0,0 +1,3 @@
#!/bin/sh
rm -f /run/count.mdadm.initrd
exit 0

2
debian/mdadm-udeb.install vendored Normal file
View file

@ -0,0 +1,2 @@
sbin/
lib/udev/rules.d/63-md-raid-arrays.rules

60
debian/mdadm-waitidle vendored Normal file
View file

@ -0,0 +1,60 @@
#!/bin/sh
# This script is not used when systemd is running
### BEGIN INIT INFO
# Provides: mdadm-waitidle
# Required-Start:
# Required-Stop:
# Should-Stop: halt reboot kexec
# X-Stop-After: umountroot
# Default-Start:
# Default-Stop: 0 6
# Short-Description: Wait for MD arrays to become idle
# Description: Waits until all MD arrays are in idle and synced state
# before halt/reboot.
### END INIT INFO
#
set -eu
MDADM=/sbin/mdadm
test -x "$MDADM" || exit 0
test -f /proc/mdstat || exit 0
. /lib/lsb/init-functions
case "${1:-}" in
start|restart|force-reload)
# nothing, the only reason the script is here is to stop arrays
;;
stop)
sync
wait=
for md in /sys/block/md*/md ; do
[ -d "$md" ] || continue
[ "$wait" ] || log_action_begin_msg "Waiting for MD arrays to become idle"
wait=y
[ -w $md/sync_action ] && echo idle > $md/sync_action
done
if [ "$wait" ]; then
# mdadm --wait-clean has a short internal timeout
if $MDADM --wait-clean --scan; then
log_action_end_msg 0
else
log_action_end_msg 1
sleep 1
fi
fi
;;
status)
status_of_proc /usr/bin/$NAME $NAME
;;
*)
echo "Usage: ${0:-} stop" >&2
exit 1;;
esac
exit 0

48
debian/mdadm.config vendored Normal file
View file

@ -0,0 +1,48 @@
#!/bin/sh
# Copyright © 2001-2004 Mario Jou/3en <joussen@debian.org>
# Copyright © martin f. krafft <madduck@debian.org>
# Distributable under the terms of the GNU GPL version 2.
#
. /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
if [ -s $DEBIANCONFIG ] ; then
AUTOCHECK=true
AUTOSCAN=true
START_DAEMON=true
MAILADDR=root
[ -f $DEBIANCONFIG ] && . $DEBIANCONFIG
if [ -f $CONFIG ]; then
MAILADDR=$(sed -rne 's/^MAILADDR[[:space:]]*([^[:space:]]+).*/\1/p' $CONFIG)
fi
[ -n "$AUTOCHECK" ] && db_set mdadm/autocheck "$AUTOCHECK"
[ -n "$AUTOSCAN" ] && db_set mdadm/autoscan "$AUTOSCAN"
[ -n "$START_DAEMON" ] && db_set mdadm/start_daemon "$START_DAEMON"
[ -n "$MAILADDR" ] && db_set mdadm/mail_to "$MAILADDR"
fi
db_capb escape
db_input medium mdadm/autocheck || :
db_go
db_input medium mdadm/autoscan || :
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

12
debian/mdadm.cron.d vendored Normal file
View file

@ -0,0 +1,12 @@
#
# cron.d/mdadm -- schedules periodic redundancy checks of MD devices
#
# Copyright © martin f. krafft <madduck@madduck.net>
# distributed under the terms of the Artistic Licence 2.0
#
# By default, run at 00:57 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).
57 0 * * 0 root if [ -x /usr/share/mdadm/checkarray ] && [ $(date +\%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi

21
debian/mdadm.cron.daily vendored Normal file
View file

@ -0,0 +1,21 @@
#!/bin/sh
#
# cron.daily/mdadm -- daily check that MD devices are functional
#
# Copyright © 2008 Paul Slootman <paul@debian.org>
# distributed under the terms of the Artistic Licence 2.0
# As recommended by the manpage, run
# mdadm --monitor --scan --oneshot
# every day to ensure that any degraded MD devices don't go unnoticed.
# Email will go to the address specified in /etc/mdadm/mdadm.conf .
#
set -eu
MDADM=/sbin/mdadm
[ -x $MDADM ] || exit 0 # package may be removed but not purged
[ -e /etc/default/mdadm ] && . /etc/default/mdadm
[ $AUTOSCAN = false ] && exit 0
exec $MDADM --monitor --scan --oneshot

9
debian/mdadm.doc-base.faq vendored Normal file
View file

@ -0,0 +1,9 @@
Document: mdadm-faq
Title: mdadm Debian FAQ
Author: martin f. krafft
Abstract: The document answers frequently asked questions about Debian's mdadm
Section: System/Administration
Format: text
Index: /usr/share/doc/mdadm/FAQ.gz
Files: /usr/share/doc/mdadm/FAQ.gz

9
debian/mdadm.doc-base.recipes vendored Normal file
View file

@ -0,0 +1,9 @@
Document: mdadm-readme-recipes
Title: mdadm Debian recipes
Author: David Pashley
Abstract: The document contains some common recipes for mdadm usage on Debian
Section: System/Administration
Format: text
Index: /usr/share/doc/mdadm/README.recipes.gz
Files: /usr/share/doc/mdadm/README.recipes.gz

7
debian/mdadm.docs vendored Normal file
View file

@ -0,0 +1,7 @@
TODO
debian/README.recipes
debian/README.checkarray
debian/FAQ
ANNOUNCE-*
external-reshape-design.txt
mdmon-design.txt

2
debian/mdadm.examples vendored Normal file
View file

@ -0,0 +1,2 @@
mdadm.conf-example
misc/syslog-events

100
debian/mdadm.init vendored Normal file
View file

@ -0,0 +1,100 @@
#!/bin/sh
#
# Start the MD monitor daemon for all active MD arrays if desired.
# This script is not used under systemd.
#
# Copyright © 2001-2005 Mario Jou/3en <joussen@debian.org>
# Copyright © 2005-2009 Martin F. Krafft <madduck@debian.org>
# Distributable under the terms of the GNU GPL version 2.
#
### BEGIN INIT INFO
# Provides: mdadm
# Required-Start: $local_fs $syslog
# Required-Stop: $local_fs $syslog sendsigs
# 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
MDMON=/sbin/mdmon
RUNDIR=/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 [ -x /usr/bin/systemd-detect-virt ] && /usr/bin/systemd-detect-virt --quiet --container; then
log_daemon_msg "Not starting MD monitoring service in container"
log_end_msg 0
exit 0
fi
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
if [ "$(echo $RUNDIR/md[0-9]*.pid)" != "$RUNDIR/md[0-9]*.pid" ]; then
log_daemon_msg "Restarting MD external metadata monitor" "mdmon --takeover --all"
set +e
$MDMON --takeover --all
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
for file in $RUNDIR/md[0-9]*.pid ; do
[ ! -f "$file" ] && continue
ln -sf $file /run/sendsigs.omit.d/mdmon-${file##*/}
done
;;
status)
status_of_proc -p $PIDFILE "$MDADM" "mdadm" && exit 0 || exit $?
;;
restart|reload|force-reload)
${0:-} stop
${0:-} start
;;
*)
echo "Usage: ${0:-} {start|stop|status|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0

109
debian/mdadm.initramfs-hook vendored Normal file
View file

@ -0,0 +1,109 @@
#!/bin/sh
#
# Copyright © 2006-2008 Martin F. Krafft <madduck@debian.org>,
# 2012 Michael Tokarev <mjt@tls.msk.ru>
# based on the scripts in the initramfs-tools package.
# released under the terms of the Artistic Licence.
#
set -eu
PREREQ="udev"
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 "$@"
}
. /usr/share/initramfs-tools/hook-functions
# copy the binary as early as possible
copy_exec /sbin/mdadm /sbin
copy_exec /sbin/mdmon /sbin
# Copy udev rules, which udev no longer does
for UDEV_RULE in 63-md-raid-arrays.rules 64-md-raid-assembly.rules; do
for rules_folder in /lib/udev/rules.d /etc/udev/rules.d; do
if [ -f $rules_folder/$UDEV_RULE ]; then
mkdir -p $DESTDIR$rules_folder
cp $rules_folder/$UDEV_RULE $DESTDIR$rules_folder/$UDEV_RULE
fi
done
done
# load raid modules in the initramfs
for module in linear multipath raid0 raid1 raid456 raid5 raid6 raid10; do
force_load $module
done
# load efivars for Intel RST IMSM, see Bug#962844
force_load efivarfs || true
# copy the mdadm configuration
CONFIG=/etc/mdadm/mdadm.conf
ALTCONFIG=/etc/mdadm.conf
DESTMDADMCONF=$DESTDIR/etc/mdadm/mdadm.conf
[ ! -f $CONFIG ] && [ -f $ALTCONFIG ] && CONFIG=$ALTCONFIG || :
mkdir -p ${DESTDIR}/etc/mdadm
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
cp -p $CONFIG $DESTMDADMCONF
info "auto-generated the mdadm.conf configuration file."
else
# we failed to auto-generate, so let the emergency procedure take over
warn "failed to auto-generate the mdadm.conf file."
warn "please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz ."
fi
else
cp -p $CONFIG ${DESTDIR}/etc/mdadm
sed -i '/^CREATE/s/^/#/' $DESTMDADMCONF
if ! grep -q '^ARRAY' $CONFIG; then
tmpfile="${DESTMDADMCONF}.tmp"
if /usr/share/mdadm/mkconf > $tmpfile; then
cp -p $tmpfile $DESTMDADMCONF
rm -f $tmpfile
else
warn "failed to auto-generate temporary mdadm.conf file."
fi
else
# make sure the configuration file knows about all running devices
/sbin/mdadm --detail --scan | while read array device params; do
uuid=${params#*UUID=}; uuid=${uuid%% *}
if grep -qi "UUID=$uuid" $DESTMDADMCONF; then
info "$uuid $device added to the mdadm.conf in the initramfs"
fi
done
fi
fi

9
debian/mdadm.install vendored Normal file
View file

@ -0,0 +1,9 @@
sbin/
lib/
misc/mdcheck usr/share/mdadm/
debian/mkconf usr/share/mdadm/
debian/checkarray usr/share/mdadm/
debian/initramfs/* usr/share/initramfs-tools/
debian/bug-submission/script usr/share/bug/mdadm/

2
debian/mdadm.links vendored Normal file
View file

@ -0,0 +1,2 @@
/dev/null lib/systemd/system/mdadm-waitidle.service
/dev/null lib/systemd/system/mdadm.service

5
debian/mdadm.lintian-overrides vendored Normal file
View file

@ -0,0 +1,5 @@
# root device could be and array, so keep on in single-user mode
init.d-script-possible-missing-stop etc/init.d/mdadm-waitidle 1
# mdadm forks mdmon as required, not sure it should start separately
systemd-service-file-missing-install-key lib/systemd/system/mdmonitor.service

23
debian/mdadm.logcheck.ignore.server vendored Normal file
View file

@ -0,0 +1,23 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: md driver [.[:digit:]]+ MAX_MD_DEVS=[[:digit:]]+, MD_SB_DISKS=[[:digit:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: bitmap version [.[:digit:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: md[[:digit:]]+ stopped\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: md[[:digit:]]+ still in use\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: cannot remove active disk [[:alnum:]]+ from md[[:digit:]]+ \.\.\. ?$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: raid([01456]|456|10) personality registered for level ([01456]|10)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: (data-check|requested-resync|resync|reshape|recovery) of RAID array md[[:digit:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: resuming (data-check|requested-resync|resync|reshape|recovery) of md[[:digit:]]+ from checkpoint\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: md[[:digit:]]+: (data-check|requested-resync|resync|reshape|recovery) done\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: minimum _guaranteed_ ?speed: [[:digit:]]+ KB/sec/disk\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: using maximum available idle IO bandwidth \(but not more than [[:digit:]]+ KB/sec\) for (data-check|requested-resync|resync|reshape|recovery)\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: delaying (data-check|requested-resync|resync|reshape|recovery) of md[[:digit:]]+ until md[[:digit:]]+ has finished \(they share one or more physical units\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: using [[:digit:]]+k window, over a total of [[:digit:]]+( blocks|k)\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: (un)?bind<[^>]+>$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: export_rdev\([^)]+\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? raid[[:digit:]]+: raid set [[:alnum:]]+ active with [[:digit:]]+ out of [[:digit:]]+ mirrors$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? RAID([01456]|10) conf printout:$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+---( [wrf]d:[[:digit:]]+){2,3}$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+disk [[:digit:]]+,( wo:[[:digit:]]+,)? o:[[:digit:]]+, dev:[[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?: Rebuild((Start|Finish)ed|[[:digit:]]+) event detected on md device /dev/[-_./[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?: SpareActive event detected on md device /dev/[-_./[:alnum:]]+, component device /dev/[-_./[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?: (New|Degraded)Array event detected on md device /dev/[-_./[:alnum:]]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mdadm(\[[[:digit:]]+\])?: DeviceDisappeared event detected on md device /dev/[-_./[:alnum:]]+$

3
debian/mdadm.logcheck.violations vendored Normal file
View file

@ -0,0 +1,3 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? md: kicking non-fresh [[:alnum:]]+ from array!$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])? raid[[:digit:]]+: Disk failure on [[:alnum:]]+, disabling device\.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ kernel:( \[ *[[:digit:]]+\.[[:digit:]]+\])?[[:space:]]+Operation continuing on [[:digit:]]+ devices?$

1
debian/mdadm.manpages vendored Normal file
View file

@ -0,0 +1 @@
usr/share/man/*/*

22
debian/mdadm.mdadm-shutdown.service vendored Normal file
View file

@ -0,0 +1,22 @@
[Unit]
Description=Prepare mdadm shutdown initramfs
ConditionFileIsExecutable=/usr/bin/dracut
After=local-fs.target boot.mount boot.automount
Wants=local-fs.target
Before=shutdown.target
Conflicts=shutdown.target umount.target
DefaultDependencies=no
Documentation=man://dracut(8)
[Service]
RemainAfterExit=yes
Type=oneshot
ExecStart=/bin/true
ExecStop=/bin/mount -o remount,exec,suid /run
ExecStop=/bin/mkdir -p /run/initramfs
ExecStop=/usr/bin/dracut --no-compress --no-kernel --quiet --force --force-add "shutdown mdraid" --omit "caps" /run/initramfs/shutdown.cpio
ExecStop=/bin/sh -c 'cd /run/initramfs; cpio -id --quiet < shutdown.cpio'
ExecStop=/bin/rm /run/initramfs/shutdown.cpio
[Install]
WantedBy=sysinit.target

8
debian/mdadm.modprobe vendored Normal file
View file

@ -0,0 +1,8 @@
# mdadm module configuration file
# set start_ro=1 to make newly assembled arrays read-only initially,
# to prevent metadata writes. This is needed in order to allow
# resume-from-disk to work - new boot should not perform writes
# because it will be done behind the back of the system being
# resumed. See http://bugs.debian.org/415441 for details.
options md_mod start_ro=1

111
debian/mdadm.postinst vendored Normal file
View file

@ -0,0 +1,111 @@
#!/bin/sh
# Copyright © 2001-2005 Mario Jou/3en <joussen@debian.org>
# Copyright © 2005-2008 Martin F. Krafft <madduck@debian.org>
# Distributable under the terms of the GNU GPL version 2.
#
set -e
. /usr/share/debconf/confmodule
case "${1:-}" in
configure|reconfigure)
if [ ! -f /proc/mdstat ] && [ -x $(command -v modprobe 2>/dev/null) ]; then
modprobe md >/dev/null 2>&1 || :
fi
if [ ! -f /proc/mdstat ]; then
echo 'W: mdadm: failed to load MD subsystem.' >&2
fi
DEBIANCONFIG=/etc/default/mdadm
CONFIG=/etc/mdadm/mdadm.conf
ALTCONFIG=/etc/mdadm.conf
MDADM=/sbin/mdadm
# 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
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/autocheck
AUTOCHECK="${RET:-true}"
db_get mdadm/autoscan
AUTOSCAN="${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.
#
# AUTOCHECK:
# should mdadm run periodic redundancy checks over your arrays? See
# /etc/cron.d/mdadm.
AUTOCHECK=$AUTOCHECK
# AUTOSCAN:
# should mdadm check once a day for degraded arrays? See
# /etc/cron.daily/mdadm.
AUTOSCAN=$AUTOSCAN
# 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}
_eof
db_stop
# Remove old init script
update-rc.d mdadm-raid remove
command -v update-initramfs >/dev/null 2>&1 && update-initramfs -u
if command -v update-grub2 >/dev/null 2>&1; then
update-grub || true
fi
;;
esac
[ -d /run/systemd/system ] && systemctl --system daemon-reload >/dev/null || :
#DEBHELPER#

23
debian/mdadm.postrm vendored Normal file
View file

@ -0,0 +1,23 @@
#! /bin/sh
# Copyright © 2001,2002 Mario Jou/3en <joussen@debian.org>
# Copyright © 2006-2008 Martin F. Krafft <madduck@debian.org>
# Distributable under the terms of the GNU GPL version 2.
#
set -e
case "${1:-}" in
remove)
if command -v update-initramfs >/dev/null 2>&1; then
update-initramfs -u
fi
;;
purge)
rm -f /etc/default/mdadm /etc/mdadm.conf /etc/mdadm/mdadm.conf
;;
esac
[ -d /run/systemd/system ] && systemctl --system daemon-reload >/dev/null || :
#DEBHELPER#

45
debian/mdadm.templates vendored Normal file
View file

@ -0,0 +1,45 @@
# These templates have been reviewed by the debian-l10n-english
# team
#
# If modifications/additions/rewording are needed, please ask
# debian-l10n-english@lists.debian.org for advice.
#
# Even minor modifications require translation updates and such
# changes should be coordinated with translators and reviewers.
Template: mdadm/autocheck
Type: boolean
Default: true
_Description: Should mdadm run monthly redundancy checks of the MD arrays?
If the kernel supports it (versions greater than 2.6.14), mdadm can periodically check the
redundancy of MD arrays (RAIDs). This may be a resource-intensive process,
depending on the local 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 check on the first Sunday of every
month at 01:06.
Template: mdadm/autoscan
Type: boolean
Default: true
_Description: Should mdadm check once a day for degraded arrays?
mdadm can check once a day for degraded arrays and missing spares
to ensure that such events don't go unnoticed.
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).
.
Enabling this option is recommended.
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
notifications for important MD events.

104
debian/mkconf vendored Executable file
View file

@ -0,0 +1,104 @@
#!/bin/sh
#
# mkconf -- outputs valid mdadm.conf contents for the local system
#
# Copyright © martin f. krafft <madduck@madduck.net>
# distributed under the terms of the Artistic Licence 2.0
#
set -eu
ME="${0##*/}"
MDADM=/sbin/mdadm
DEBIANCONFIG=/etc/default/mdadm
CONFIG=/etc/mdadm/mdadm.conf
# initialise config variables in case the environment leaks
MAILADDR= DEVICE= HOMEHOST= PROGRAM=
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)"
HOMEHOST="$(sed -ne 's/^HOMEHOST //p' $CONFIG)"
PROGRAM="$(sed -ne 's/^PROGRAM //p' $CONFIG)"
fi
[ "${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
;;
esac
cat <<_eof
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE ${DEVICE:-partitions containers}
# automatically tag new arrays as belonging to the local system
HOMEHOST ${HOMEHOST:-<system>}
# 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 [ -z "${SOURCE_DATE_EPOCH:-}" ]; then
echo "# This configuration was auto-generated on $(date -R) by mkconf"
else
echo "# This configuration was auto-generated on $(date -R --utc -d@$SOURCE_DATE_EPOCH) by mkconf"
fi
exit $error

3
debian/not-installed vendored Normal file
View file

@ -0,0 +1,3 @@
lib/udev/rules.d/01-md-raid-creating.rules
lib/udev/rules.d/64-md-raid-assembly.rules
lib/udev/rules.d/69-md-clustered-confirm-device.rules

104
debian/patches/debian-conffile-location.diff vendored Normal file
View file

@ -0,0 +1,104 @@
From: martin f. krafft <madduck@debian.org>
Subject: Set /etc/mdadm/mdadm.conf as primary config file location
On Debian, the configuration file resides primarily in /etc/mdadm/mdadm.conf,
/etc/mdadm.conf is only used as a backup.
This is a Debian-specific patch.
Forwarded: not-needed
Reviewed-by: martin f. krafft <madduck@debian.org>
---
Makefile | 4 ++--
ReadMe.c | 2 +-
mdadm.8.in | 14 ++++++--------
mdadm.conf.5 | 2 +-
mdassemble.8 | 2 +-
5 files changed, 11 insertions(+), 13 deletions(-)
--- a/Makefile
+++ b/Makefile
@@ -74,8 +74,8 @@ CPPFLAGS += -DBINDIR=\"$(BINDIR)\"
PKG_CONFIG ?= pkg-config
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)\"
# Both MAP_DIR and MDMON_DIR should be somewhere that persists across the
--- a/ReadMe.c
+++ b/ReadMe.c
@@ -613,7 +613,7 @@ char Help_incr[] =
;
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(#), array lines, device lines, and various\n"
" configuration lines.\n"
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -267,13 +267,13 @@ the exact meaning of this option in diff
.TP
.BR \-c ", " \-\-config=
Specify the config file or directory. Default is to use
-.B /etc/mdadm.conf
+.B /etc/mdadm/mdadm.conf
and
-.BR /etc/mdadm.conf.d ,
+.BR /etc/mdadm/mdadm.conf.d ,
or if those are missing then
-.B /etc/mdadm/mdadm.conf
+.B /etc/mdadm.conf
and
-.BR /etc/mdadm/mdadm.conf.d .
+.BR /etc/mdadm.conf.d .
If the config file given is
.B "partitions"
then nothing will be read, but
@@ -2009,9 +2009,9 @@ The config file is only used if explicit
or requested with (a possibly implicit)
.BR \-\-scan .
In the later case,
-.B /etc/mdadm.conf
-or
.B /etc/mdadm/mdadm.conf
+or
+.B /etc/mdadm.conf
is used.
If
@@ -3340,7 +3340,7 @@ uses this to find arrays when
is given in Misc mode, and to monitor array reconstruction
on Monitor mode.
-.SS /etc/mdadm.conf
+.SS /etc/mdadm/mdadm.conf (or /etc/mdadm.conf)
The config file lists which devices may be scanned to see if
they contain MD super block, and gives identifying information
@@ -3348,7 +3348,7 @@ they contain MD super block, and gives i
.BR mdadm.conf (5)
for more details.
-.SS /etc/mdadm.conf.d
+.SS /etc/mdadm/mdadm.conf.d (or /etc/mdadm.conf.d)
A directory containing configuration files which are read in lexical
order.
--- a/mdadm.conf.5
+++ b/mdadm.conf.5
@@ -8,7 +8,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
.I mdadm

24
debian/patches/debian-no-Werror.diff vendored Normal file
View file

@ -0,0 +1,24 @@
From: martin f. krafft <madduck@debian.org>
Subject: Remove -Werror from compiler flags
-Werror seems like a bad idea on released/packaged code because a toolchain
update (introducing new warnings) could break the build. We'll let upstream
use it to beautify the code, but remove it for out builds.
Signed-off-by: martin f. krafft <madduck@debian.org>
---
Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--- a/Makefile
+++ b/Makefile
@@ -50,7 +50,7 @@ ifeq ($(origin CC),default)
CC := $(CROSS_COMPILE)gcc
endif
CXFLAGS ?= -ggdb
-CWFLAGS = -Wall -Werror -Wstrict-prototypes -Wextra -Wno-unused-parameter
+CWFLAGS = -Wall -Wstrict-prototypes -Wextra -Wno-unused-parameter
ifdef WARN_UNUSED
CWFLAGS += -Wp,-D_FORTIFY_SOURCE=2 -O3
endif

77
debian/patches/documentation-keys-in-service-files.patch vendored Normal file
View file

@ -0,0 +1,77 @@
Description: Make adjustments to systemd files provided by upstream
Author: Felix Lechner <felix.lechner@lease-up.com>
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/systemd/mdcheck_continue.service
+++ b/systemd/mdcheck_continue.service
@@ -7,7 +7,8 @@
[Unit]
Description=MD array scrubbing - continuation
-ConditionPathExistsGlob = /var/lib/mdcheck/MD_UUID_*
+ConditionPathExistsGlob=/var/lib/mdcheck/MD_UUID_*
+Documentation=man:mdadm(8)
[Service]
Type=oneshot
--- a/systemd/mdcheck_start.service
+++ b/systemd/mdcheck_start.service
@@ -8,6 +8,7 @@
[Unit]
Description=MD array scrubbing
Wants=mdcheck_continue.timer
+Documentation=man:mdadm(8)
[Service]
Type=oneshot
--- a/systemd/mdmonitor-oneshot.service
+++ b/systemd/mdmonitor-oneshot.service
@@ -7,6 +7,7 @@
[Unit]
Description=Reminder for degraded MD arrays
+Documentation=man:mdadm(8)
[Service]
Environment=MDADM_MONITOR_ARGS=--scan
--- a/systemd/mdadm-grow-continue@.service
+++ b/systemd/mdadm-grow-continue@.service
@@ -8,6 +8,7 @@
[Unit]
Description=Manage MD Reshape on /dev/%I
DefaultDependencies=no
+Documentation=man:mdadm(8)
[Service]
ExecStart=BINDIR/mdadm --grow --continue /dev/%I
--- a/systemd/mdadm-last-resort@.service
+++ b/systemd/mdadm-last-resort@.service
@@ -2,6 +2,7 @@
Description=Activate md array %I even though degraded
DefaultDependencies=no
ConditionPathExists=!/sys/devices/virtual/block/%i/md/sync_action
+Documentation=man:mdadm(8)
[Service]
Type=oneshot
--- a/systemd/mdmon@.service
+++ b/systemd/mdmon@.service
@@ -9,6 +9,7 @@
Description=MD Metadata Monitor on /dev/%I
DefaultDependencies=no
Before=initrd-switch-root.target
+Documentation=man:mdmon(8)
[Service]
# mdmon should never complain due to lack of a platform,
--- a/systemd/mdmonitor.service
+++ b/systemd/mdmonitor.service
@@ -8,6 +8,7 @@
[Unit]
Description=MD array monitor
DefaultDependencies=no
+Documentation=man:mdadm(8)
[Service]
Environment= MDADM_MONITOR_ARGS=--scan

25
debian/patches/exit-gracefully-when-md-device-not-found.patch vendored Normal file
View file

@ -0,0 +1,25 @@
Description: Exit gracefully when md device not found
Author: Felix Lechner <felix.lechner@lease-up.com>
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970329
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Monitor.c
+++ b/Monitor.c
@@ -539,8 +539,14 @@ static int check_array(struct state *st,
if (fd < 0)
goto disappeared;
- if (st->devnm[0] == 0)
- strcpy(st->devnm, fd2devnm(fd));
+ if (st->devnm[0] == 0) {
+ char *found = fd2devnm(fd);
+ if (!found) {
+ alert("DeviceDisappeared", dev, NULL, ainfo);
+ goto out;
+ }
+ strcpy(st->devnm, found);
+ }
for (mse2 = mdstat; mse2; mse2 = mse2->next)
if (strcmp(mse2->devnm, st->devnm) == 0) {

18
debian/patches/fix-command-line-help.patch vendored Normal file
View file

@ -0,0 +1,18 @@
Description: Make command-line help consistent with manual page.
Mode was missing.
Author: Felix Lechner <felix.lechner@lease-up.com>
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932791
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/ReadMe.c
+++ b/ReadMe.c
@@ -477,7 +477,7 @@ char Help_assemble[] =
;
char Help_manage[] =
-"Usage: mdadm arraydevice options component devices...\n"
+"Usage: mdadm [mode] arraydevice [options] <component devices...>\n"
"\n"
"This usage is for managing the component devices within an array.\n"
"The --manage option is not needed and is assumed if the first argument\n"

200
debian/patches/fix-manpages.patch vendored Normal file
View file

@ -0,0 +1,200 @@
Description: Fix typos and macro issues in manpages
Author: Felix Lechner <felix.lechner@lease-up.com>
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915182
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916946
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962946
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933773
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/md.4
+++ b/md.4
@@ -363,9 +363,9 @@ tab(;);
;Device #1;Device #2;Device #3;Device #4
0x00;0;0;1;1
0x01;2;2;3;3
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
0x80;254;254;255;255
;\\---------v---------/;\\---------v---------/
;RAID1;RAID1
@@ -392,9 +392,9 @@ C.
;Dev #1;Dev #2;Dev #3;Dev #4;Dev #5
0x00;0;0;1;1;2
0x01;2;3;3;4;4
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
:;:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.
0x80;317;318;318;319;319
;
.TE
@@ -454,15 +454,15 @@ C.
;
0x00;0;1;2;3;\\
0x01;4;5;6;7;> [#]
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
:;:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
0x40;252;253;254;255;/
0x41;3;0;1;2;\\
0x42;7;4;5;6;> [#]~
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
:;:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
0x80;255;252;253;254;/
;
.TE
@@ -493,15 +493,15 @@ C.
;
0x00;0;1;2;3;4;\\
0x01;5;6;7;8;9;> [#]
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
:;:;:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
0x40;315;316;317;318;319;/
0x41;4;0;1;2;3;\\
0x42;9;5;6;7;8;> [#]~
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
:;:;:;:;:;:;:
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;:
0x80;319;315;316;317;318;/
;
.TE
@@ -572,9 +572,9 @@ C.
0x01;3;0;1;2;) AA~
0x02;4;5;6;7;) AB
0x03;7;4;5;6;) AB~
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
:;:;:;:;:; :
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
0x79;251;252;253;254;) EX
0x80;254;251;252;253;) EX~
;
@@ -605,9 +605,9 @@ C.
0x01;4;0;1;2;3;) AA~
0x02;5;6;7;8;9;) AB
0x03;9;5;6;7;8;) AB~
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
:;:;:;:;:;:; :
-\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
+;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;\.\.\.;) \.\.\.
0x79;314;315;316;317;318;) EX
0x80;318;314;315;316;317;) EX~
;
@@ -987,7 +987,7 @@ other device(s).
.I md
cannot control the timeout that the underlying devices use to
determine failure. Any changes desired to that timeout must be set
-explictly on the underlying device, separately from using
+explicitly on the underlying device, separately from using
.IR mdadm .
If a FAILFAST request does fail, and if it is still safe to mark the
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -461,11 +461,10 @@ number of spare devices.
.BR \-z ", " \-\-size=
Amount (in Kilobytes) of space to use from each drive in RAID levels 1/4/5/6.
This must be a multiple of the chunk size, and must leave about 128Kb
-of space at the end of the drive for the RAID superblock.
-If this is not specified
-(as it normally is not) the smallest drive (or partition) sets the
-size, though if there is a variance among the drives of greater than 1%, a warning is
-issued.
+of space at the end of the drive for the RAID superblock. When specified as
+\(acmax\(ac (as it often is) the smallest drive (or partition) sets the size.
+In that case, a warning will follow if the drives, as a group, have sizes that
+differ by more than one percent.
A suffix of 'K', 'M', 'G' or 'T' can be given to indicate Kilobytes,
Megabytes, Gigabytes or Terabytes respectively.
@@ -682,7 +681,7 @@ A bug introduced in Linux 3.14 means tha
started using a different layout. This could lead to
data corruption. Since Linux 5.4 (and various stable releases that received
backports), the kernel will not accept such an array unless
-a layout is explictly set. It can be set to
+a layout is explicitly set. It can be set to
.RB ' original '
or
.RB ' alternate '.
@@ -924,6 +923,7 @@ the
.B name
will default to
.IR home .
+(Does not work in Grow mode.)
.TP
.BR \-R ", " \-\-run
@@ -1133,7 +1133,7 @@ out-of-date. If
cannot find enough working devices to start the array, but can find
some devices that are recorded as having failed, then it will mark
those devices as working so that the array can be started. This works only for
-native. For external metadata it allows to start dirty degraded RAID 4, 5, 6.
+native. For external metadata it allows one to start dirty degraded RAID 4, 5, 6.
An array which requires
.B \-\-force
to be started may contain data corruption. Use it carefully.
@@ -1446,7 +1446,7 @@ array, and the slot that it used is stil
be added back to the array in the same position. This will normally
cause the data for that device to be recovered. However based on the
event count on the device, the recovery may only require sections that
-are flagged a write-intent bitmap to be recovered or may not require
+are flagged by a write-intent bitmap to be recovered or may not require
any recovery at all.
When used on an array that has no metadata (i.e. it was built with
@@ -1821,7 +1821,7 @@ Details of
.B check
and
.B repair
-can be found it
+can be found in
.IR md (4)
under
.BR "SCRUBBING AND MISMATCHES" .
@@ -2901,7 +2901,7 @@ long time. A
is required. If the array is not simultaneously being grown or
shrunk, so that the array size will remain the same - for example,
reshaping a 3-drive RAID5 into a 4-drive RAID6 - the backup file will
-be used not just for a "cricital section" but throughout the reshape
+be used not just for a "critical section" but throughout the reshape
operation, as described below under LAYOUT CHANGES.
.SS CHUNK-SIZE AND LAYOUT CHANGES
@@ -2939,7 +2939,8 @@ option in Grow mode. Currently this work
.B ppl
and
.B resync
-policies and allows to enable or disable the RAID5 Partial Parity Log (PPL).
+policies and allows one to enable or disable the RAID5 Partial Parity
+Log (PPL).
.SH INCREMENTAL MODE
--- a/mdmon.8
+++ b/mdmon.8
@@ -115,7 +115,7 @@ container. Some array management comman
add are now only valid at the container level. Attempts to perform
these actions on member arrays are blocked with error messages like:
.IP
-"mdadm: Cannot remove disks from a \'member\' array, perform this
+"mdadm: Cannot remove disks from a \(aqmember\(aq array, perform this
operation on the parent container"
.P
Containers are identified in /proc/mdstat with a metadata version string

21
debian/patches/host-name-in-default-mailfrom.patch vendored Normal file
View file

@ -0,0 +1,21 @@
Description: Add host name to default MAILFROM
The host on which the error occurred is mentioned in the subject and also in
the message body, but some may find it useful in the From address, as well.
Author: Felix Lechner <felix.lechner@lease-up.com>
Bug-Debian: https://bugs.debian.org/1006464
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Monitor.c
+++ b/Monitor.c
@@ -440,8 +440,8 @@ static void alert(char *event, char *dev
if (info->mailfrom)
fprintf(mp, "From: %s\n", info->mailfrom);
else
- fprintf(mp, "From: %s monitoring <root>\n",
- Name);
+ fprintf(mp, "From: %s monitoring <root@%s>\n",
+ Name, hname);
fprintf(mp, "To: %s\n", info->mailaddr);
fprintf(mp, "Subject: %s event on %s:%s\n\n",
event, dev, hname);

20
debian/patches/mdmonitor-service-simplify.diff vendored Normal file
View file

@ -0,0 +1,20 @@
Subject: simplify mdmonitor.service
From: Michael Tokarev <mjt@tls.msk.ru>
Date: Fri, 14 Nov 2014 19:18:05 +0300
Bug-Debian: http://bugs.debian.org/764647
Forwarded: no
There isn't much for customization for mdadm --monitor.
it'll just do what it's supposed to do, so just run it.
--- a/systemd/mdmonitor.service
+++ b/systemd/mdmonitor.service
@@ -11,7 +11,4 @@ DefaultDependencies=no
Documentation=man:mdadm(8)
[Service]
-Environment= MDADM_MONITOR_ARGS=--scan
-EnvironmentFile=-/run/sysconfig/mdadm
-ExecStartPre=-/usr/lib/mdadm/mdadm_env.sh
-ExecStart=BINDIR/mdadm --monitor $MDADM_MONITOR_ARGS
+ExecStart=BINDIR/mdadm --monitor --scan

21
debian/patches/readlink-path.patch vendored Normal file
View file

@ -0,0 +1,21 @@
From: Michael Tokarev <mjt@tls.msk.ru>
Subject: readlink is in /bin not /usr/bin on debian
Date: Fri, 14 Nov 2014 19:11:51 +0300
Bug-Debian: http://bugs.debian.org/766416
Forwarded: no
This is a debian-specific change, upstream ships
the rule to use /usr/bin/readlink while on debian
it is /bin/readlink
--- a/udev-md-raid-arrays.rules
+++ b/udev-md-raid-arrays.rules
@@ -37,7 +37,7 @@ ENV{ID_FS_USAGE}=="filesystem|other", EN
ENV{MD_LEVEL}=="raid[1-9]*", ENV{SYSTEMD_WANTS}+="mdmonitor.service"
# Tell systemd to run mdmon for our container, if we need it.
-ENV{MD_LEVEL}=="raid[1-9]*", ENV{MD_CONTAINER}=="?*", PROGRAM="/usr/bin/readlink $env{MD_CONTAINER}", ENV{MD_MON_THIS}="%c"
+ENV{MD_LEVEL}=="raid[1-9]*", ENV{MD_CONTAINER}=="?*", PROGRAM="/bin/readlink $env{MD_CONTAINER}", ENV{MD_MON_THIS}="%c"
ENV{MD_MON_THIS}=="?*", PROGRAM="/usr/bin/basename $env{MD_MON_THIS}", ENV{SYSTEMD_WANTS}+="mdmon@%c.service"
ENV{RESHAPE_ACTIVE}=="yes", PROGRAM="/usr/bin/basename $env{MD_MON_THIS}", ENV{SYSTEMD_WANTS}+="mdadm-grow-continue@%c.service"

12
debian/patches/series vendored Normal file
View file

@ -0,0 +1,12 @@
fix-manpages.patch
fix-command-line-help.patch
documentation-keys-in-service-files.patch
mdmonitor-service-simplify.diff
host-name-in-default-mailfrom.patch
exit-gracefully-when-md-device-not-found.patch
strcat-look-for-md-device-in-dev-md.patch
sha1-includes.diff
readlink-path.patch
debian-no-Werror.diff
debian-conffile-location.diff
test-installed.patch

40
debian/patches/sha1-includes.diff vendored Normal file
View file

@ -0,0 +1,40 @@
From: Michael Tokarev <mjt@tls.msk.ru>
Subject: do not #include ansidecl.h from sha1.h, use system headers
In 3.2.5 version of mdadm, new sha1 implementation has been included
which tries to include ansidecl.h header which is internal to some
other project. But this #include isn't really necessary, since this
implementation does not actually use any defines from ansidecl.h. So
just remove the #include, instead of adding a new external dependency.
References: http://www.spinics.net/lists/raid/msg38859.html
While at it, unconditionally include system headers like limits.h and
stdint.h, since on a Linux system these headers are available, and
these contains definitive information about real system types than
any guesses.
--- a/sha1.h
+++ b/sha1.h
@@ -22,7 +22,7 @@
#include <stdio.h>
-#if defined HAVE_LIMITS_H || _LIBC
+#if 1 /* defined HAVE_LIMITS_H || _LIBC */
# include <limits.h>
#endif
@@ -33,9 +33,9 @@
the resulting executable. Locally running cross-compiled executables
is usually not possible. */
-#ifdef _LIBC
-# include <sys/types.h>
-typedef u_int32_t sha1_uint32;
+#if 1 /* def _LIBC */
+# include <stdint.h>
+typedef uint32_t sha1_uint32;
typedef uintptr_t sha1_uintptr;
#else
# define INT_MAX_32_BITS 2147483647

17
debian/patches/strcat-look-for-md-device-in-dev-md.patch vendored Normal file
View file

@ -0,0 +1,17 @@
Description: Look for md device in /dev/md
Author: Martin Mares <mj@ucw.cz>
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958060
Forwarded: no
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/Monitor.c
+++ b/Monitor.c
@@ -188,7 +188,7 @@ int Monitor(struct mddev_dev *devlist,
st->devname = xstrdup(mdlist->devname);
else {
st->devname = xmalloc(8+strlen(mdlist->devname)+1);
- strcpy(strcpy(st->devname, "/dev/md/"),
+ strcat(strcpy(st->devname, "/dev/md/"),
mdlist->devname);
}
st->next = statelist;

32
debian/patches/test-installed.patch vendored Normal file
View file

@ -0,0 +1,32 @@
Description: Test installed files
The test suite seems to check the executable bit on the local build product
'mdadm' but runs all programs from the system PATH. This change should test
the installed version.
.
I believe this change tests the installed version, but that hypothesis is not
supported by much else. The autopkgtest restriction isolation-machine made it
difficult so far to run the test suite anywhere.
.
The entire setup is untested and may require further modification in order to
function.
.
Incorporates a suggestion from the fdisk maintainer to specify the fdisk
prerequisite explicitly.
Author: Felix Lechner <felix.lechner@lease-up.com>
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872118
Forwarded: not-needed
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/tests/func.sh
+++ b/tests/func.sh
@@ -101,10 +101,6 @@ check_env() {
echo "test: testing can only be done as 'root'."
exit 1
}
- [ \! -x $mdadm ] && {
- echo "test: please run make everything before perform testing."
- exit 1
- }
cmds=(mdadm lsblk df udevadm losetup mkfs.ext3 fsck seq)
for cmd in ${cmds[@]}
do

1
debian/po/POTFILES.in vendored Normal file
View file

@ -0,0 +1 @@
[type: gettext/rfc822deb] mdadm.templates

198
debian/po/ca.po vendored Normal file
View file

@ -0,0 +1,198 @@
# mdadm Catalan translation.
# Copyright (C) 2004-2006 Software in the Public Interest
# This file is distributed under the same license as the squid package.
# Innocent De Marchi <tangram.peces@gmail.com>, 2011.
#
msgid ""
msgstr ""
"Project-Id-Version: 3.1.4-1+8efb9d1\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2011-05-17 16:54+0100\n"
"Last-Translator: Innocent De Marchi <tangram.peces@gmail.com>\n"
"Language-Team: Catalan <debian-l10n-catalan@lists.debian.org>\n"
"Language: ca\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: Catalan\n"
"X-Poedit-Country: SPAIN\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
"Voleu que «mdadm» executi comprovacions de redundància mensuals de les "
"matrius MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 el nucli ho accepta (versions superiors a la 2.6.14), «mdadm» pot fer "
"comprovacions periòdiques de la redundància de les matrius MD (RAIDs). Pot "
"ésser que aquest procés consumeixi molts recursos del sistema, depenent de "
"la configuració, però pot ajudar a prevenir casos poc freqüents de pèrdua de "
"dades. Teniu present que aquestes comprovacions es fan en mode lectura "
"llevat que es detectin errors: si hi ha errors, «mdadm» els corregirà i per "
"això, caldrà que tengui accés d'escriptura als mitjans físics. "
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"El valor predeterminat, si s'activa, es fer la comprovació el primer "
"diumenge de cada mes a les 01:06 am."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Desitjau arrencar el dimoni monitor MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"El dimoni monitor de MD (RAID) envia notificacions per correu electrònic "
"quan es produeixen esdeveniments importants en els dispositius MD (com un "
"error de disc)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Es recomana l'activació d'aquesta opció."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatari de les notificacions de correu electrònic:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Introduïu l'adreça de correu electrònic de l'usuari que ha de rebre les "
"notificacions de correu electrònic per a esdeveniments MD rellevants."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Les matrius MD necessaris per al sistema de fitxers arrel:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Escriviu «all» (tots), «none» (cap) o una llista separada per espais dels "
#~ "dispositius com «md0 md1» o «md/1 md/d0» (podeu ometre el «/dev/» "
#~ "inicial)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "per a ús intern, només és necessària la descripció llarga. "
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Si el sistema de fitxers arrel del sistema està en un conjunt MD (RAID), "
#~ "cal que s'iniciï al principi de la seqüència d'arrencada. Si està en un "
#~ "volum lògic (LVM), que està definit sobre un MD, cal iniciar totes les "
#~ "matrius que el constitueixen."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 sabeu exactament quines matrius són necessàries per arrencar el "
#~ "sistema de fitxers arrel, i vol ajornar l'arrencada de la resta de "
#~ "conjunts a un punt posterior de la seqüència d'arrencada, Introduïu aquí "
#~ "els conjunts que voleu arrencar. També podeu seleccionar «all» per, "
#~ "simplement, arrencar tots els disponibles."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 no necessita o vol arrencar qualsevol matriu per al sistema de fitxers "
#~ "arrel, deixau en blanc la resposta (o escriviu «none»). Pot ésser el seu "
#~ "cas si fa servir l'auto-arrencada del nucli o no necessiteu cap matriu en "
#~ "l'arrencada."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "S'ha produït un error: el node de dispositiu no existeix."
#~ msgid "An error occurred: not a block device"
#~ msgstr "S'ha produït un error: no és un dispositiu de blocs."
#~ msgid "An error occurred: not an MD array"
#~ msgstr "S'ha produït un error: no és un conjunt («array») MD."
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr ""
#~ "S'ha produït un error: la matriu («array») no apareix llistada en el "
#~ "fitxer de configuració «mdadm.conf»."
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Voleu arrencar les matrius no llistats en el fitxer «mdadm.conf»?"
#~ msgid ""
#~ "The specified array (${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 ""
#~ "La matriu («array») especificada (${array}) no apareix llistada en el "
#~ "fitxer de configuració (${config}). Per tant, no es pot iniciar la matriu "
#~ "durant l'arrencada del sistema, llevat que corregeixi el fitxer de "
#~ "configuració i regenereu el disc RAM inicial."
#~ 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 ""
#~ "Aquest avís només és important si necessiteu que les matrius s'arrenquin "
#~ "en el disc RAM inicial per poder arrencar el sistema. Si feu servir "
#~ "l'arrencada automàtica del nucli o no necessiteu que les matrius "
#~ "estiguin arrencats quan es carregui el disc RAM, podeu continuar. També "
#~ "podeu decidir no continuar i introduir «none» quan se li demani quines "
#~ "matrius cal iniciar del disc RAM inicial."

244
debian/po/cs.po vendored Normal file
View file

@ -0,0 +1,244 @@
#
# 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: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-10-18 16:52+0200\n"
"Last-Translator: Miroslav Kure <kurem@debian.cz>\n"
"Language-Team: Czech <debian-l10n-czech@lists.debian.org>\n"
"Language: cs\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 (verze větší než 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Pokud kontrolu povolíte, bude 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:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Má mdadm jednou denně zjišťovat degradovaná pole?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm může jednou denně zjišťovat degradovaná pole a chybějící "
"náhradní disky, aby zaručil, že tyto události neprojdou bez povšimnutí."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Chcete spustit daemon pro monitorování MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Daemon pro monitorování MD (RAIDu) zasílá emailová upozornění na významné MD "
"události, jako je selhání disku."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Povolení této možnosti je doporučeno."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Příjemce emailových upozornění:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications 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 "MD arrays needed for the root file system:"
#~ msgstr "MD pole vyžadovaná pro kořenový souborový systém:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Zadejte prosím mezerami oddělený seznam zařízení, případně „all“ nebo "
#~ "„none“. Počáteční „/dev/“ můžete vynechat a zadat jen např. „md0 md1“ "
#~ "nebo „md/1 md/d0“."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "pro vnitřní použití - pouze kvůli zobrazení dlouhého popisu."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Pokud je 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 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."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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“."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Vyskytla se chyba: uzel zařízení neexistuje"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Vyskytla se chyba: není blokovým zařízením"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Vyskytla se chyba: není MD polem"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Vyskytla se chyba: pole není uvedeno v souboru mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Spustit pole neuvedená v mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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'."
#~ 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."

189
debian/po/da.po vendored Normal file
View file

@ -0,0 +1,189 @@
# Danish translation mdadm.
# Copyright (C) 2011 mdadm & nedenstående oversættere.
# This file is distributed under the same license as the mdadm package.
# Joe Hansen <joedalton2@yahoo.dk>, 2011.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2011-04-03 17:30+01:00\n"
"Last-Translator: Joe Hansen <joedalton2@yahoo.dk>\n"
"Language-Team: Danish <debian-l10n-danish@lists.debian.org> \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Skal mdadm køre månedlig redundanskontrol af MD arrays?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 ""
"Hvis kernen understøtter det (versioner større end 2.6.14), kan mdadm "
"periodisk kontrollere redundansen på MD arrays (RAID'er). Det kan være en "
"ressourcekrævende proces, afhængig af den lokale opsætning, men det kan "
"hjælpe med at forhindre at du i sjældne tilfælde får datatab. Bemærk at "
"dette er en skrivebeskyttet kontrol med mindre at der findes fejl; hvis der "
"registreres fejl vil mdadm forsøge at rette dem, hvilket kan medføre "
"skriveadgang til mediet."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Standarden - hvis aktiveret - er at kontrollere på den første søndag i hver "
"måned klokken 01:06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Ønsker du at starte MD-overvågningsdæmonen?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD-overvågningsdæmonem (RAID) sender e-post-påmindelser udløst af vigtige MD-"
"hændelser (såsom en diskfejl)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Aktivering af denne indstilling anbefales."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Modtager af e-post-påmindelser:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Indtast venligst e-post-adressen på brugeren, som skal modtage e-post-"
"påmindelser for vigtige MD-hændelser."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "MD arrays krævet for rodfilsystemet:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Indtast venligst »all«, »none« eller en mellemrumsadskilt liste af "
#~ "enheder såsom »md0 md1« eller »md/1 md/d0« (det foranstillede »/dev/« kan "
#~ "udelades)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "for intern brug - kun den lange beskrivelse er krævet."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Hvis systemets rodfilsystem er placeret på en MD-array (RAID), skal det "
#~ "startes tidligt under opstartssekvensen. Hvis den er placeret på en "
#~ "logisk diskenhed (LVM), som er på MD, skal alle indgående arrays startes."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 ""
#~ "Hvis du ved præcis hvilke arrays som er krævet, for at få rodfilsystemet "
#~ "op, og du ønsker at udsætte start af alle andre arrays til et senere "
#~ "tidspunkt i opstartssekvensen, så indtast her de arrays som skal startes. "
#~ "Alternativt kan du indtaste »all« for at starte alle tilgængelige arrays."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 ""
#~ "Hvis du ikke har brug for eller ønsker at starte nogen arrays for "
#~ "rodfilsystemet, så efterlad svaret tomt (eller indtast »none«). Dette kan "
#~ "være tilfældet, hvis du bruger automatisk start af kernen eller ikke skal "
#~ "bruge arrays til at starte op med."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Der opstod en fejl: Enhedsknude findes ikke"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Der opstod en fejl: Ikke en blokenhed"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Der opstod en fejl: Ikke en MD array"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Der opstod en fejl: Array er ikke anført i mdadm.conf-filen"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Start arrays er ikke anført i mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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 ""
#~ "Den angivne array (${array}) er ikke anført i konfigurationsfilen "
#~ "(${config}). Den kan derfor ikke startes under opstarten, med mindre du "
#~ "retter i konfigurationsfilen og gendanner den oprindleige ramdisk."
#~ 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 ""
#~ "Denne advarsel er kun relevant hvis du skal have arrays til at blive "
#~ "startet fra den oprindelige ramdisk for at kunne starte op. Hvis du "
#~ "bruger den automatiske opstart i kernen, eller ikke skal bruge at arrays "
#~ "startes så tidligt som den oprindelige ramdisk indlæses, så kan du bare "
#~ "fortsætte. Alternativt så vælg at fortsætte og indtaste »none« når du "
#~ "bliver spurgt om hvilke arrays, der skal startes fra den oprindelige "
#~ "ramdisk."

268
debian/po/de.po vendored Normal file
View file

@ -0,0 +1,268 @@
# 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.
#
# (C) Mario Joussen <joussen@debian.org>, 2009.
# (C) Helge Kreutzmann <debian@helgefjell.de>, 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 4.1.5\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-04-10 09:40+0200\n"
"Last-Translator: Mario Joussen <joussen@debian.org>\n"
"Language-Team: German <debian-l10n-german@lists.debian.org>\n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 (Versionen größer als 2.6.14) kann Mdadm "
"regelmäßig die Redundanz Ihrer MD-Verbünde (RAID) überprüfen. Dies kann "
"abhängig von Ihrer Installation ein ressourcenintensiver Vorgang sein, der "
"aber helfen kann, seltene Fälle von Datenverlust zu vermeiden. Bitte "
"beachten Sie, dass 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
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:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Soll Mdadm einmal täglich auf degradierte Verbünde prüfen?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"Mdadm kann einmal täglich auf degradierte Verbünde und fehlende "
"Ausweichmedien prüfen, um sicherzustellen, dass diese Ereignisse bemerkt "
"werden."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Möchten Sie den RAID-Überwachungsdämon starten?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Der MD- (RAID-)Überwachungsdämon verschickt Benachrichtigungen als Reaktion "
"auf wichtige RAID-Ereignisse (wie zum Beispiel Festplattenfehler)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Das Aktivieren dieser Option ist empfohlen."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Empfänger der E-Mail-Benachrichtungen:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Geben Sie bitte die E-Mail-Adresse des Benutzers an, der die E-Mail-"
"Benachrichtigung für wichtigen MD-Ereignisse erhalten soll."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Für das Wurzeldateisystem benötigte MD folgende Verbünde:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Bitte geben Sie »all«, »none« oder eine leerzeichenseparierte Geräteliste "
#~ "wie zum Beispiel »md0 md1« oder »md/1 md/d0« ein (das führende »/dev« "
#~ "kann weggelassen werden)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr ""
#~ "für internen Gebrauch - es wird nur die ausführliche Beschreibung "
#~ "benötigt."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Wenn das Wurzeldateisystem Ihres Systems auf einem MD-Verbund (RAID) "
#~ "liegt, muss es frühzeitig während des Bootvorgangs gestartet werden. Wenn "
#~ "sich Ihr Wurzeldateisystem auf einem logischen Laufwerk (LVM) befindet, "
#~ "das sich wiederum auf einem MD Verbund befindet, müssen alle zugehörigen "
#~ "Verbünde gestartet werden."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 Verbünde zum Booten benötigen."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Ein Fehler ist aufgetreten: Geräteknoten existiert nicht"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Ein Fehler ist aufgetreten: kein Blockgerät"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Ein Fehler ist aufgetreten: kein RAID-Verbund"
#~ 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"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Nicht in mdadm.conf aufgeführte Verbünde starten?"
#~ msgid ""
#~ "The specified array (${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 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."
#~ 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 "
#~ "muss, können Sie einfach fortfahren. Alternativ wählen Sie, nicht "
#~ "fortzufahren und geben »none« ein, wenn Sie gefragt werden, welche RAID-"
#~ "Verbünde von der initialen Ramdisk gestartet werden sollen."
#~ 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-Überwachungsdaemon gestartet, so werden E-Mail-"
#~ "Benachrichtigungen verschickt, falls ein zum RAID gehörendes Laufwerk "
#~ "ausfällt oder den Status ändert."

235
debian/po/es.po vendored Normal file
View file

@ -0,0 +1,235 @@
# 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
# - Updates:
# Jonatan Porras <jonatanpc8@gmail.com>, 2020
#
# 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 (<debian-l10n-spanish@lists.debian.org>)
#
# 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: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2008-04-25 17:47+0200\n"
"Last-Translator: Javier Fernández-Sanguino <jfs@debian.org>\n"
"Language-Team: Debian Spanish <debian-l10n-spanish@lists.debian.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-15\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 el 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"El valor por omisio, si se activa, es comprobar el primer Domingo de cada "
"mes a las 01:06 am."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "¿Debería mdadm comprobar una vez al día si hay arrays degradadas?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm puede comprobar una vez al día si hay arrays degradadas y repuestos que "
"faltan para garantizar que tales eventos no pasen desapercibidos."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "¿Desea arrancar el demonio de monitorización MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
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)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Es opcional habilitar esta opción."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatario de las notificaciones por correo:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications 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."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Arrays MD necesarios para el sistema de ficheros raíz:"
# No se traduce «all» y «none» porque no aparecen en la plantilla para traducir los elementos individuales
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Introduzca «all» (todos), «none» (ninguno) o una lista de dispositivos "
#~ "separados por espacios como por ejemplo puede sólo introducir «md0 md1» o "
#~ "«md/1 md/d0» (no tiene que preceder los nombres de dispositivos con «/"
#~ "dev»)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "para uso interno. Sólo se utiliza la descripción larga."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Si el sistema de ficheros raíz de su sistema está en un array MD (RAID) "
#~ "tiene que inicializarse antes durante de la secuencia de arranque. Si "
#~ "está en un volumen lógico (LVM), que está definido sobre un MD, todos los "
#~ "arrays que lo forman tienen que haberse inicializado."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Se produjo un error: el nodo de dispositivo no existe"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Se produjo un error: no es un dispositivo de bloques"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Se produjo un error: no es un array MD"
#~ 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"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "¿Desea arrancar los arrays no listados en mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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."

193
debian/po/eu.po vendored Normal file
View file

@ -0,0 +1,193 @@
# mdadm debconf templates basque translation
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Inaki Larranaga Murgoitio <dooteo@zundan.com>, 2020.
# Piarres Beobide <pi@beobide.net>, 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm-debconf\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-09-21 17:06+0100\n"
"Last-Translator: Inaki Larranaga Murgoitio <dooteo@zundan.com>, 2020\n"
"Language-Team: Euskara <debian-l10n-basque@lists.debian.org>\n"
"Language: eu\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
"mdadm-ek hilabetero MD matrizen erredundantzia egiaztatu behar du?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 ""
"Kernelak onartzen badu (2.6.14 baino bertsio berriagoak), mdadm-ek MD "
"matrizen (RAID-en) erredundantzia aldiro egiazta dezake. Konfigurazio "
"lokalaren arabera baliabide-eskakizun handiko prozesu bat izan daitekeen "
"arren datu galera kasuak saihesten lagundu dezake. Kontutan izan "
"irakur-soileko egiaztapena dela errorerik aurkitu ezean; bestela, erroreeak "
"aurkituz gero, mdadm-ek hauek konpontzen saiatuko da, horretarako euskarria "
"idazketa moduan atzitu behar izan dezakeelarik."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Gaituta egonez gero, lehenetsi gisa hilabete bakoitzeko aurreneko "
"asteleheneko 01:06-etan egiaztatuko da."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "mdadm-ek degradatutako matrizeak egunean behin egiaztatuko ditu?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm-ek egunean behin degradatutako matrizeak eta falta diren ordezkoak "
"egiazta ditzake halako gertaerak oharkabe ez geratzeko."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "MD monitorizazio-daemona abiarazi nahi duzu?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD (RAID) monitorizazio-daemonak mezu elektronikoak bidaltzen ditu "
"MD gertaera (adib. diskoen erroreak) garrantzitsuetaz berri emanez."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Aukera hau gaitzea gomendatzen da."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Jakinarazpenen hartzailearen helb. eletronikoa:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Idatzi MD gertaera garrantzitsuen jakinarazpenak jasoko dituen "
"erabiltzailearen helbide elektronikoa."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Erro fitxategi-sistemarentzat beharrezko MD array-ak:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Mesedez idatzi 'denak', 'batez', edo zuriunez bereziriko gailuen "
#~ "zerrenda, adibidez 'md0 md1' edo 'md/1 md/d0' (hasierako '/dev/' baztertu "
#~ "daiteke)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "barne erabilerako - deskribapen luzea bakarrik behar da."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Sistemaren erro fitxategi-sistema MD array (RAID) batetan kokaturik "
#~ "badago, berau abio sekuentziaren hasieran abiarazi behar da. MD batetan "
#~ "kokaturiko bolumen logiko (LVM) batetan badago osatzen duten array "
#~ "guztiak abiarazi behar dira."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 ""
#~ "Erro fitxategi-sistema erabiltzeko beharrezkoak diren arrayak zehazki "
#~ "jakin eta beste array-en abiaraztea abioaren beranduagoko puntu batetara "
#~ "atzeratu nahi baduzu, idatzi abiarazi beharreko array-ak hemen. Bestela "
#~ "idatzi 'denak' array erabilgarri guztiak abiarazteko."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 ""
#~ "Ez baduzu erro fitxategi sistemarako array-rik abiarazi behar, hutsik "
#~ "utzi ezazu (edo 'batez' idatzi). Hau abioan array-rik behar ez duzulako "
#~ "edo kernel auto-abioa erabiltzen duzulako izan daiteke."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Errore bat gertatu da: gailu nodoa ez dago"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Errore bat gertatu da: ez da bloke gailu bat"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Errore bat gertatu da: ez da MD array bat"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr ""
#~ "Errore bat gertatu da: array-a ez dago mdadm.conf fitxategian "
#~ "zerrendaturik"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Abiarazi mdadm.conf fitxategian ez dauden array-ak?"
#~ msgid ""
#~ "The specified array (${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 ""
#~ "Zehazturiko (${array}) array-a ez dago (${config}) konfigurazio "
#~ "fitxategian zerrendaturiko. Horregatik ezin da abioan abiarazi zuk "
#~ "konfigurazio fitxategia konpondu eta abio ramdiskoa bersortu arte."
#~ 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 ""
#~ "Abisu hau abiarazi ahal izateko ramdisk.etik array-ak baiaraztea behar "
#~ "baduzu bakarrik da garrantzitsua. Kernel auto-abioa erabiltzen baduzu edo "
#~ "ez baduzu ramdisk-etik hasieran array-rik kargatzea behar aurrera "
#~ "jarraitu dezakezu. Bestela ez jarraitzea hautatu eta 'batez' idatzi "
#~ "hasierako ramdisk-etik kargatu beharreko array-ez galdetzean."

190
debian/po/fi.po vendored Normal file
View file

@ -0,0 +1,190 @@
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-10-13 10:58+0300\n"
"Last-Translator: Ari Ervasti <ari.ervasti87@gmail.com>\n"
"Language-Team: Finnish <debian-l10n-finnish@lists.debian.org>\n"
"Language: fi\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.3\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Tulisiko mdadm:n tarkistaa kuukausittain MD-pakkojen eheys?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 ""
"Ohjelma mdadm voi säännöllisesti tarkistaa MD-pakkojen (RAIDien) tietojen "
"monistuksen, jos ydin tukee tätä (versiosta 2.6.14 eteenpäin). Tämä prosessi "
"voi paikallisesta kokoonpanosta riippuen kuluttaa paljon resursseja, mutta "
"saattaa ehkäistä tietojen menetyksiä tietyissä harvinaisissa tapauksissa. "
"Tarkistus vaatii vain tietojen lukemista, jos virheitä ei löyty. Jos "
"virheitä löytyy, mdadm yrittää korjata ne, jolloin levylle saatetaan myös "
"kirjoittaa."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Oletuksena, jos tarkistus on käytössä, se tehdään kuukauden ensimmäisenä "
"sunnuntaina kello 01.06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
"Tulisiko mdadm-ohjelman tehdä tarkastus kerran päivässä pilkkoutuneiden "
"taulujen varalta?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm voi tehdä tarkastuksen kerran päivässä pilkkoutuneiden taulujen ja "
"puuttuvien osien varalta varmistaakseen, ettei sellaista tapahdu huomaamatta."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Haluatko käynnistää MD-seurannan?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD-pakkoja (RAIDeja) seuraava taustaohjelma lähettää tietoja sähköpostiin "
"tärkeiden MD-tapahtumien (kuten levyrikon) sattuessa."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Tämän valitseminen on suositeltavaa."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Sähköpostiviestien vastaanottaja:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Anna sähköpostiosoite, johon sähköpostitiedotteet tärkeistä MD-tapahtumista "
"lähetetään."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Juuritiedostojärjestelmän tarvitsemat MD-pakat:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Syötä ”all” (kaikki), ”none” (ei mitään) tai välilyönnein eroteltu lista "
#~ "laitteista, esimerkiksi ”md0 md1” tai ”md/1 md/d0” (edeltävä /dev/ "
#~ "voidaan jättää pois)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "vain sisäiseen käyttöön - vain pitkä kuvaus on tarpeellinen."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Jos järjestelmän juuritiedostojärjestelmä sijaitsee MD-levypakassa "
#~ "(RAID), pakka tulee käynnistää aikaisessa vaiheessa käynnistettäessä "
#~ "järjestelmää. Jos se sijaitsee loogisella taltiolla (LVM), joka on MD-"
#~ "pakassa, kaikki taltioon liittyvät pakat tulee käynnistää."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 ""
#~ "Jos tiedät tarkalleen mitä pakkoja tarvitaan juuritiedostojärjestelmän "
#~ "käynnistämiseen ja haluat viivästyttää muiden pakkojen käynnistystä, "
#~ "syötä käynnistettävät pakat tähän. Vaihtoehtoisesti voit käynnistää "
#~ "kaikki pakat syöttämällä ”all”."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 ""
#~ "Jos mitään pakkoja ei tarvitse käynnistää juuritiedostojärjestelmän "
#~ "käyttämiseksi, jätä kenttä tyhjäksi (tai syötä ”none”). Tämä voi olla "
#~ "tilanne, jos käytät ytimen autokäynnistystä tai et tarvitse mitään "
#~ "pakkoja käynnistykseen."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Tapahtui virhe: laitetiedostoa ei ole olemassa"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Tapahtui virhe: ei lohkolaite"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Tapahtui virhe: ei MD-pakka"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Tapahtui virhe: pakkaa ei ole listattu tiedostossa mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr ""
#~ "Käynnistetäänkö pakat, joita ei ole listattu tiedostossa mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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 ""
#~ "Annettua pakkaa (${array}) ei ole listattu asetustiedostossa (${config}). "
#~ "Niinpä sitä ei voida käynnistää käynnistettäessä järjestelmä, ellei "
#~ "asetustiedostoa korjata ja käynnistysmuistilevyä (initrd) luoda uudelleen."
#~ 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 ""
#~ "Tämä varoitus on aiheellinen vain, jos järjestelmän käynnistäminen vaatii "
#~ "pakkojen käynnistämistä käynnistysmuistilevyltä. Jos ytimen "
#~ "autokäynnistys on käytössä tai pakkoja ei tarvita siinä vaiheessa, kun "
#~ "käynnistysmuistilevy ladataan, voit jatkaa. Vaihtoehtoisesti voit olla "
#~ "jatkamatta ja syöttää ”none” kysyttäessä käynnistysmuistilevyltä "
#~ "käynnistettäviä pakkoja."

205
debian/po/fr.po vendored Normal file
View file

@ -0,0 +1,205 @@
# Translation of mdadm debconf templates to French
# Copyright (C) 2008 Florentin Duneau <fduneau@gmail.com>
# This file is distributed under the same license as the lurker package.
#
#
# Éric Madesclair <eric-m@wanadoo.fr>, 2005, 2006.
# Jean-Luc Coulon (f5ibh) <jean-luc.coulon@wanadoo.fr>, 2006.
# Florentin Duneau <fduneau@gmail.com>, 2006, 2007, 2008.
# Grégoire Scano <gregoire.scano@malloc.fr>, 2019.
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2019-08-13 16:52+0800\n"
"Last-Translator: Grégoire Scano <gregoire.scano@malloc.fr>\n"
"Language-Team: French <debian-l10n-french@lists.debian.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: KBabel 1.11.4\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Faut-il vérifier chaque mois la redondance des ensembles RAID ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 ensembles 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Par défaut, la vérification s'effectuera tous les premiers dimanche du mois "
"à 01 h 06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
"Faut-il rechercher l'existence d'ensembles RAID dégradés tous les jours ?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm peut rechercher des ensembles RAID dégradés et des disques de secours "
"manquants une fois par jour pour s'assurer que de tels évènements ne passent "
"pas inaperçus."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
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:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Le démon de surveillance MD envoie des notifications par courriel lors "
"d'importants événements MD (comme une panne de disque dur)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Il est recommandé d'activer cette option."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinataire des notifications par courriel :"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Veuillez indiquer l'adresse électronique de l'utilisateur qui doit recevoir "
"les notifications lors d'importants événements MD."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Ensembles MD requis par le système de fichiers racine :"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Veuillez indiquer « all », « none » ou une liste de périphériques, "
#~ "séparés par des espaces, par exemple, « md0 md1 » ou « md/1 md/d0 » (vous "
#~ "pouvez omettre « /dev/ »)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr ""
#~ "Pour une utilisation interne - seule la description longue est nécessaire"
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located 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."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 "
#~ "entrez « none »). Ceci peut être le cas si vous utilisez l'option de "
#~ "démarrage automatique (« autostart ») du noyau ou si vous n'avez besoin "
#~ "d'aucun ensemble pour démarrer."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Erreur : périphérique inconnu"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Erreur : ce n'est pas un périphérique en mode bloc"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Erreur : ce n'est pas un ensemble RAID"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Erreur : ensemble non mentionné dans le fichier mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr ""
#~ "Faut-il démarrer les ensembles RAID non mentionnés dans mdadm.conf ?"
#~ msgid ""
#~ "The specified array (${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 »)."
#~ 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 si des ensembles RAID doivent "
#~ "être lancés à 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 depuis le disque mémoire "
#~ "initial, vous pouvez simplement poursuivre. Vous pouvez aussi choisir de "
#~ "ne pas poursuivre et entrer « none » lorsqu'il vous sera demandé le nom "
#~ "des ensembles RAID à démarrer à partir du disque mémoire initial."

191
debian/po/gl.po vendored Normal file
View file

@ -0,0 +1,191 @@
# Galician translation of mdadm's debconf templates
# This file is distributed under the same license as the mdadm package.
# Jacobo Tarrio <jtarrio@debian.org>, 2007, 2008.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2008-02-06 23:45+0000\n"
"Last-Translator: Jacobo Tarrio <jtarrio@debian.org>\n"
"Language-Team: Galician <proxecto@trasno.net>\n"
"Language: gl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 núcleo ten soporte para iso (en versións superiores á 2.6.14), mdadm "
"pode facer comprobacións periódicas de redundancia dos arrays MD (RAIDs). "
"Este pode ser un proceso intensivo en recursos, dependendo da configuración "
"local, 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
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:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
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:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
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)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Recoméndase activar esta opción."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatario para os avisos por email:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Introduza o enderezo de email do usuario que debe recibir os avisos por "
"email de eventos importantes de MD."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Arrays MD necesarios para o sistema de ficheiros raíz"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Introduza \"all\" (todos), \"none\" (ningún) ou unha lista de "
#~ "dispositivos separados por espazos, tales coma \"md0 md1\" ou \"md/1 "
#~ "md/0\" (pódese omitir o \"/dev/\" do principio)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "para uso interno - só se precisa da descrición longa."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Se o sistema de ficheiros raíz do sistema está ubicado nun array MD "
#~ "(RAID), hai que o iniciar no principio da secuencia de inicio. Se está "
#~ "ubicado nun volume lóxico (LVM) que está nun MD, hai que iniciar os "
#~ "arrays constituíntes."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Houbo un erro: o nodo do dispositivo non existe"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Houbo un erro: non é un dispositivo de bloques"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Houbo un erro: non é un array MD"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Houbo un erro: o array non figura no ficheiro mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "¿Iniciar os arrays que non figuran en mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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 indicado (${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."
#~ 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."

194
debian/po/it.po vendored Normal file
View file

@ -0,0 +1,194 @@
# Italian (it) translation of debconf templates for mdadm
# Copyright (C) 2008 Software in the Public Interest
# This file is distributed under the same license as the mdadm package.
# Luca Monducci <luca.mo@tiscali.it>, 2008-2020.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm italian debconf\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-09-16 20:02+0200\n"
"Last-Translator: Luca Monducci <luca.mo@tiscali.it>\n"
"Language-Team: Italian <debian-l10n-italian@lists.debian.org>\n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Far eseguire a mdadm i controlli mensili di ridondanza sugli array MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 il kernel lo supporta (tutte le versioni successive la 2.6.14), mdadm può "
"effettuare delle verifiche periodiche sulla ridondanza degli array MD "
"(RAID). Questo è un processo che potrebbe richiedere molte risorse, in base "
"alle impostazioni locali, ma può prevenire i rari casi di perdita di dati. "
"Notare che questa verifica è di sola-lettura tranne quando riscontra degli "
"errori; quando ci sono errori, mdadm prova a correggerli e potrebbe accedere "
"in scrittura al supporto."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Se attivo, la configurazione predefinita prevede che il controllo sia "
"eseguito la prima domenica di ogni mese alle 01.06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Far eseguire a mdadm il controllo quotidiano di degrado degli array?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm può controllare una volta al giorno il degrado degli array e "
"l'assenza dei dischi di scorta in modo che questi eventi non passino "
"inosservati."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Avviare il demone di monitoraggio MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Il demone di monitoraggio MD (RAID) invia delle notifiche via email quando "
"si verificano eventi importanti (come la rottura di un disco)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Si raccomanda l'attivazione di questa funzione."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatario delle email di notifica:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Inserire l'indirizzo email dell'utente che deve ricevere le notifiche di "
"eventi importanti legati al MD."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Array MD necessari per il file system di root:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Inserire \"all\", \"none\" oppure un elenco dei device separati da uno "
#~ "spazio, per esempio \"md0 md1\" o \"md/1 md/d0\" (il \"/dev/\" iniziale "
#~ "può essere omesso)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "uso interno - è necessaria solo la descrizione lunga."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Se il file system di root è su un array MD (RAID), è necessario attivare "
#~ "tale array all'inizio della sequenza d'avvio. Se è su un volume logico "
#~ "(LVM), il quale è su un MD, è necessario attivare tutti gli array che "
#~ "costituiscono il volume."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 si conoscono esattamente quali sono gli array da attivare per il file "
#~ "system di root e si vuole rimandare l'attivazione di tutti gli altri "
#~ "array a una fase successiva della sequenza d'avvio, inserire adesso gli "
#~ "array da attivare. In alternativa, inserire \"all\" per attivare tutti "
#~ "gli array disponibili."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 si ha bisogno o non si vuole attivare nessun array per il file "
#~ "system di root, lasciare la risposta in bianco (oppure inserire \"none"
#~ "\"). Questo potrebbe essere il caso se si utilizza l'attivazione "
#~ "automatica da kernel oppure se non si ha bisogno di alcun array per "
#~ "l'avvio."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Errore: il nodo del device non esiste"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Errore: non è un device a blocchi"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Errore: non è un array MD"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Errore: array non elencato nel file mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Avviare gli array non elencati in mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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'array specificato (${array}) non è presente nel file di configurazione "
#~ "(${config}): quindi non può essere attivato durante l'avvio senza "
#~ "correggere il file di configurazione e ricreare il ramdisk iniziale."
#~ 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 ""
#~ "Questo avviso è pertinente solo se è necessario attivare gli array dal "
#~ "ramdisk iniziale per permettere l'avvio. Con l'avvio automatico da kernel "
#~ "o se non è necessario attivare gli array così presto come al caricamento "
#~ "del ramdisk iniziale, si può proseguire. In alternativa, scegliere di non "
#~ "continuare e inserire \"none\" quando viene chiesto quali array attivare "
#~ "dal ramdisk iniziale."

247
debian/po/ja.po vendored Normal file
View file

@ -0,0 +1,247 @@
#
# 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.6.3+200709292116+4450e59-4\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2008-02-07 05:52+0900\n"
"Last-Translator: Hideki Yamane (Debian-JP) <henrich@debian.or.jp>\n"
"Language-Team: Japanese <debian-japanese@lists.debian.org>\n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "mdadm は、毎月 MD アレイの冗長性チェックを行いますか?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"有効にした場合、デフォルトでは毎月第一日曜 01:06 にチェックが実行されます。"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "MD 監視デーモンを起動しますか?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD (RAID) 監視デーモンは、重大な MD 関連のイベント (ディスク障害など) に対し"
"てメールで通知を送ります。"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "この機能を有効にするのをお勧めします。"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "メール通知の宛先:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"MD 関連の重大なイベントが発生した際、メールでの通知を受け取る必要があるユーザ"
"のメールアドレスを入力してください。"
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "ルートファイルシステムに必要な MD アレイ:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "'all' または 'none'、あるいはデバイスのリストを 'md0 md1' や 'md/1 md/d0' "
#~ "のようにスペースで区切って入力してください (前に付く '/dev/' は省略可能で"
#~ "す)。"
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "内部での利用について - でも、長い説明が必要です。"
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "あなたのシステムのルートファイルシステムが MD アレイ (RAID) 上に配置されて"
#~ "いるならば、ブートシーケンスの初期段階で MD アレイを開始する必要がありま"
#~ "す。ルートファイルシステムが MD のような論理ボリューム (LVM) 上にある場合"
#~ "は、構成しているアレイ全ての開始が必要です。"
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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' と入力して単に全ての利用可能なアレイを最初に立ち上げてください。"
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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' と入力) してく"
#~ "ださい。これは、カーネルで自動的に起動される場合や起動時にはアレイは不要で"
#~ "あるという場合です。"
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "エラーが発生しました: デバイスノードが存在しません"
#~ msgid "An error occurred: not a block device"
#~ msgstr "エラーが発生しました: ブロックデバイスではありません"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "エラーが発生しました: MD アレイではありません"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr ""
#~ "エラーが発生しました: mdadm.conf ファイルに記述されていないアレイです"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "mdadm.conf に記述されていないアレイを起動しますか?"
#~ msgid ""
#~ "The specified array (${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 を再生成しなければブート時に起"
#~ "動できません。"
#~ 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' と入力します。"
#~ 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 アレイに属しているディスクが故障"
#~ "するか何らかの理由で変化した際にメールで通知が送られます。"

119
debian/po/nl.po vendored Normal file
View file

@ -0,0 +1,119 @@
# Dutch translation for the configuration of mdadm
#
# 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'
#
# Frans Pop <aragorn@tiscali.nl>, 2005, 2006.
# Frans Pop <elendil@planet.nl>, 2008.
# Maarten <Maarten@posteo.de>, 2019.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 4.1-3\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2019-09-19 22:51+0200\n"
"Last-Translator: Maarten <Maarten@posteo.de>\n"
"Language-Team: Dutch <debian-l10n-dutch@lists.debian.org>\n"
"Language: nl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 1.8.11\n"
# Zie voor mijn notatie het artikel over 'disk array' in de Engelse Wikipedia. Zie ook het artikel over 'Disk-Array' in de Duitse Wikipedia. De Duitsers vertalen 'disk' dus niet naar 'Festplatte'.
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
"Moet mdadm maandelijkse redundatiecontroles van de disk-arrays uitvoeren?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 (de versie is groter dan 2.6.14), dan kan "
"mdadm periodiek de redundantie van uw disk-arrays controleren. Afhankelijk "
"van de configuratie kan dit een zware systeembelasting teweegbrengen, maar "
"het zou ook zeldzame gevallen van gegevensverlies kunnen voorkomen. De "
"controle gebruikt alleen leesopdrachten, tenzij fouten worden gevonden. Als "
"fouten worden gevonden, dan zal mdadm deze proberen te herstellen, hetgeen "
"schrijfopdrachten tot gevolg kan hebben."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Als de controle is geactiveerd, dan wordt deze standaard uitgevoerd op elke "
"eerste zondag van de maand om 01:06 uur 's nachts."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Moet mdadm eens per dag controleren op in verval geraakte disk-arrays?"
# such events -> those events
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm kan eens per dag controleren op in verval geraakte disk-arrays en op "
"ontbrekende reserveschijven om er zeker van te zijn dat die toestanden niet "
"onopgemerkt blijven."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Wilt u de achtergronddienst voor de disk-array-monitor starten?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"De achtergronddienst voor de disk-array-monitor stuurt per e-mail berichten "
"bij belangrijke gebeurtenissen (zoals de uitval van een harde schijf)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Gebruik van deze optie wordt aanbevolen."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Adres voor e-mailberichten:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Voer het e-mailadres in van de gebruiker die de e-mailberichten over "
"belangrijke gebeurtenissen met betrekking tot de disk-arrays dient te "
"ontvangen."

196
debian/po/pt.po vendored Normal file
View file

@ -0,0 +1,196 @@
# Portuguese translation for mdadm debconf messages.
# Copyright (C) 2008 Pedro Ribeiro <p.m42.ribeiro@gmail.com>
# This file is distributed under the same license as the mdadm package.
# Pedro Ribeiro <p.m42.ribeiro@gmail.com>, 2008
# Miguel Figueiredo <elmig@debianpt.org>, 2020
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 2.6.3+200709292116+4450e59-4\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-10-10 09:47+0100\n"
"Last-Translator: Miguel Figueiredo <elmig@debianpt.org>\n"
"Language-Team: Portuguese <traduz@debianpt.org>\n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 (versões mais recentes que 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 "
"acessosde escrita aos discos."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"O pré-definido, se ligado, é os testes serem executados no primeiro Domingo "
"de cada mês às 01:06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Deve o mdadm verificar arrays degradados, uma vez por dia?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"O mdadm pode verificar uma vez por dia a existência de arrays degradados e "
"spares em falta para assegurar que tais eventos não passam despercebidos."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
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:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"O daemon 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: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "É recomendado activar esta opção."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatário de email para notificações:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Por favor, introduza o endereço de email do utilizador que deve receber as "
"notificações de eventos MD importantes."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Grupos MD necessários para o sistema de ficheiros raiz:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Por favor, introduza 'all', 'none', ou uma lista de dispositivos "
#~ "separados por espaços, tais como 'md0 md1' ou 'md/1 md/d0' (o '/dev/' "
#~ "inicial pode ser omitido)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "para uso interno - apenas a descrição longa é necessária"
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Se o sistema de ficheiros de raiz do sistema estiver 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."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Ocorreu um erro: o nó do dispositivo não existe"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Ocorreu um erro: não é um dispositivo de bloco"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Ocorreu um erro: não é um grupo MD"
#~ 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"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Iniciar grupos não listados no mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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 simplesmente continuar. Em alternativa, escolha "
#~ "não continuar e introduza 'none' quando perguntado sobre quais grupos "
#~ "iniciar a partir do ramdisk inicial."

308
debian/po/pt_BR.po vendored Normal file
View file

@ -0,0 +1,308 @@
# Debconf translations for mdadm.
# Copyright (C) 2006 THE mdadm'S COPYRIGHT HOLDER
# This file is distributed under the same license as the sysvinit package.
# Felipe Augusto van de Wiel (faw) <faw@cathedrallabs.org>, 2006.
# Adriano Rafael Gomes <adrianorg@debian.org>, 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-10-09 17:50-0300\n"
"Last-Translator: Adriano Rafael Gomes <adrianorg@debian.org>\n"
"Language-Team: Brazilian Portuguese <debian-l10n-portuguese@lists.debian."
"org>\n"
"Language: pt_BR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
#| 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."
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 tiver suporte (versões maiores que 2.6.14), o mdadm pode "
"periodicamente checar a redundância dos seus dispositivos MD (RAIDs). Este "
"pode ser um processo com uso intensivo dos recursos, dependendo da sua "
"configuração local, mas pode ajudar a prevenir casos raros de perda de "
"dados. Note que esta é uma checagem somente leitura, a menos que erros sejam "
"encontrados. Se erros forem encontrados, o mdadm tentará corrigi-los, o que "
"poderá resultar em acesso de escrita na mídia."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
#| msgid ""
#| "The default, if turned on, is to run the checks on the first Sunday of "
#| "every month at 01:06 o'clock."
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"O padrão, se ativado, é checar no primeiro domingo de cada mês à 01:06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "O mdadm deve checar diariamente por dispositivos degradados?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"O mdadm pode checar diariamente por dispositivos degradados e por "
"dispositivos reserva em falta para garantir que tais eventos não passem "
"despercebidos."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Você deseja iniciar o \"daemon\" de monitoramento MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
#| 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."
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"O \"daemon\" de monitoramento MD (RAID) envia e-mails de notificações em "
"resposta a eventos MD importantes (como uma falha de disco)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "É recomendado habilitar esta opção."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Destinatário para os e-mails de notificações:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
#| msgid ""
#| "Please enter the email address of the user who should get the email "
#| "notification for important MD events."
msgid ""
"Please enter the email address of the user who should get the email "
"notifications 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."
#, fuzzy
#~| msgid "MD arrays needed for the root filesystem:"
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Dispositivos MD necessários para o sistema de arquivos raiz:"
#, fuzzy
#~| 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\"."
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ 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\"."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "para uso interno - apenas a descrição longa é necessária."
#, fuzzy
#~| 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."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located 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."
#, fuzzy
#~| 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."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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."
#, fuzzy
#~| 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."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Um erro ocorreu: o dispositivo (\"device node\") não existe"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Um erro ocorreu: não é um dispositivo de blocos"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Um erro ocorreu: não é um dispositivo MD"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Um erro ocorreu: dispositivo não listado no arquivo mdadm.conf"
#, fuzzy
#~| msgid "Proceed with starting arrays not listed in mdadm.conf?"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Continuar com o início de dispositivos não listados no mdadm.conf?"
#, fuzzy
#~| 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."
#~ msgid ""
#~ "The specified array (${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."
#~ 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."
#~ 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 ?"

208
debian/po/ru.po vendored Normal file
View file

@ -0,0 +1,208 @@
# translation of 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 <kozlov.y@gmail.com>, 2006, 2008.
# Yuri Kozlov <yuray@komyakino.ru>, 2020.
msgid ""
msgstr ""
"Project-Id-Version: 4.1-6\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-09-16 06:37+0300\n"
"Last-Translator: Yuri Kozlov <yuray@komyakino.ru>\n"
"Language-Team: Russian <debian-l10n-russian@lists.debian.org>\n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 20.04.3\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: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
"Должен ли mdadm запускать ежемесячную проверку избыточности на MD-массивах?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Если ответить утвердительно, то по умолчанию проверка выполняется в первое "
"воскресенье каждого месяца в 01:06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
"Должен ли mdadm запускать ежедневную проверку наличия повреждённых массивов?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm может ежедневно проверять наличие повреждённых массивов и "
"отсутствие резерва, чтобы эти события не остались незамеченными."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Запускать службу слежения MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Служба слежения MD (RAID) посылает почтовые уведомления в случае"
" возникновения "
"важных событий MD (таких как отказ диска)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Рекомендуется ответить утвердительно."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Получатель уведомительных писем:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Введите адрес электронной почты пользователя, который будет получать "
"почтовые уведомления о важных событиях MD."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "MD-массивы, необходимые для корневой файловой системы:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Введите список устройств через пробел, слово 'all' или 'none'. Вы можете "
#~ "не указывать начальную часть пути типа '/dev/', а просто вводить имена "
#~ "устройств, например 'md0 md1' или 'md/1 md/d0'."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr ""
#~ "для внутреннего пользования - нужно использовать только длинное описание."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Если в системе корневая файловая система расположена на MD-массиве "
#~ "(RAID), он должен быть запущен в самом начале процесса загрузки. Если "
#~ "корневая файловая система расположена на логическом томе (LVM), который "
#~ "расположен на MD, то должны быть запущены все составляющие массивы."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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', чтобы просто запустить все "
#~ "доступные массивы."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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'). "
#~ "Этот вариант подходит, если вы используете автоматический запуск из ядра "
#~ "или если для загрузки массивы ненужны."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Произошла ошибка: нода устройства не существует"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Произошла ошибка: устройство не является блочным"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Произошла ошибка: это не MD-массив"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Произошла ошибка: массив не описан в файле mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Запустить массивы, неописанные в mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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."

193
debian/po/sk.po vendored Normal file
View file

@ -0,0 +1,193 @@
# Slovak translations for mdadm package
# Slovenské preklady pre balík mdadm.
# Copyright (C) 2011 THE mdadm'S COPYRIGHT HOLDER
# This file is distributed under the same license as the mdadm package.
# Automatically generated, 2011.
# Slavko <linux@slavino.sk>, 2011-2020.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 4.1-6\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2020-09-15 12:39+0200\n"
"Last-Translator: Slavko <linux@slavino.sk>\n"
"Language-Team: slovenčina <linux@slavino.sk>\n"
"Language: sk\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n"
"X-Generator: Geany / PoHelper 1.36\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr "Má mdadm spúšťať mesačnú kontrolu redundancie polí MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 ""
"Ak to jadro podporuje (verzie novšie ako 2.6.14), mdadm môže periodicky "
"kontrolovať redundanciu polí MD (RAIDov). Tento proces môže byť (v "
"závislosti od lokálneho nastavenia) náročný na zdroje systému, ale môže "
"pomôcť pri predchádzaní vzácnym prípadom straty dát. Pamätajte, že, pokiaľ "
"nie sú nájdené chyby, je to kontrola len čítaním, až keď sú nájdené chyby, "
"mdadm sa ich pokúsi opraviť, čo môže mať za následok zápis na médium."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Predvolene je vypnuté, ak túto možnosť zapnete, bude kontrola vykonávaná "
"každú prvú nedeľu mesiaca o 01:06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr "Má mdadm raz denne zisťovať degradované polia?"
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
"mdadm môže raz denne zisťovať degradované polia a chýbajúce náhradné "
"zariadenia, aby zaistil, že takéto udalosti neostanú nepovšimnuté."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Chcete spustiť démona monitorovania MD?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Monitorovací démon MD (RAID) posiela upozornenia emailom, ako reakcie na "
"dôležité udalosti MD (napr. zlyhanie disku)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Povolenie tejto možnosti je odporúčané."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Adresát emailových upozornení:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""
"Prosím, zadajte emailovú adresu používateľa, ktorý má dostávať emailové "
"upozornenia na dôležité udalosti MD."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Polia MD, potrebné pre koreň súborového systému:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Prosím, zadajte „all”, „none” alebo medzerou oddelený zoznam zariadení, "
#~ "napr. „md0 md1” alebo „md/1 md/d0” (počiatočné „/dev/” môže byť "
#~ "vynechané)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "na interné použitie – potrebný je len dlhý popis."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Ak je koreň súborového systému umiestnený na poli MD (RAID), musí byť "
#~ "spustený počas zavádzania systému. Ak je koreň umiestnený na logickom "
#~ "zväzku (LVM), ktorý je na MD, musia byť spustené všetky súvisiace polia."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 ""
#~ "Ak viete presne, ktoré polia sú potrebné na pripojenie koreňa súborového "
#~ "systému a chcete odložiť štart všetkých ostatných polí na neskorší okamih "
#~ "zavádzania, zadajte tu polia, ktoré majú byť spustené. Alebo zadajte "
#~ "„all”, čím budú jednoducho spustené všetky dostupné polia."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 ""
#~ "Ak pre koreň súborového systému nepotrebujete alebo nechcete spúšťať "
#~ "žiadne polia, nechajte odpoveď prázdnu (alebo zadajte „none”). Tento "
#~ "prípad môže nastať, ak používate automatický štart polí priamo v jadre "
#~ "alebo nepotrebujete pri zavádzaní žiadne polia."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Nastala chyba: uzol zariadenia neexistuje"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Nastala chyba: nie je blokové zariadenie"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Nastala chyba: nie je pole MD"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Nastala chyba: pole nie je uvedené v súbore mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Spustiť polia, ktoré nie sú uvedené v mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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}) nie je uvedené v konfiguračnom súbore (${config}), "
#~ "a preto nemôže byť spustené počas zavádzania, až kým neopravíte "
#~ "konfiguračný súbor a nevytvoríte nový počiatočný ramdisk (initrd)."
#~ 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 varovanie je dôležité, len ak potrebujete aby boli polia spúšťané z "
#~ "počiatočného ramdisku, aby boli dostupné počas zavádzania. Ak používate "
#~ "automatické spúšťanie polí priamo z jadra, alebo ak nepotrebujte aby boli "
#~ "polia spúšťané tak skoro (z počiatočného ramdisku), môžete prosto "
#~ "pokračovať. Alebo môžete zvoliť nepokračovať a odpovedať „none” na "
#~ "otázku, ktoré polia majú byť spúšťané z počiatočného ramdisku."

200
debian/po/sv.po vendored Normal file
View file

@ -0,0 +1,200 @@
# translation of mdadm_2.6.7-3_sv.po to Swedish
# 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.
#
# Martin Ågren <martin.agren@gmail.com>, 2008.
msgid ""
msgstr ""
"Project-Id-Version: mdadm_2.6.7-3_sv\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2008-07-23 18:34+0200\n"
"Last-Translator: Martin Ågren <martin.agren@gmail.com>\n"
"Language-Team: Swedish <debian-l10n-swedish@lists.debian.org>\n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 har stöd för det (versioner senare än 2.6.14), 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 kommer "
"mdadm försöka att rätta till dem, vilket kan leda till skrivåtkomst till "
"mediet."
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
"Standardvärdet, om påslagen, är att kontrollera på den första söndagen i "
"varje månad klockan 01.06."
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr "Vill du starta MD-övervakningsdemonen?"
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"MD-övervakningsdemonen (RAID) skickar e-postnotifieringar för viktiga MD-"
"händelser (såsom ett diskfel)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Att aktivera denna funktion rekommenderas."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Mottagare av e-postnotifieringar:"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications 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 "MD arrays needed for the root file system:"
#~ msgstr "MD-kedjor som behövs för rotfilsystemet:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Ange \"all\", \"none\" eller en blankstegsseparerad lista på enheter, "
#~ "såsom \"md0 md1\" eller \"md/1 md/0\" (det inledande \"/dev\" kan "
#~ "uteslutas)."
#~ msgid "for internal use - only the long description is needed."
#~ msgstr "för intern användning - endast den långa beskrivningen behövs."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located 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."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 senare "
#~ "tidspunkt i uppstartssekvensen, ange vilka kedjor som ska starta här. "
#~ "Alternativt, ange \"all\" för att helt enkelt starta alla tillgängliga "
#~ "kedjor."
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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\"). Detta kan vara fallet om du "
#~ "använder kärnans automatstart eller inte behöver några kedjor för att "
#~ "starta upp."
#~ msgid "An error occurred: device node does not exist"
#~ msgstr "Ett fel inträffade: enhetsnoden finns inte"
#~ msgid "An error occurred: not a block device"
#~ msgstr "Ett fel inträffade: inte en blockenhet"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Ett fel inträffade: inte en MD-kedja"
#~ msgid "An error occurred: array not listed in mdadm.conf file"
#~ msgstr "Ett fel inträffade: kedjan är inte listad i filen mdadm.conf"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr "Starta kedjor som inte är listade i mdadm.conf?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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."

92
debian/po/templates.pot vendored Normal file
View file

@ -0,0 +1,92 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the mdadm package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: mdadm\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid "Should mdadm run monthly redundancy checks of the MD arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Do you want to start the MD monitoring daemon?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr ""
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr ""
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications for important MD events."
msgstr ""

193
debian/po/vi.po vendored Normal file
View file

@ -0,0 +1,193 @@
# Vietnamese Translation for mdadm.
# Copyright © 2008 Free Software Foundation, Inc.
# Clytie Siddall <clytie@riverland.net.au>, 2005-2008.
#
msgid ""
msgstr ""
"Project-Id-Version: mdadm 2.6.3+200709292116+4450e59-4\n"
"Report-Msgid-Bugs-To: mdadm@packages.debian.org\n"
"POT-Creation-Date: 2019-02-09 08:48+0100\n"
"PO-Revision-Date: 2008-02-23 17:40+1030\n"
"Last-Translator: Clytie Siddall <clytie@riverland.net.au>\n"
"Language-Team: Vietnamese <vi-VN@googlegroups.com>\n"
"Language: vi\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.7b3\n"
#. Type: boolean
#. Description
#: ../mdadm.templates:2001
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:2001
msgid ""
"If the kernel supports it (versions greater than 2.6.14), mdadm can "
"periodically check the redundancy of MD arrays (RAIDs). This may be a "
"resource-intensive process, depending on the local 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 có phải hỗ trợ (các phiên bản sau 2.6.14) thì 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 cục bộ, 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: gặp lỗi thì 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:2001
msgid ""
"The default, if turned on, is to check on the first Sunday of every month at "
"01:06."
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:3001
msgid "Should mdadm check once a day for degraded arrays?"
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:3001
msgid ""
"mdadm can check once a day for degraded arrays and missing spares to ensure "
"that such events don't go unnoticed."
msgstr ""
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
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:4001
msgid ""
"The MD (RAID) monitor daemon sends email notifications in response to "
"important MD events (such as a disk failure)."
msgstr ""
"Trình nền theo dõi MD (RAID) gửi thư thông báo hưởng ứng dữ kiện MD quan "
"trọng (v.d. đĩa bị hỏng)."
#. Type: boolean
#. Description
#: ../mdadm.templates:4001
msgid "Enabling this option is recommended."
msgstr "Khuyên bạn hiệu lực tùy chọn này."
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid "Recipient for email notifications:"
msgstr "Người nhận thư thông báo :"
#. Type: string
#. Description
#: ../mdadm.templates:5001
msgid ""
"Please enter the email address of the user who should get the email "
"notifications 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ề dữ kiện MD "
"quan trọng."
#~ msgid "MD arrays needed for the root file system:"
#~ msgstr "Các mảng MD cần thiết cho hệ thống tập tin gốc:"
#~ msgid ""
#~ "Please enter 'all', 'none', or a space-separated list of devices such as "
#~ "'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted)."
#~ msgstr ""
#~ "Hãy nhập « all » (tất cả), « none » (không có), hoặc một danh sách các "
#~ "thiết bị định giới bằng dấu cách như « md0 md1 » hoặc « md/1 md/d0 » (có "
#~ "thể bỏ sót phần « /dev/ » đi trước)."
#~ 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."
#~ msgid ""
#~ "If the system's root file system is located on an MD array (RAID), it "
#~ "needs to be started early during the boot sequence. If it is located on a "
#~ "logical volume (LVM), which is on MD, all constituent arrays need to be "
#~ "started."
#~ msgstr ""
#~ "Nếu hệ thống tập tin gốc của hệ thống nằm trên một mảng MD (RAID) thì cần "
#~ "phải khởi chạy nó sớm trong tiến trình khởi động. Nếu nó nằm trên một "
#~ "khối tin hợp lý (LVM) mà lần lượt nằm trên một MD thì cần phải khởi chạy "
#~ "tất cả các mảng thành phần."
#~ msgid ""
#~ "If you know exactly which arrays are needed to bring up the root file "
#~ "system, 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 sẵn sàng. "
#~ msgid ""
#~ "If you do not need or want to start any arrays for the root file system, "
#~ "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 sử dụng khả năng tự động khởi động hạt nhân "
#~ "(kernel autostart), hoặc không cần mảng nào để khởi động máy tính."
#~ 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"
#~ 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"
#~ msgid "An error occurred: not an MD array"
#~ msgstr "Gặp lỗi: không phải là một mảng MD"
#~ 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 »"
#~ msgid "Start arrays not listed in mdadm.conf?"
#~ msgstr ""
#~ "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?"
#~ msgid ""
#~ "The specified array (${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."
#~ 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 tự "
#~ "động khởi chạy hạt nhân (kernel autostart), hoặc không cần mảng nào được "
#~ "khởi chạy một 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."

52
debian/rules vendored Executable file
View file

@ -0,0 +1,52 @@
#!/usr/bin/make -f
# Copyright © 2001-2005 Mario Jou/3en <joussen@debian.org>
# Copyright © 2005-2008 Martin F. Krafft <madduck@debian.org>
# Copyright © 2021 Felix Lechner <felix.lechner@lease-up.com>
# Distributable under the terms of the GNU GPL version 2.
#
#export DH_VERBOSE=1
include /usr/share/dpkg/pkg-info.mk
include /usr/share/dpkg/vendor.mk
export CROSS_COMPILE=$(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)-
export LDFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get LDFLAGS)
export CXFLAGS = $(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CFLAGS) \
$(shell DEB_BUILD_MAINT_OPTIONS=hardening=+all dpkg-buildflags --get CPPFLAGS)
export DEBIAN="yes"
export EXTRAVERSION=$(DEB_VENDOR) $(DEB_VERSION)
# these are reversed in the Makefile
export CONFFILE="/etc/mdadm/mdadm.conf"
export CONFFILE2="/etc/mdadm.conf"
%:
dh $@
override_dh_install:
$(MAKE) install-systemd DESTDIR=$(CURDIR)/debian/tmp
dh_install
mkdir -p $(CURDIR)/debian/mdadm/etc/mdadm
chmod +x $(CURDIR)/debian/mdadm/usr/share/mdadm/mdcheck
ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes), yes)
install -Dm0644 debian/source_mdadm.py \
$(CURDIR)/debian/mdadm/usr/share/apport/package-hooks/source_mdadm.py
endif
override_dh_installsystemd:
dh_installsystemd --name mdadm-shutdown
override_dh_installinit:
dh_installinit --init-script=mdadm-waitidle --no-start -- stop 98 0 6 .
dh_installinit -- defaults 25
override_dh_gencontrol:
ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes), yes)
dh_gencontrol -- -Vmta:Suggests="default-mta | mail-transport-agent"
else
dh_gencontrol -- -Vmta:Recommends="default-mta | mail-transport-agent"
endif

4
debian/salsa-ci.yml vendored Normal file
View file

@ -0,0 +1,4 @@
---
include:
- https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
- https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

1
debian/source/format vendored Normal file
View file

@ -0,0 +1 @@
3.0 (quilt)

60
debian/source_mdadm.py vendored Normal file
View file

@ -0,0 +1,60 @@
'''apport package hook for mdadm
(c) 2009-2016 Canonical Ltd.
Author: Steve Beattie <sbeattie@ubuntu.com>
Based on the ideas in debian's /usr/share/bug/mdadm/script
'''
from apport.hookutils import attach_file, attach_file_if_exists, attach_hardware, path_to_key, command_output
import os
import re
import glob
import gzip
import subprocess
import sys
def get_initrd_files(pattern):
'''Extract listing of files from the current initrd which match a regex.
pattern should be a "re" object. '''
(_, _, release, _, _) = os.uname()
try:
fd = gzip.GzipFile('/boot/initrd.img-' + release, 'rb')
# universal_newlines needs to be False here as we're passing
# binary data from gzip into cpio, which means we'll need to
# decode the bytes into strings later when reading the output
cpio = subprocess.Popen(['cpio', '-t'], close_fds=True, stderr=subprocess.STDOUT,
stdin=subprocess.PIPE, stdout=subprocess.PIPE,
universal_newlines=False)
except OSError as e:
return 'Error: ' + str(e)
out = cpio.communicate(fd.read())[0].decode(sys.stdout.encoding, errors='replace')
if cpio.returncode != 0:
return 'Error: command %s failed with exit code %i %' % (
'cpio', cpio.returncode, out)
lines = ''.join([l for l in out.splitlines(True) if pattern.search(l)])
return lines
def add_info(report):
attach_hardware(report)
attach_file(report, '/proc/mounts', 'ProcMounts')
attach_file_if_exists(report, '/etc/mdadm/mdadm.conf', 'mdadm.conf')
attach_file(report, '/proc/mdstat', 'ProcMDstat')
attach_file(report, '/proc/partitions', 'ProcPartitions')
attach_file(report, '/etc/blkid.tab', 'etc.blkid.tab')
attach_file_if_exists(report, '/boot/grub/menu.lst', 'GrubMenu.lst')
attach_file_if_exists(report, '/boot/grub/grub.cfg', 'Grub.cfg')
attach_file_if_exists(report, '/etc/lilo.conf', 'lilo.conf')
devices = glob.glob("/dev/[hs]d*")
for dev in devices:
report['MDadmExamine' + path_to_key(dev)] = command_output(['/sbin/mdadm', '-E', dev])
initrd_re = re.compile('md[a/]')
report['initrd.files'] = get_initrd_files(initrd_re)

6
debian/tests/control vendored Normal file
View file

@ -0,0 +1,6 @@
Tests: test-installed
Restrictions: needs-root, isolation-machine
Depends:
fdisk | util-linux (<< 2.29.2-3~),
mdadm,
udev

3
debian/tests/test-installed vendored Executable file
View file

@ -0,0 +1,3 @@
#!/bin/sh
./test

7
debian/upstream/metadata vendored Normal file
View file

@ -0,0 +1,7 @@
Archive: kernel.org
Repository: "https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/"
Repository-Browse: "https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/"
Bug-Submit: "http://vger.kernel.org/vger-lists.html#linux-raid"
Bug-Database: "https://marc.info/?l=linux-raid"
Documentation: "https://raid.wiki.kernel.org/index.php/Linux_Raid"
Other-References: "https://mirrors.edge.kernel.org/pub/linux/utils/raid/mdadm/"

3
debian/watch vendored Normal file
View file

@ -0,0 +1,3 @@
version=4
opts="uversionmangle=s/-rc/~rc/" \
https://www.kernel.org/pub/linux/utils/raid/mdadm/mdadm-([.[:digit:]]+(?:-rc[[:digit:]]+)?).tar.gz