frantisek holop wrote: > hmm, on Wed, Apr 01, 2009 at 05:05:10AM +0200, frantisek holop said that >> i wonder what will happen when 65536/255/63 is reached, >> what kind of frankenstein translation table will come into life >> just to save c/h/s again. maybe there will come an LBA only age, >> i mean fdisk-wise, not disk-wise, those are already LBA only... > > openbsd could be the first one to nuke c/h/s from the MBR > entirely, replace it with 8 or 16 byte LBA values (4 bytes > currently) and lead the way for terribly huge disks :] > > -f
old news. 65536*255*63*512 539,051,950,080 bytes (the marketing people would probably call that a 640G or 750G disk :) And here is a 1T-ish system I've got running (which I mistakenly called a 1.5T system on a prev. post, I think). fdisk: 1> p Disk: wd0 geometry: 1938037/16/63 [1953542144 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start: size ] ------------------------------------------------------------------------------- 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 1 1 - 1938036 15 63 [ 63: 1953541233 ] OpenBSD fdisk: 1> p g Disk: wd0 geometry: 1938037/16/63 [932 Gigabytes] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start: size ] ------------------------------------------------------------------------------- 0: 00 0 0 0 - 0 0 0 [ 0: 0G] unused 1: 00 0 0 0 - 0 0 0 [ 0: 0G] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0G] unused *3: A6 0 1 1 - 1938036 15 63 [ 63: 932G] OpenBSD These "problems" just aren't problems. Nick.