All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Schleifer <alexander.schleifer@googlemail.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 speed goes down
Date: Wed, 18 Jul 2012 11:26:15 +0200	[thread overview]
Message-ID: <CA+=meHUK7Sw32BYA57iPNQHpZHPp8s8HOnb5dXA_kwq__H_FEw@mail.gmail.com> (raw)
In-Reply-To: <CA+=meHWy3Uejy+At8kB0u4AyRPqR1B_iZoD1LOfFDw5GsmUqkg@mail.gmail.com>

I assume, that there is no physical error on the harddisks, because
nothing shows up in log files, SMART values are OK, resync end with no
error and fsck also found nothing to repair.
So I changed the scheduler from cfq to deadline, but this only takes a
couple of minutes longer until the RAID locks up. In iotop, I can see
the process "smbd", which I used for the file transfer -  it uses
about 98% of IO. Trying to unmount or stop the array will take
forever, even if I try to kill the smbd process.
I will now try to get a lock by transferring a file to a harddisk
which is not in this array.

-Alex

2012/7/16 Alexander Schleifer <alexander.schleifer@googlemail.com>:
> Hi,
>
> after re-sync and fsck, everything seems fine. The first try to copy a
> big test file to the raid5 starts with a speed of ~45 MB/s which is
> perfect, but after a couple of minutes the speed goes down to ~10
> KB/s. The only way to get the raid5 working again was to reset the
> system. The raid5 then goes again in resync from an unclean array. I
> checked dmesg, but found nothing. What can I do to get more
> information what is going on there?
>
> Thanks,
> Alex

  reply	other threads:[~2012-07-18  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 20:10 RAID5 speed goes down Alexander Schleifer
2012-07-18  9:26 ` Alexander Schleifer [this message]
2012-07-19 16:32 ` Asdo

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='CA+=meHUK7Sw32BYA57iPNQHpZHPp8s8HOnb5dXA_kwq__H_FEw@mail.gmail.com' \
    --to=alexander.schleifer@googlemail.com \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.