On 6/28/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
sata_inic162x can't do LBA48 properly yet. Whine loudly about it to reduce confusion.Signed-off-by: Tejun Heo <[EMAIL PROTECTED]> --- drivers/ata/sata_inic162x.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) Index: work/drivers/ata/sata_inic162x.c =================================================================== --- work.orig/drivers/ata/sata_inic162x.c +++ work/drivers/ata/sata_inic162x.c @@ -664,8 +664,12 @@ static int inic_init_one(struct pci_dev void __iomem * const *iomap; int i, rc; - if (!printed_version++) + if (!printed_version++) { dev_printk(KERN_DEBUG, &pdev->dev, "version " DRV_VERSION "\n"); + printk(KERN_WARNING "WARNING: sata_inic162x doesn't support " + "LBA48 yet. Devices larger than\n " + "2^28 - 1 sectors (~127GiB) won't work.\n"); + } /* alloc host */ host = ata_host_alloc_pinfo(&pdev->dev, ppi, NR_PORTS); -
Does it simply fail? Or does it corrupt? In my Windows experience, if you try to write data past ~128GiB and you don't have LBA48 support you get a wraparound effect that causes corruption of the data below ~128GiB. I've seen it happen several times under Win2K in particular. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
