| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
--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...
|
| |
|
|
|
|
|
| |
Similar to -Esv, this combination should print out the
'devices=' line in the otherwise --breif output.
|
|
|
|
| |
From: "Michael Labuschke" <michael@labuschke.de>
|
|
|
|
| |
--getsize64 seems to have disappeared.
|
| |
|
|
|
|
|
| |
It can be increased further, but that takes a bit more code
so will wait for 2.6.
|
|
|
|
|
| |
Need to mask of bits above the bottom 16 when calculating number of
copies.
|
|
|
|
|
| |
->name is sized to '33' to have room for a trailing nul,
but thhat needs to get put in position '32'. Doh!
|
|
|
|
|
|
|
| |
From: Luca Berra <bluca@comedia.it>
Put another way, if we find any active arrays, then assume things are
going as planned.
|
|
|
|
|
|
| |
From: Luca Berra <bluca@comedia.it>
There is no need and it causes occasional problems.
|
|
|
|
|
|
|
|
|
| |
From: Luca Berra <bluca@comedia.it>
- Fix a bug where mdassemble didn't close a filedescriptor and so couldn't assembele
stacked arrays.
- Allow mdassemble, when run a second time, to mark all arrays as writable.
This is useful if they are started read-only as is best at boot-time.
|
|
|
|
| |
To ensure kernel never needs to allocate more than 1 page contiguously.
|
|
|
|
|
| |
Otheriwse the last write happens on fclose which is after ftruncate,
to the truncate has no effect.
|
|
|
|
| |
Just include the content directly. It is safer.
|
| |
|
|
|
|
| |
They do nothing but cause confusion.
|
|
|
|
|
|
| |
So if the device name is /dev/md/d0, then the number of
partitions is as given. This is useful in 'CREATE' in
mdadm.conf
|
|
|
|
|
|
|
|
| |
If they are for a partition and a whole device (common case)
they old message doesn't really cover the situation. So add
the "overlap" option to the text.
Also detect whether the device list was in mdadm.conf and
act accordingly.
|
|
|
|
| |
.. in man page
|
|
|
|
| |
Thanks Martin Krafft
|
|
|
|
| |
From: Paul Clements <paul.clements@steeleye.com>
|
| |
|