From: Pallai Roland <dap@mail.index.hu>
To: djani22@dynamicweb.hu
Cc: linux-raid@vger.kernel.org
Subject: Re: Oops in raid1?
Date: Sat, 20 Aug 2005 18:50:42 +0200 [thread overview]
Message-ID: <1124556642.3810.143.camel@localhost.localdomain> (raw)
In-Reply-To: <025a01c5a5a3$ee160540$0400a8c0@LocalHost>
On Sat, 2005-08-20 at 18:26 +0200, djani22@dynamicweb.hu wrote:
> I get this message, when high upload. (disk write)
> But the GNBD generates this, in that situation, and thats why I think, this
> is something else...
yes, seems like it's an another bug in the GNBD, but the backtrace is
clear in the first case too, the request to the underlying device what's
generated that panic, not the raid1d's own.
all in all, try to disable the preempt mode, that may help..
--
dap
next prev parent reply other threads:[~2005-08-20 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050717182650.24540.patches@notabene>
2005-07-17 8:27 ` [PATCH md ] When resizing an array, we need to update resync_max_sectors as well as size NeilBrown
2005-07-17 12:10 ` Found a new bug! djani22
2005-07-17 22:13 ` Neil Brown
2005-07-17 22:31 ` djani22
2005-08-14 22:38 ` djani22
2005-08-15 1:21 ` Neil Brown
2005-08-15 10:50 ` djani22
2005-08-16 13:54 ` perfomance question djani22
2005-08-16 14:30 ` RAID6 Query Colonel Hell
2005-08-16 15:40 ` dean gaudet
2005-08-16 16:44 ` Colonel Hell
2005-08-18 4:59 ` perfomance question Neil Brown
2005-08-18 15:20 ` djani22
2005-08-18 4:34 ` Found a new bug! Neil Brown
2005-08-18 15:39 ` djani22
2005-08-20 9:55 ` Oops in raid1? djani22
2005-08-20 15:53 ` Pallai Roland
2005-08-20 16:26 ` djani22
2005-08-20 16:50 ` Pallai Roland [this message]
2005-08-20 16:57 ` djani22
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=1124556642.3810.143.camel@localhost.localdomain \
--to=dap@mail.index.hu \
--cc=djani22@dynamicweb.hu \
--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).