From: Valdis.Kletnieks@vt.edu
To: Thomas Backlund <tmb@mageia.org>
Cc: Andreas Dilger <adilger@dilger.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: INFO: task jbd2/dm-0-8:3993 blocked for more than 120 seconds
Date: Wed, 17 Aug 2011 19:48:07 -0400 [thread overview]
Message-ID: <27048.1313624887@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 18 Aug 2011 00:08:53 +0300." <4E4C2DE5.5020100@mageia.org>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Thu, 18 Aug 2011 00:08:53 +0300, Thomas Backlund said:
> Andreas Dilger skrev 17.8.2011 17:35:
> > This is a problem with your disk hardware.
> Are you sure?
> I get nothing from smart, even after I had executed the long test...
SMART is nice, but it isn't guaranteed. In particular, you need to
double-check that what you think it's testing in a "long" test is what
it actually did...
> # smartctl -a /dev/sda
> smartctl 5.39.1 2010-01-28 r3054 [x86_64-mandriva-linux-gnu] (local build)
> Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
>
> === START OF INFORMATION SECTION ===
> Device Model: WDC WD1002FAEX-00Z3A0
> Serial Number: WD-WCATR3168879
> Firmware Version: 05.01D05
> User Capacity: 1,000,204,886,016 bytes
So we're looking at a terabyte of disk...
> Selective self-test flags (0x0):
> After scanning selected spans, do NOT read-scan remainder of disk.
And it's *NOT* doing a read-scan of the entire terabyte.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-08-17 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 13:31 INFO: task jbd2/dm-0-8:3993 blocked for more than 120 seconds Thomas Backlund
2011-08-17 14:35 ` Andreas Dilger
2011-08-17 21:08 ` Thomas Backlund
2011-08-17 23:48 ` Valdis.Kletnieks [this message]
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=27048.1313624887@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmb@mageia.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