From: Robert Hancock <hancockr@shaw.ca>
To: Fred Moyer <fred@redhotpenguin.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.21.1] SATA freeze
Date: Sat, 12 May 2007 19:02:38 -0600 [thread overview]
Message-ID: <464663AE.6040409@shaw.ca> (raw)
In-Reply-To: <464610F7.6030202@redhotpenguin.com>
Fred Moyer wrote:
>> This appears to be a different problem. Something is issuing
>> SMART-related commands (smartd or smartctl perhaps) which the drive
>> seems to be reacting strangely to. It apparently completed the command
>> but never raised DRQ to request any data being transferred even though
>> we expected it to. Maybe SMART is disabled on the drive and that's
>> causing it to just toss these commands? CCing linux-ide in case anyone
>> knows what would cause this.
>
> Here's smartctl -a for this drive - same output for both sda and sdb.
> Smartd is currently running. Any advice appreciated.
>
> Previously on 2.6.15 I was seeing sdb remount as readonly under heavy
> i/o. I have not seen that issue yet with 2.6.21 (with Robert's patch
> from May 5th for sata_nv), but that occurrence of remounts read-only was
> infrequently, so that issue may be solved.
>
> app2 ~ # smartctl -a /dev/sda
> smartctl version 5.36 [x86_64-pc-linux-gnu] Copyright (C) 2002-6 Bruce
> Allen
> Home page is http://smartmontools.sourceforge.net/
>
> Device: ATA ST3808110AS Version: n/a
> Serial number: 5LR8895K
> Device type: disk
> Local Time is: Sat May 12 12:05:58 2007 PDT
> Device does not support SMART
>
> Error Counter logging not supported
>
> [GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
> Device does not support Self Test logging
>
Sounds like SMART is likely disabled on that drive. You can try doing
"smartctl -s on /dev/sda" and see if that will turn it on.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-05-13 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zU1kuoSgByTYCYqY+iCQ5rMJy34@ifi.uio.no>
2007-05-12 18:48 ` [2.6.21.1] SATA freeze Robert Hancock
2007-05-12 19:09 ` Fred Moyer
2007-05-13 1:02 ` Robert Hancock [this message]
2007-05-13 1:52 ` Fred Moyer
2007-05-13 1:20 ` Robin H. Johnson
2007-05-13 18:18 ` Jim Paris
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=464663AE.6040409@shaw.ca \
--to=hancockr@shaw.ca \
--cc=fred@redhotpenguin.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).