From: Brad Campbell <brad@wasp.net.au>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Something is broken with SATA RAID ?
Date: Thu, 03 Mar 2005 09:03:42 +0400 [thread overview]
Message-ID: <42269AAE.7080106@wasp.net.au> (raw)
In-Reply-To: <1109810381l.5754l.0l@werewolf.able.es>
J.A. Magallon wrote:
> Hi...
>
> I posted this in other mail, but now I can confirm this.
>
> I have a box with a SATA RAID-5, and with 2.6.11-rc3-mm2+libata-dev1
> works like a charm as a samba server, I dropped it 12Gb from an
> osx client, and people does backups from W2k boxes and everything was fine.
> With 2.6.11-rc4-mm1, it hangs shortly after the mac starts copying
> files. No oops, no messages... It even hanged on a local copy (wget),
> so I will discard samba as the buggy piece in the puzzle.
>
> I'm going to make a definitive test with rc5-mm1 vs rc5-mm1+libata-dev1.
> I already know that plain rc5-mm1 hangs. I have to wait the md reconstruction
> of the 1.2 TB to check rc5-mm1+libata (and no user putting things there...)
>
> But, anyone has a clue about what is happening ? I have seen other
> reports of RAID related hangs... Any important change after rc3 ?
> Any important bugfix in libata-dev1 ? Something broken in -mm ?
There was (is) a bug in -rc4-mm1 that may still be there in -rc5-mm1 related to the way RAID-5 and
RAID-6 writes out blocks that can cause a deadlock in the raid code. Do you processes just hang in
the D state and any access to /proc/mdstat do the same thing?
Can you try with just 2.6.11+libata+libata-dev?
I moved to 2.6.11+libata+libata-dev+netdev and all my problems went away.
CC'd to linux-raid
Regards,
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
parent reply other threads:[~2005-03-03 5:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1109810381l.5754l.0l@werewolf.able.es>]
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=42269AAE.7080106@wasp.net.au \
--to=brad@wasp.net.au \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).