Heiko Wundram schrieb: > You cannot manage disks >= ~2TB with fdisk (i.e., DOS partition tables), as > they (or rather the on-disk-structure of DOS partition tables) have an > inherent limitation in the maximum number of LBA48-blocks they can address. > > I'd presume that because of this inherent limitation, fdisk is reporting the > wrong total size (2TB+774G+epsilon ~ 3TB; sounds like somewhere someone is > doing a modulo operation, possibly), and completely "off" values for > heads/sectors. > > Anyway, md-devices cannot be partitioned anyway (of course you can write a > partition table on them, but the kernel won't use that to create md2-1,-2, > etc.), so using fdisk is wrong. > > If you want to check the "real" size of the device, don't use fdisk, but > rather use > > blockdev --getsize64 /dev/md2 > > which shows you the byte-count of the corresponding volume, and which I think > will be 3TB, as you want it to be.
Nope, it did show the same 774 GB. > If you want to subpartition large devices, use lvm(2), which does not have > the > 2TB limitation on size. > > Hope this helps! Thanks for your explanations and suggestions ... but ... I just now received a reply to my posting on the german list, the mistake was that CONFIG_LBD was not set in my kernel. Now I get: # blockdev --getsize64 /dev/md2 2973068230656 # fdisk -l Platte /dev/md2: 2973.0 GByte, 2973068230656 Byte Thanks anyway! Stefan
