On Tue, Mar 08, 2016 at 10:20:17PM -0500, Dan Russell wrote:
> The partially-rebuilt drive is sdk, the original “failed” drive is sdag
Best to leave both out if one has outdated and the other only half
the content...
> However fdisk and mdadm are reporting the array is 17.6TB in size, whereas it should be 66TB (24 3TB HDDs RAID6).
I reproduced your commands using tmpfs based loop devices and it gives me
the same problem. The RAID size is only 16 TiB. It seems to be hitting a
limit somewhere.
Your /dev/mapper/sdx are snapshot/overlays, I hope?
DDF metadata seems to be located at the end of the device, so you could try
your luck with mdadm 1.0 metadata instead; that gives me a RAID of a size
closer to home.
# mdadm --create /dev/md42 --assume-clean --metadata=1.0 --level=6 --raid-devices=24 --chunk=64 /dev/loop{0..23}
# fdisk -l /dev/md42
Disk /dev/md42: 60 TiB, 65999996846080 bytes, 128906243840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 1441792 bytes
It wastes some sectors at the end though, not sure if more or less
than what DDF uses for metadata. You might have to add some empty
space to your device mappings to get a full view.
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
