IDE corruption w/ 48 Bit addressing
Hi,
i'm having a PPC-405 based board (IBM STB04500 if anyone cares), and i'm using a Maxtor 6Y200L0, a 200GB harddisk drive.
Obviously this uses 48bit addressing, and i'm using linucppc 2.4.21-pre4 devel. The same bug occurs with 2.4.20 release.
Users report harddisk corruption, and a quick test showed, that data written to 0x1800000000+x (LBA sector 0xC000000+x/512) is also written to x. (direct O_LARGEFILE-access to /dev/discs0/disc).
This will of course corrupt the filesystem.
Now my questions:
- is this a bug in the IDE low-level interface driver?
- or maybe in the kernel?
- or maybe fixed in newer versions?
- why does the corruption start at this lba sector?
User reported that this occurs with different HDD models and brands, too, but only with 48bit-drives. Everything else works perfectly.
felix
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 4 lines
Users report harddisk corruption, and a quick test showed, that data written to 0x1800000000+x (LBA sector 0xC000000+x/512) is also written to x. (direct O_LARGEFILE-access to
/dev/discs0/disc).
OK, update, this was a bit misleading:
when reading from the device, the upper 3 bytes aren't updated in the right way, so the "previous content" (as specified in the ATA/6 specs) seem to be invalid and contain, well, wrong content.
felix
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 8 lines · Felix Domke
Hi,
i'm having a PPC-405 based board (IBM STB04500 if anyone cares), and i'm using a Maxtor 6Y200L0, a 200GB harddisk drive.
Obviously this uses 48bit addressing, and i'm using linucppc 2.4.21-pre4 devel. The same bug occurs with 2.4.20 release.
So far as I know the IBM Redwood-5 (STB04xxx) has an ATAPI-5 controller onboard, which would not support 48-bit addressing and would support a max of 137GB. But if you're using an ATA/6 controller then nevermind...
--
Todd
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/