Yep, it's in swap. Check the sector you wrote against the sector ranges listed in the parted print. All good to go. > On 5 Jan 2018, at 6:10 PM, Alexander Shenkin <al@xxxxxxxxxxx> wrote: > >> On 1/5/2018 5:25 AM, Brad Campbell wrote: >>> On 05/01/18 13:20, Brad Campbell wrote: >>> You re-wrote Sectors 5857843312+7 on the disk. >>> Add those two and we get 5844545408 sectors. So if my maths is any good >>> you wrote a block 13297904 sectors from the end of the data area. >> I can't believe I did that. No, you wrote a block ~6M *after* the data area and you should be fine. >> 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? > > 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... > > Thanks again, > Allie > > > 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. > > > Disk /dev/sda: 3000.6 GB, 3000592982016 bytes > 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk identifier: 0x00000000 > > Device Boot Start End Blocks Id System > /dev/sda1 1 4294967295 2147483647+ ee GPT > Partition 1 does not start on physical sector boundary. > > Disk /dev/sda1: 1998 MB, 1998585856 bytes > 255 heads, 63 sectors/track, 242 cylinders, total 3903488 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk identifier: 0x00000000 > > Disk /dev/sda1 doesn't contain a valid partition table > > Disk /dev/sda2: 1 MB, 1048576 bytes > 255 heads, 63 sectors/track, 0 cylinders, total 2048 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk identifier: 0x00000000 > > Disk /dev/sda2 doesn't contain a valid partition table > > Disk /dev/sda3: 2990.4 GB, 2990407680000 bytes > 255 heads, 63 sectors/track, 363563 cylinders, total 5840640000 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk identifier: 0x00000000 > > Disk /dev/sda3 doesn't contain a valid partition table > > Disk /dev/sda4: 8184 MB, 8184135680 bytes > 255 heads, 63 sectors/track, 994 cylinders, total 15984640 sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 4096 bytes > I/O size (minimum/optimal): 4096 bytes / 4096 bytes > Disk identifier: 0x00000000 > > Disk /dev/sda4 doesn't contain a valid partition table > > > > > > user@machinename:~$ sudo parted /dev/sda 'unit s print' > Model: ATA ST3000DM001-9YN1 (scsi) > Disk /dev/sda: 5860533168s > Sector size (logical/physical): 512B/4096B > Partition Table: gpt > > Number Start End Size File system Name Flags > 1 2048s 3905535s 3903488s boot raid > 2 3905536s 3907583s 2048s grubbios bios_grub > 3 3907584s 5844547583s 5840640000s ext4 main raid > 4 5844547584s 5860532223s 15984640s linux-swap(v1) swap > > > user@machinename:~$ swapon --summary > Filename Type Size Used Priority > /dev/sda4 partition 7992316 552272 -1 > /dev/sdb4 partition 7992316 0 -2 > /dev/sdc4 partition 7992316 0 -3 > > -- 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
