From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Huge problem with XFS/iCH7R
Date: Mon, 03 Jul 2006 17:20:11 -0400 [thread overview]
Message-ID: <44A98A0B.8080203@tmr.com> (raw)
In-Reply-To: <20060703163216.B1474487@wobbly.melbourne.sgi.com>
Nathan Scott wrote:
> On Sun, Jul 02, 2006 at 09:51:45PM +0200, Carsten Otto wrote:
>> Hi there!
>>
>> (System specs below)
>>
>> Short summary:
>> System (with software raid 5, XFS, four disks connected to AHCI
>> controller) crashes very often and loses data.
>>
>> My system crashes every few days, at the moment daily. The message shown
>> is (the drive changes about every time, I do not see a pattern here):
>> ---
>> ata4: handling error/timeout
>> ata4: port reset, p_is 0 is 0 pis 0 cmd c017 tf 7f ss 0 se 0
>> ata4: status=0x50 { DriveReady SeekComplete }
>> sdd: Current: sense key=0x0
>> ASC=0x0 ASCQ=0x0
>> Info fid=0x0
>
> FWIW, the above look like hardware/driver problems.
If the problem doesn't occur before 2.6.16, that makes a hardware
problem less likely. It's not impossible that some buggy feature is now
used, but lower probability than the kernel change being the culprit.
The bug fix you mention may solve the whole thing, or make it easier to
debug.
General comment: if a kernel version made my system crash once a day I
sure wouldn't be using it. New features are neat, but I wouldn't put up
with that if it made my cat pee holy water.
I would test proposed fixes, of course, but only until I got more info
for developers.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-07-03 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 19:51 Huge problem with XFS/iCH7R Carsten Otto
2006-07-02 19:56 ` Carsten Otto
2006-07-02 21:22 ` Jan Engelhardt
2006-07-03 6:32 ` Nathan Scott
2006-07-03 21:20 ` Bill Davidsen [this message]
2006-07-03 22:47 ` Nathan Scott
2006-07-05 12:29 ` Bill Davidsen
2006-07-16 8:45 ` Carsten Otto
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=44A98A0B.8080203@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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