From: butdiene <butdiene@yahoo.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 panicked with zam-42245
Date: Tue, 15 Jan 2008 10:58:38 -0800 (PST) [thread overview]
Message-ID: <14844935.post@talk.nabble.com> (raw)
In-Reply-To: <1200354983.31588.13.camel@localhost>
yes, you must be right. I had reiser4 debug option enabled in kernel config.
and it happens only after I enabled it.
I wasn't happy with reiser4 so far.
1st, after crashes, fsck.reiser4 always found lost+found, while I hoped
transaction support would result in a crash resilient fs.
I couldn't get get rid of the firefox hang problem. whenever "sync" issued,
the hdd spins for long and firefox hangs. this results in a rather slow fs.
now I have switched back to jfs. it's incredibly fast compared with what I
experienced with reiser4.
thanks a lot!
Jake Maciejewski wrote:
>
> On Mon, 2008-01-14 at 11:43 -0800, butdiene wrote:
>> I got this error message reproducibly when building kernel (make). I
>> don't
>> have the log file since kernel hangs thereafter
>>
>> it happens only on my laptop but not to several other reiser4 boxes.
>>
>> Thanks!
>
> Are you sure it wasn't 32245? That's the one I get compiling. If I
> disable debug, I don't see it, and reiser4 seems completely stable. With
> debug enabled, I always hit zam-32245 eventually.
>
> --
> Jake Maciejewski <maciejej@msoe.edu>
>
> -
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
View this message in context: http://www.nabble.com/reiser4-panicked-with-zam-42245-tp14811158p14844935.html
Sent from the ReiserFS - General mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-01-15 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 19:43 reiser4 panicked with zam-42245 butdiene
2008-01-14 23:56 ` Jake Maciejewski
2008-01-15 18:58 ` butdiene [this message]
2008-01-15 20:05 ` Edward Shishkin
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=14844935.post@talk.nabble.com \
--to=butdiene@yahoo.com \
--cc=reiserfs-devel@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).