Just off the cuff, I can't see it being likely an Ext3 problem -- as
long as the driver is passing along the proper device size ext3
shouldn't have any problems -- However, if you have any questions
about that, you should explicitly pass mkfs (or mkfs.ext[23] an
explicit size parameter).
( in that respect, I'd be more interested in seeing /proc/partitions
than /proc/interrupts).
check to see if you can do a raw write of the entire device (dd
if=/dev/zero of=/dev/hda bs=10k). It's about as simple as you can
get, and it chould tell you more about the style of te problem.
On 4/23/07, Kieft, Brian <bkieft@xxxxxxxxx> wrote:
I'm currently running an embedded linux system (arm) with a CF card
mounted as EXT3. I'll copy some system details below… Anyway, I'm getting
some drive errors and I'm wondering if they're due to bad/old drivers,
something with EXT3 and CF latency, or something else entirely.
hda: write_intr error1: nr_sectors=1, stat=0x51
hda: write_intr: status=0x51 { DriveReady SeekComplete Error }
hda: write_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:01 (hda), sector 528431
--
Stephen Samuel http://www.bcgreen.com
778-861-7641
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
