From: "D. Stussy" <spam+newsgroups@bde-arc.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Possible logic bug in either EXT4 FS or SATA driver.
Date: Mon, 19 Dec 2011 12:24:54 -0800 [thread overview]
Message-ID: <jco6iq$1dp$1@snarked.org> (raw)
Syslog:
kernel: ata1: illegal qc_active transition (3fffffff->fffffffe)
When this happens, the filesystem on the offending disk is auto-remounted
as read-only. Is this an indication of a bug in the ext4 filesystem or in
the SATA driver?
I am seeing this bug with a 3.1.5 kernel compiled from source about every
3-4 days. Soft rebooting does not work; a hard reset is required.
System: AMD Opteron 4184 stepping 01 (6-core) 2.8GHz (2794.027 MHz) 64-bit
MB: Supermicro H8SCM-F / 32GB ECC Ram
HD: ATA-8: ST32000644NS, SN11, max UDMA/133
3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32)
(1.81 TB) SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Write Protect is off / Mode Sense: 00 3a 00 00
Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
EXT4: Basic filesystem, no extended attributes nor using driver for
ext2/3.
reply other threads:[~2011-12-19 20:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jco6iq$1dp$1@snarked.org' \
--to=spam+newsgroups@bde-arc.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=replies+newsgroups@kd6lvw.ampr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).