From: Fredrik Andersson <nablaman@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Linux Software Raid hangs after months of operation
Date: Fri, 31 Jul 2009 21:05:35 +0200 [thread overview]
Message-ID: <a125a870907311205k6380fafcy3eecbac6150f23f5@mail.gmail.com> (raw)
Hi, I have a bunch of machines running Linux 2.6.29.1 on x86_64 which
are running Linux software raid consisting of two disk partitions
merged into a single raid0 in /dev/md0. This setup is for performance
reasons.
The OS is not run from the raid, it is only used to hold a set of data files.
This seems to work great for weeks to months at a time, but then all
of a sudden access to the raid filesystem completely locks up. A
process trying to access any file in there hangs to the point where it
cannot be killed even with -9, so I suppose it's locked up in a
syscall.
I can't attach a debugger to the process, for then the terminal locks
up too. But the system is operational as long as I don't read anything
from the raid mount.
Th only thing that helps is a reboot. Then the raid will function
correctly again.
The version of mdadm is v2.6.7.1 - 15th October 2008.
Here is my /etc/mdadm.conf:
DEVICE /dev/sda5
DEVICE /dev/sdb3
ARRAY /dev/md0 devices=/dev/sda5,/dev/sdb3
/proc/mdstat from a locked machine:
Personalities : [raid0]
md0 : active raid0 sda5[0] sdb3[1]
898362368 blocks 256k chunks
unused devices: <none>
The raid has an ext4 filesystem on it.
I can find no other logs or status files for the software raid system.
There's nothing in /var/log/messages or any other standard log.
Does anybody know what is going on? Is this a known bug in md or the kernel?
Thank you for any help!
Fredrik
next reply other threads:[~2009-07-31 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 19:05 Fredrik Andersson [this message]
2009-07-31 21:30 ` Linux Software Raid hangs after months of operation NeilBrown
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=a125a870907311205k6380fafcy3eecbac6150f23f5@mail.gmail.com \
--to=nablaman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox