From: Tejun Heo <htejun@gmail.com>
To: Business Kid <business.kid@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Recent kernel hosing partition
Date: Mon, 10 Dec 2007 22:39:54 +0900 [thread overview]
Message-ID: <475D41AA.2060205@gmail.com> (raw)
In-Reply-To: <f68177890712100347i3a03df38n36cffd00c8603ae1@mail.gmail.com>
Business Kid wrote:
> Yeah, dd will do that but I'm not too sure whether that would be
> helpful.
>
> That's a bit rough! Hexedit with style? :-).
:-)
> The drive is triggering all sorts of errors. Can you post the
> result of 'smartctl -a /dev/sdX' where sdX is the offending drive. Also
> please restore cc to linux-ide@vger.kernel.org
> <mailto:linux-ide@vger.kernel.org>.
>
>
> Attached smartctl -a /dev/sda > smartctl.out
>
> I see where you're going, and I think you're wrong. The drive is only 2
> months old. I had heavy toolchain compiles and massive copies/ deletions
> pass of without incident on sda8 while F7's root partition (sda3) was
> lightly loaded by comparison. sda3 picked up _all_ the errors. I never
> hit an error on the hard work - no dodgy exits. The console stuff on
> sda3 was all fine. It only screwed every application I was running under
> X - Firefox particularly. I could still compile with the tools & libs on
> sda3 when X was screwed. Badblocks never found a thing (e2fsck -cf).
> Lost+found is empty on every other partition.
Right, it doesn't look like your harddrive is bad.
> Sadly, "errors all over the place" is common enough with Via chipsets
> and Seagate disks. I've seen it before. I'm stuck with Via in this box.
> I would not have bought Seagate, but when someone gives it to you and
> you're unemployed...
I'm not aware of any specific issues with via + Segate drives. Have
pointers?
> Another issue here is that the old ide driver could get through the
> mess, whereas the newer one cannot. I get "Drive reset: success" and the
> old ide driver recovers, whereas the new one goes out to lunch. The log
> snippets show a 60 seconds gap between errors. That's a 60 second freeze.
Hmmm...
1. So, the IDE driver suffers from error conditions too? Do you have
logs around?
2. Do you have logs of libata driver goes out to lunch?
3. Can you post boot log from you current setup?
Thanks.
--
tejun
next prev parent reply other threads:[~2007-12-10 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 20:02 Recent kernel hosing partition business.kid
2007-12-10 7:51 ` Tejun Heo
[not found] ` <f68177890712100208o27d71584l685520d2e9ecf5bd@mail.gmail.com>
[not found] ` <475D11A1.1070700@gmail.com>
[not found] ` <f68177890712100347i3a03df38n36cffd00c8603ae1@mail.gmail.com>
2007-12-10 13:39 ` Tejun Heo [this message]
2007-12-10 17:49 ` For Junk Mail
2007-12-11 1:47 ` Tejun Heo
2007-12-11 10:19 ` For Junk Mail
2007-12-12 8:07 ` Tejun Heo
2007-12-12 12:08 ` For Junk Mail
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=475D41AA.2060205@gmail.com \
--to=htejun@gmail.com \
--cc=business.kid@gmail.com \
--cc=linux-ide@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).