Hi,
Guido Villa wrote:
Hello,
I have an error as described in subject.
I couldn't find a previous report for this kind of error, so maybe you are interested in it.
Motherboard: ASUS TUV4X, BIOS rev. 1005
SATA controller: Silicon Image 3112A, bios rev. 4.2.50
Hard disk: Maxtor Maxtor 6B300S0 (300GB, SATA)
This is the only HDD attached to the controller. It is not the boot device, I have other HDDs on the IDE channels, but I don't think it matters.
I happen to have a SiI 3112A controller and a Maxtor 6B300S0 attached to it, formatted with ext2. Never had any problems. I just copied 200GB of data to it, worked flawlessly. (Vanilla 2.6.11) Maybe its the Motherboard?
Kernels: 2.6.9, 2.6.10, 2.6.11.2
I also patched the 2.6.11.2 by adding this Maxtor disk to the sata_sil.c blacklist (once with the SIL_QUIRK_MOD15WRITE and once with the SIL_QUIRK_UDMA5MAX), but the behaviour did not change.
Problem:
I create a single partition on the hard disk, I format it with ext2, I mount it, I begin writing onto the partition. After seconds (or minutes) of copying, I get this error:
EXT2-fs error (device sda1): ext2_new_block: Allocating block in system zone - block = 22413316
I have also tried with ext3, in this case it prints more error messages:
EXT3-fs error (device sda1): ext3_new_block: Allocating block in system zone - block = 61997060
Aborting journal on device sda1.
EXT3-fs error (device sda1) in ext3_prepare_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sda1) in start_transaction: Journal has aborted
-- Manuel Lauss - 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/
