Bug 2998 - (sata sii) file system failures on sata drive
Summary: (sata sii) file system failures on sata drive
Status: RESOLVED DUPLICATE of bug 6845
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-01 13:06 UTC by Sean Middleditch
Modified: 2007-09-02 09:50 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.7-bk9
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Sean Middleditch 2004-07-01 13:06:41 UTC
Distribution: Fedora Devel
Hardware Environment: Athlon XP 1800+
Software Environment: kernel 2.6.7-bk9
Problem Description:

I have a Seagate sata drive on a Silicon Image 3112 controller.  The problem I'm
having doesn't seem to be the usual problem with this combination though, as
shown below.

Basically, I can partition the driver and make file systems on those partitions
just fine.  As soon as I try to create some files or folders I start getting I/O
errors and file system errors in dmesg.  No hardware errors are being reported
anywhere that I can tell.

I do not have any other serial ata drivers or controllers around to test if this
is a case of broken hardware.  Any suggestions on how to debug this further will
be greatly appreciated.

SATA Controller (Silicon Image 3112):
00:0a.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology Inc)
SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)

Hard-disk:
Seagate 3160023AL

I modified the sata_sil driver to put the above seagate model in the blacklist.
 The error logs below report that this worked as the Seagate error message is
displayed.  Didn't obviously help any, though.

[root@stargrazer mnt]# uname -a
Linux stargrazer 2.6.7-1.459 #1 Mon Jun 28 16:20:56 EDT 2004 i686 athlon i386
GNU/Linux


Created XFS partision, then mounted:
[root@stargrazer extra]# touch test
touch: cannot touch `test': Unknown error 990

Created ext3 partition, then mounted:
[root@stargrazer extra]# touch test
touch: cannot touch `test': Input/output error

Errors from dmesg from the XFS error above:

SCSI subsystem initialized
libata version 1.02 loaded.
sata_sil version 0.54
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
ata1: SATA max UDMA/100 cmd 0x22840080 ctl 0x2284008A bmdma 0x22840000 irq 11
ata2: SATA max UDMA/100 cmd 0x228400C0 ctl 0x228400CA bmdma 0x22840008 irq 11
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
ata1(0): applying Seagate errata fix
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: ST3160023AS       Rev: 3.18
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
 sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
XFS mounting filesystem sda1
Ending clean XFS mount for filesystem: sda1
Filesystem "sda1": XFS internal error xfs_btree_check_sblock at line 342 of file
fs/xfs/xfs_btree.c.  Caller 0x229dae6b
 [<229c678b>] xfs_btree_check_sblock+0x9b/0xa9 [xfs]
 [<229dae6b>] xfs_inobt_lookup+0x10b/0x31e [xfs]
 [<229dae6b>] xfs_inobt_lookup+0x10b/0x31e [xfs]
 [<229f9a1e>] kmem_zone_alloc+0x3b/0x70 [xfs]
 [<229d8e3d>] xfs_dialloc+0x2dc/0x8d0 [xfs]
 [<0212da19>] buffered_rmqueue+0x11c/0x144
 [<0212dadd>] __alloc_pages+0x9c/0x27b
 [<229de8bc>] xfs_ialloc+0x47/0x3ef [xfs]
 [<229f1986>] xfs_dir_ialloc+0x71/0x22b [xfs]
 [<229e48e6>] xfs_log_reserve+0x79/0x80 [xfs]
 [<229ef702>] xfs_trans_reserve+0xae/0x173 [xfs]
 [<229f5eea>] xfs_create+0x2f2/0x556 [xfs]
 [<229ad440>] xfs_acl_get_attr+0x39/0x5a [xfs]
 [<229fe8e3>] linvfs_mknod+0x1a1/0x2ef [xfs]
 [<0212b0f4>] do_generic_mapping_read+0x2e4/0x2ec
 [<229cbc36>] xfs_dir2_lookup+0x80/0xf4 [xfs]
 [<0212da19>] buffered_rmqueue+0x11c/0x144
 [<22849a7e>] do_get_write_access+0x405/0x421 [jbd]
 [<229fea38>] linvfs_create+0x7/0x9 [xfs]
 [<0214b37c>] vfs_create+0xb8/0xef
 [<0214b736>] open_namei+0x16a/0x426
 [<02140146>] filp_open+0x23/0x3c
 [<021403e6>] sys_open+0x31/0x7d
[root@stargrazer extra]#

Errors from dmesg from ext3 from above:

kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs error (device sda1): ext3_new_inode: reserved inode or inode > inodes
count - block_group = 0, inode=5
Aborting journal on device sda1.
EXT3-fs error (device sda1) in ext3_new_inode: IO failure
EXT3-fs error (device sda1) in ext3_create: IO failure
Comment 1 Andrew Morton 2007-08-07 16:44:14 UTC
Are these problems still present in recent kernels?

Thanks.
Comment 2 Sean Middleditch 2007-08-07 21:18:34 UTC
I replaced that hardware a long time ago, and I don't have it to test anymore.  Sorry.
Comment 3 Tejun Heo 2007-08-07 21:56:36 UTC
Yeah, this problem is present.  I'm following this up in bug 6845 but running out of ideas.
Comment 4 Tejun Heo 2007-08-07 21:57:32 UTC
Jeff, can you mark this a duplicate of 6845?
Comment 5 Adrian Bunk 2007-09-02 09:50:43 UTC

*** This bug has been marked as a duplicate of bug 6845 ***

Note You need to log in before you can comment on or make changes to this bug.