Re: LibPATA code issues / 2.6.16 (previously, 2.6.15.x)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[4597362.011000] ata3: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[4597362.011000] ata3: status=0x51 { DriveReady SeekComplete Error }
[4597362.011000] ata3: error=0x04 { DriveStatusError }

Now under 2.6.16.20. (was doing an rsync from 1 drive (IDE) -> to this SATA) drive.

The SATA drive AFAIK does not have any issues, no bad sectors/etc, still the same drive as before, but this is the new one from the previous RMA.

Just FYI.


On Fri, 21 Apr 2006, Linus Torvalds wrote:



On Fri, 21 Apr 2006, Jeff Garzik wrote:


Agreed, though the original poster had already done a 400GB dd from
/dev/zero...

Yes, but to a _file_ on the partition (ie he didn't overwrite any existign
data, just the empty parts of a filesystem).

I realize that it's not enough for the "re-allocate on write" behaviour,
and for that you really _do_ need to re-write the whole disk to get all
the broken blocks reallocated, but my argument was just that we should
make sure to _tell_ people when they are overwriting all their old data ;)

		Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux