Re: Recover array after I panicked

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

 



On Mon, Apr 24, 2017 at 02:54:50PM +0200, Patrik Dahlström wrote:
> What offset are you referring to here? The --data-offset to the mdadm
> --create command?

Yes, data offset...

> I don't think the disk was ever kicked out. The kernel reset the link
> and continued, I believe.

Okay.

Another thing you can check is, pick an arbitrary offset that does not 
have zeroes on the disks, and see if the XOR matches for 5, or 6 disks.

It should match for 6 for however far the grow progressed, 
and match for 5 afterwards.

Again with my example from before,

# for hexdump -C -n 16 -s 10000000 "$f"
00989680  30 30 30 30 30 30 30 30  32 61 38 39 36 38 30 0a  |000000002a89680.|
00989690                                                             ^^
00989680  30 30 30 30 30 30 30 30  32 61 38 39 36 38 30 0a  |000000002a89680.|
00989690                                                             ^^
00989680  30 30 30 30 30 30 30 30  32 62 30 39 36 38 30 0a  |000000002b09680.|
00989690                                                             ^^
00989680  30 30 30 30 30 30 30 30  32 62 38 39 36 38 30 0a  |000000002b89680.|
00989690                                                             ^^
00989680  30 30 30 30 30 30 30 30  32 63 30 39 36 38 30 0a  |000000002c09680.|
00989690                                                             ^^ 
00989680  30 30 30 30 30 30 30 30  32 63 38 39 36 38 30 0a  |000000002c89680.|
00989690                                                             ^^

2a ^ 2a ^ 2b ^ 2b ^ 2c = 2c OK for 6 disk area

# for hexdump -C -n 16 -s 90000000 "$f"
055d4a80  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
055d4a90                                                              ^^
055d4a80  30 30 30 30 30 30 30 31  35 32 35 34 61 38 30 0a  |000000015254a80.|
055d4a90                                                              ^^
055d4a80  30 30 30 30 30 30 30 31  35 32 64 34 61 38 30 0a  |0000000152d4a80.|
055d4a90                                                              ^^
055d4a80  30 30 30 30 30 30 30 31  35 33 35 34 61 38 30 0a  |000000015354a80.|
055d4a90                                                              ^^ 
055d4a80  30 30 30 30 30 30 30 31  35 33 64 34 61 38 30 0a  |0000000153d4a80.|
055d4a90                                                              ^^

25 ^ 2d ^ 35 ^ 3d = \0\0 OK for 5 disk area

(I did not intend for the parity to be zero in this example, 
 but that's just how it turned out to be...)

If you have a 5disk parity match in the zone that should be 6disks, 
then maybe one of your earlier mdadm create experiments started to 
sync the raid.

This would be yet another nail in your coffin.

Regards
Andreas Klauer
--
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