Re: mdadm recovery after HW failure: missing blocks at the end

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all!

For the record:

Am 01.11.2012 um 22:03 schrieb Sebastian Hegler:
> * Did mdadm (or the kernel md driver) write to the end area of the disk?
Apparently no.

> * Is it possible to make mdadm give me back the 128kiB at the end of each device?
Yes:
diff --git a/super1.c b/super1.c
index 5bb1f01..4824aa3 100644
--- a/super1.c
+++ b/super1.c
@@ -1723,8 +1723,8 @@ static __u64 _avail_size1(struct supertype *st, __u64 devs
        /* Allow space for bad block log */
        if (super && super->bblog_size)
                devsize -= __le16_to_cpu(super->bblog_size);
-       else
-               devsize -= 8;
 
 
        if (st->minor_version < 0)



Yours,
Sebastian

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux