From: berk walker <berk.walker@verizon.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Peter T. Breuer" <ptb@lab.it.uc3m.es>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
dm-crypt@saout.de
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Thu, 30 Dec 2004 15:54:44 -0500 [thread overview]
Message-ID: <41D46B14.2080301@verizon.net> (raw)
In-Reply-To: <41D45C1F.5030307@tls.msk.ru>
Michael Tokarev wrote:
> Peter T. Breuer wrote:
>
>> In gmane.linux.raid Georg C. F. Greve <greve@fsfeurope.org> wrote:
>>
>> Yes, well, don't put the journal on the raid partition. Put it
>> elsewhere (anyway, journalling and raid do not mix, as write ordering
>> is not - deliberately - preserved in raid, as far as I can tell).
>
>
> This is a sort of a nonsense, really. Both claims, it seems.
> I can't say for sure whenever write ordering is preserved by
> raid -- it should, and if it isn't, it's a bug and should be
> fixed. Nothing else is wrong with placing journal into raid
> (the same as the filesystem in question). Suggesting to remove
> journal just isn't fair: the journal is here for a reason.
> And, finally, the kernel should not crash. If something like
> this is unsupported, it should refuse to do so, instead of
> crashing randomly.
>
> /mjt
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I might have missed some of this thread....
but have you tried this on a completely different box? I have seen, and
am fighting some problems such as yours, and having nothing to do with raid.
If you haven't, then try it. You might get different results. Hardware
can sometimes be a dog to chase down, problemwise.
b-
next prev parent reply other threads:[~2004-12-30 20:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:31 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker [this message]
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King
2004-12-31 9:58 ` Georg C. F. Greve
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 10:21 Nick Warne
2004-12-31 11:46 Manfred Spraul
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=41D46B14.2080301@verizon.net \
--to=berk.walker@verizon.net \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=ptb@lab.it.uc3m.es \
/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