Hi Alex, On 01/05/2018 05:10 AM, Alexander Shenkin wrote: > On 1/5/2018 5:25 AM, Brad Campbell wrote: >> I'm going to go and write a letter of apology to my primary school >> maths teacher now. > Thanks much, Brad. fdisk & parted output are below. I have swap space > mounted on /dev/sda4, 15,984,640 sectors long, after the partitions used > for raid. I'm not sure where exactly the parity data sits... Looks to > me like this happened in swap space, no? Currently, swapon reports > 552,272 kb (= 1,104,544 sectors) in use (i think). If that's > contiguous, then the write should have happened after the used space > (13,297,904 > 1,104,544). But I'm not sure swap is contiguous. In this > case, regardless, I suspect I should just reboot, and then run > checkarray to be safe? The output of fdisk is invalid on your system, see the warning it printed. Use gdisk or parted instead. Don't use '*'. > One followup: is parity info stored in a separate area than data info on > the disk? If the write *had* fallen within the raid partition area, > would you indeed be able to tell if it overwrote data vs parity vs both? > Google wouldn't tell me... No. Parity is interleaved with data on all devices, chunk by chunk, on all default raid5/6 layouts. In raid4, the last device is all of the parity. There are optional layouts for raid5 that do the same, and variants for raid6 that place various combinations of parity and syndrome at either end. See the --layout option in the mdadm man page. The non-data area of member devices contains at least the superblock, and optionally a write-intent bitmap and/or a bad-block list. Most of the non-data space is reserved for optimizing future --grow operations. > user@machinename:~$ sudo fdisk -l /dev/sda* > > WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util > fdisk doesn't support GPT. Use GNU Parted. All of the partition data following this warning is bogus -- it is the "protective" MBR record. Phil -- 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
