| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Update the testing scripts to allow for new space calculations
for space for bitmaps.
Add a test script for adding devices to linear arrays.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new superblock needs to have a new disk.number. This is a bit of a hack...
Fix handling of negative bitmap offsets on 64bit hosts.
The bitmap offset is a signed 32bit number, so casting to (long)
isn't sufficient. We must cast to (int32_t).
Fix various problems with --grow --add for linear.
The code to add a drive to a live linear array had never
been tested properly and so was buggy. This tidies it up
and means that the new regression-test passes.
|
|
|
|
|
| |
The bitmap offset is a signed 32bit number, so casting to (long)
isn't sufficient. We must cast to (int32_t).
|
|
|
|
|
| |
This if you unplug a device and udev removes the entry from /dev,
you can still remove the device.
|
|
|
|
| |
From: David Huffman <dhuffman@storix.com>
|
|
|
|
|
|
|
|
| |
udev likes to get information about a device as key=value pairs so it
can create disk/by-id links etc. So add --export flag which causes
the output of --detail to easily parsable.
From: Kay Sievers <kay.sievers@novell.com>
|
|
|
|
|
|
|
| |
We have the same calculation in multiple places with subtle differences.
So unite it all.
Also fix up and endian problem in --examine.
|
|
|
|
| |
This helps with piping to a pager for example.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From: Peter Samuelson <peter@p12n.org>
nroff formats "-" as the very short hyphen used for hyphenated terms
and for splitting a word across two lines. When you want a literal
ASCII "-", like for typing on a command line, you're supposed to use
"\-" instead.
Yeah, it sounds pedantic, but it actually makes a difference. With
modern Unicode-capable terminals, "man" actually renders these with
different characters, so if you try to search for "--create" in your
favorite pager, you won't find it unless the nroff source says
"\-\-create". This discrepancy doesn't generally show up with
non-Unicode terminals.
Signed-Off-By: Peter Samuelson <peter@p12n.org>
|
|
|
|
|
|
|
|
|
| |
From: Peter Samuelson <peter@p12n.org>
Option names and example command lines seem to be boldface most of the
time, fix up the few that weren't.
Signed-Off-By: Peter Samuelson <peter@p12n.org>
|
|
|
|
|
|
|
|
|
| |
From: Peter Samuelson <peter@p12n.org>
\(em renders as "--" in ASCII, and a nice em dash (i.e., a dash the
width of the letter "m") in more capable formats like PostScript.
Signed-Off-By: Peter Samuelson <peter@p12n.org>
|
|
|
|
|
|
|
|
|
| |
From: Peter Samuelson <peter@p12n.org>
do not hyphenate terms:
"override", "therein", "overwrite", "superblock format".
Signed-Off-By: Peter Samuelson <peter@p12n.org>
|
| |
|
|
|
|
|
| |
If nether ftw nor nftw are available, add_dev gets defined twice.
Fix that...
|
| |
|
|
|
|
|
| |
As I cannot compile in on x86-64.
Also, small dietlibc fix
|
| |
|
| |
|
|
|
|
|
| |
This allows mdadm to correctly restart a raid6 grow that
crashed during the critcal phase.
|
|
|
|
|
| |
The case that doesn't initialise it is impossible,
so just return with an error..
|
| |
|
| |
|
|
|
|
|
| |
--incremental allows arrays to be assembled one device at a time.
This is expected to be used with udev.
|
|
|
|
| |
Rather than opencoding the byteswap all the time.
|
| |
|
|
|
|
| |
Only happens on kernel with 32 bit sector_t.
|
|
|
|
| |
Instead of opencoding the same thing everywhere.
|
|
|
|
| |
map_dev can be slow and interferes with trying to stop the array.
|
|
|
|
| |
This improves quality of error message.
|
|
|
|
|
|
| |
If two drives in a raid5 disappear at the same time, then "-Af"
will add them both in rather than just one and forcing the array
to 'clean'. This is slightly safer in some cases.
|
|
|
|
| |
A number of odd bugs here, but now we have a regression test as well.
|
|
|
|
|
| |
This doesn't get mailed out, but will appear in syslog...
Maybe it should be mailed if it was a 'check' or 'repair' pass...
|
| |
|
|
|
|
|
| |
because it only shows how much of each device is actually used, not
how big they are.
|
|
|
|
|
| |
The setting used unfortunately requires intimate knowledge of the
kernel, and it not reset when the reshape finishes.
|
|
|
|
| |
and is also degraded.
|
|
|
|
|
| |
so the array devices with 'standard' names
get created automatically, as this is almost always what is wanted.
|
| |
|
|
|
|
| |
size.
|
|
|
|
|
|
|
|
|
|
| |
Depending on the size of the array we reserve space for up to 128K
of bitmap, and we use it where possible.
When hot-adding to a version 1.0 we can still only use the 3K at the
end though - need a sysfs interface to improve that.
If a small chunksize is requested on Create, we don't auto-enlarge
the reserved space - this still needs to be fixed.
|
|
|
|
|
|
|
| |
Fixes-debian-bug: 402457 (part)
All the code is there, and it works for '-y', but for some reason,
"syslog" was missing from the long_options.
|
|
|
|
|
| |
This stuff has never been used (at least as far as git history can
see). I wonder why it was there...
|
|
|
|
|
|
| |
Previously it onl worked when one missing device.
Also split the "force" update_super method into two and it
is really serving two functions.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
If an auto-assembly attempt failes because the array cannot be
opened or because the array has already been created, then we
get into an infinite loop.
Reported-by: Dan Pascu <dan@ag-projects.com>
Fixes-debian-bug: 396582
|
|
|
|
|
|
|
|
|
| |
From: Goswin Brederlow <brederlo@informatik.uni-tuebingen.de>
This is already mentioned in the config documentation, but not in the
place when the normal default is mentioned.
Fixes-debian-bug: 396914
|
|
|
|
| |
Otherwise we quickly lose it...
|