Turns out my raid volume's size according to the metadata on disk IS an
even multiple of the stripe factor, so it looks like this is a bug in
dmraid, and I have taken the issue to the ataraid mailing list.
Heinz Mauelshagen wrote:
On Thu, Oct 12, 2006 at 02:59:45PM +0100, Alasdair G Kergon wrote:
On Thu, Oct 12, 2006 at 12:01:21AM -0400, Phillip Susi wrote:
now dmraid fails to configure the dm
table because this patch rejects it.
I believe the correct thing to do is to special case the last stripe in
0-31 64-67
32-63 68-71
AFAIK current versions of dmraid handle this correctly - Heinz?
Yes, that's correct.
Alasdair
--
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
