From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: linux-kernel@vger.kernel.org
Cc: dm-crypt@saout.de
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Thu, 30 Dec 2004 17:23:17 +0100 [thread overview]
Message-ID: <m38y7fn4ay.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <m3is6k4oeu.fsf@reason.gnu-hamburg> (Georg C. F. Greve's message of "Thu, 30 Dec 2004 01:31:37 +0100")
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
[ update ]
Okay, tried to find out what is causing the kernel to crash and so I
replaced the dm-crypt part by cryptoloop: same effect.
Then I tried ext3 on top of LVM2 RAID5 with no encryption and it still
crashes. Not sure what is causing the problem exactly, but it does not
seem that dm-crypt is to blame anymore.
The message I saw on the remote console when it crashed with pure ext3
on raid5 was:
Assertion failure in journal_start() at fs/jbd/transaction.c:271: "handle->h_transaction->t_journal == journal"
Hope this helps -- filed the bug as #3968 on buzilla.kernel.org, more
info at
http://bugzilla.kernel.org/show_bug.cgi?id=3968
Help appreciated, let me know if you have an idea.
Regards,
Georg
--
Georg C. F. Greve <greve@gnu.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-30 16:23 UTC|newest]
Thread overview: 88+ 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 [this message]
2004-12-30 17:39 ` Peter T. Breuer
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 18:31 ` Peter T. Breuer
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 21:39 ` Peter T. Breuer
2005-01-02 19:42 ` ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard) Andy Smith
2005-01-02 20:18 ` Peter T. Breuer
2005-01-03 0:30 ` Andy Smith
2005-01-03 6:41 ` Neil Brown
2005-01-03 8:37 ` Peter T. Breuer
2005-01-03 8:03 ` Peter T. Breuer
2005-01-03 8:58 ` Guy
2005-01-03 10:18 ` Partiy error detection - was " Brad Campbell
2005-01-03 12:11 ` Michael Tokarev
2005-01-03 14:23 ` Peter T. Breuer
2005-01-03 18:30 ` maarten
2005-01-03 21:36 ` Michael Tokarev
2005-01-05 5:50 ` Debian Sarge mdadm raid 10 assembling at boot problem Roger Ellison
2005-01-05 13:41 ` Michael Tokarev
2005-01-05 13:57 ` [help] [I2O] Adaptec 2400A on FC3 Angelo Piraino
2005-01-05 19:15 ` Debian Sarge mdadm raid 10 assembling at boot problem Roger Ellison
2005-01-05 9:56 ` ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard) Andy Smith
2005-01-05 10:44 ` Alvin Oga
2005-01-05 10:56 ` Brad Campbell
2005-01-05 11:39 ` Alvin Oga
2005-01-05 12:02 ` Brad Campbell
2005-01-05 13:23 ` Alvin Oga
2005-01-05 13:33 ` Brad Campbell
2005-01-05 14:44 ` parts -- " Alvin Oga
2005-01-19 4:46 ` Clemens Schwaighofer
2005-01-19 5:05 ` Alvin Oga
2005-01-19 5:49 ` Clemens Schwaighofer
2005-01-19 7:08 ` Alvin Oga
2005-01-05 13:36 ` Swap should be mirrored or not? (was Re: ext3 journal on software raid) Andy Smith
2005-01-05 14:12 ` ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard) Erik Mouw
2005-01-05 14:37 ` Michael Tokarev
2005-01-05 14:55 ` errors " Alvin Oga
2005-01-05 17:11 ` Erik Mouw
2005-01-06 5:41 ` Brad Campbell
2005-01-05 15:17 ` Guy
2005-01-05 15:33 ` Alvin Oga
2005-01-05 16:22 ` Michael Tokarev
2005-01-05 17:23 ` Peter T. Breuer
2005-01-05 16:23 ` Andy Smith
2005-01-05 16:30 ` Andy Smith
2005-01-05 17:04 ` swp - " Alvin Oga
2005-01-05 17:26 ` Andy Smith
2005-01-05 18:32 ` Alvin Oga
2005-01-05 22:35 ` Andy Smith
2005-01-06 0:57 ` Guy
2005-01-06 1:28 ` Mike Hardy
2005-01-06 3:32 ` Guy
2005-01-06 4:49 ` Mike Hardy
2005-01-09 21:07 ` Mark Hahn
2005-01-06 5:04 ` Alvin Oga
2005-01-06 6:18 ` Guy
2005-01-06 6:31 ` Alvin Oga
2005-01-06 9:38 ` swap on RAID (was Re: swp - Re: ext3 journal on software raid) Andy Smith
2005-01-06 17:46 ` Mike Hardy
2005-01-06 22:08 ` No swap can be dangerous (was Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid)) Andrew Walrond
2005-01-06 22:34 ` Jesper Juhl
2005-01-06 22:57 ` Mike Hardy
2005-01-06 23:15 ` Guy
2005-01-07 9:28 ` Andrew Walrond
2005-02-28 20:07 ` Guy
2005-01-07 1:31 ` confused Re: swap on RAID (was Re: swp - Re: ext3 journal on software raid) Alvin Oga
2005-01-07 2:28 ` Andy Smith
2005-01-07 13:04 ` Alvin Oga
2005-01-09 21:21 ` swp - Re: ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard) Mark Hahn
2005-01-09 22:20 ` Alvin Oga
2005-01-06 5:01 ` Alvin Oga
2005-01-05 17:07 ` Guy
2005-01-05 17:21 ` Alvin Oga
2005-01-05 17:32 ` Guy
2005-01-05 18:37 ` Alvin Oga
2005-01-05 17:34 ` ECC: RE: ext3 blah blah blah Gordon Henderson
2005-01-05 18:33 ` Alvin Oga
2005-01-05 17:26 ` ext3 journal on software raid (was Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard) David Greaves
2005-01-05 18:16 ` Peter T. Breuer
2005-01-05 18:28 ` Guy
2005-01-05 18:26 ` Guy
2005-01-05 15:48 ` Peter T. Breuer
[not found] ` <41D45C1F.5030307-XAri/EZa3C4vJsYlp49lxw@public.gmane.org>
2004-12-30 20:54 ` PROBLEM: Kernel 2.6.10 crashing repeatedly and hard berk walker
2005-01-01 13:39 ` Helge Hafting
2005-01-07 6:21 ` Clemens Schwaighofer
2005-01-07 9:39 ` Andy Smith
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=m38y7fn4ay.fsf@reason.gnu-hamburg \
--to=greve@fsfeurope.org \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@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).