From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: Asdo <asdo@shiftmail.org>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
"Timothy D. Lenz" <tlenz@vorgon.com>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: possible bus loading problem during resync
Date: Fri, 12 Mar 2010 11:43:07 +0000 [thread overview]
Message-ID: <73e903671003120343m26999ddle5e01286eebbc93f@mail.gmail.com> (raw)
In-Reply-To: <4B9A1ED0.7060902@shiftmail.org>
On Fri, Mar 12, 2010 at 11:00 AM, Asdo <asdo@shiftmail.org> wrote:
>
>>> If that is true, how does that happen, the driver is hung? But anyway,
>>> how can such things happen when there is more than one CPU-core?
>>>
>>
>> A drive produces an error, the whole controler hangs and resets all
>> ports, all drives have to finish being reset before any IO can continue.
>> Hapens easily enough.
>>
>
> Ok but this is a multi-core CPU and he said Putty and WinSCP were hung.
> Ok for WinSCP... but Putty?
>
> Timothy is Putty hung on array check even on NCQ disabled?
>
> What is the resync speed? If it is very high it could be a CPU starvation
> but it's strange with only 2 drives. If it is very low I am not sure.
> Are disks write caches enabled?
>
> I am not able to spot any problem from your iostat or dmesg.
> Note: yes the iostat -x 1 was supposed to be captured during resync.
> Trigger a resync manually for the test. You can start it with echo check and
> stop it with echo idle > /sys/block/mdX/md/sync_action
>
I find "gnome-disk-utility" A.K.A. "palimpsest" to be a very good
heuristic to tell whether any drives are giving me physical trouble.
If there is a high remapped-sector-count or if Palimpsest otherwise
thinks a drive is suspect, there is a good chance that any unexplained
slowdowns in the machine are due to that drive.
If nothing more, it's a cheap way to get more information.
(My way of getting Palimpsest to check out drives in a machine that
doesn't have the program available in its installed distro
repositories is to run Ubuntu 9.10 from an USB stick. Boot, and up
comes Palimpsest.)
Hope this helps. Best of luck.
-- Kristleifur
prev parent reply other threads:[~2010-03-12 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 6:31 possible bus loading problem during resync Timothy D. Lenz
2010-03-09 10:30 ` Kristleifur Daðason
2010-03-09 11:00 ` Asdo
2010-03-11 5:53 ` Goswin von Brederlow
2010-03-12 11:00 ` Asdo
2010-03-12 11:43 ` Kristleifur Daðason [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=73e903671003120343m26999ddle5e01286eebbc93f@mail.gmail.com \
--to=kristleifur@gmail.com \
--cc=asdo@shiftmail.org \
--cc=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=tlenz@vorgon.com \
/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).