![]() | ||||||||||
Messages in this thread |
I've just added a 1.9 TB array to one of my servers (running 2.4.20, the device is an 12bay-IFT IDE-to-Fibre-RAID connected via a Qlogic 2300 HBA): Disk /dev/sdb: 255 heads, 63 sectors, 247422 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 247422 1987417183+ 83 Linux [...] Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0 SCSI device sdb: -320126976 512-byte hdwr sectors (-163904 MB) sdb: sdb1 Another array (1.2 TB) gives almost the same effect: Disk /dev/sdb: 255 heads, 63 sectors, 157450 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 157450 1264717093+ 83 Linux [...] Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0 SCSI device sdb: -1765523456 512-byte hdwr sectors (195564 MB) sdb: sdb1 These issues arise when using arrays larger than around 0.5 T; nevertheless, these devices do work fine with both xfs or ext3, it's "just" a cosmetical issue. However, this negative values make one feel like Linux isn't truely capable of using up to 2 TB of disk devices and so this should be resolved. To me it seems that sd.c doesn't know how to calculate the correct values for such beasts - any ideas? Regards Anders -- http://sysiphus.de/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 11:31 [W:1.610 / U:0.580 seconds] ©2003-2008 Jasper Spaans | ||||||||||