From: "Jérôme Poulin" <jeromepoulin@gmail.com>
To: Валерий <paramonov@russia.ru>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"neilb@suse.de" <neilb@suse.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"duaneg@dghda.com" <duaneg@dghda.com>,
Alexander Beregalov <a.beregalov@gmail.com>
Subject: Re: BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
Date: Sat, 8 Oct 2011 09:36:42 -0400 [thread overview]
Message-ID: <5617831734450003872@unknownmsgid> (raw)
In-Reply-To: <4E8FE4E5.9040606@russia.ru>
As soon as smart says there are ANY problem, the disk IS going bad and
will have serious problem soon enough. Especially READ DMA errors
which mean it reallocate sectors. Consumer level disk try to hide
problems as hard as they can until the disk finally fail. Try ddrescue
from disk to /dev/null to check for speed, I guess it is slow.
Envoyé de mon appareil mobile.
Jérôme Poulin
Solutions G.A.
On 2011-10-08, at 01:52, Валерий <paramonov@russia.ru> wrote:
> So, this IDE drive has non-critical SMART errors listed at end of message by command smartctl --all /dev/sde. It is unclear how this might affect the command dd.
next prev parent reply other threads:[~2011-10-08 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 5:51 BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks Валерий
2011-10-08 13:36 ` Jérôme Poulin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-08 15:59 Валерий
2011-10-08 23:37 ` Duane Griffin
2011-10-09 16:51 Валерий
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=5617831734450003872@unknownmsgid \
--to=jeromepoulin@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=axboe@kernel.dk \
--cc=duaneg@dghda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=paramonov@russia.ru \
/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).