From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com, andrew.j.wade@gmail.com
Subject: Re: assertion failed: JF_ISSET(jprivate(page), JNODE_DIRTY)
Date: Wed, 30 Aug 2006 14:26:12 +0400 [thread overview]
Message-ID: <200608301426.12602.zam@namesys.com> (raw)
In-Reply-To: <200608291738.21648.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>
On 30 August 2006 01:38, Andrew James Wade wrote:
> I now have a stack trace for this assertion:
there is a race between znode_make_dirty and flushing dirty node to
disk. I guess (but not sure by 100%) it has no bad effect so the
assertion is wrong.
> reiser4 panicked cowardly: reiser4[tar(5412)]:
[ ... ]
--
Alex.
next prev parent reply other threads:[~2006-08-30 10:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 21:58 Reiser4 stress test Andrew James Wade
2006-08-21 22:41 ` assertion failed: can_hit_entd(ctx, s) Andrew James Wade
2006-08-25 18:42 ` Alexander Zarochentsev
2006-08-26 0:57 ` Andrew James Wade
2006-08-29 21:10 ` [patch] " Andrew James Wade
2006-08-30 6:45 ` Alexander Zarochentsev
2006-08-30 15:43 ` Hans Reiser
2006-08-30 16:26 ` Alexander Zarochentsev
2006-08-21 22:44 ` assertion failed: JF_ISSET(jprivate(page), JNODE_DIRTY) Andrew James Wade
2006-08-29 21:38 ` Andrew James Wade
2006-08-30 10:26 ` Alexander Zarochentsev [this message]
2006-08-30 21:29 ` Andrew James Wade
2006-08-21 23:22 ` assertion failed: keyeq(znode_get_rd_key(node), znode_get_ld_key(node->right)) Andrew James Wade
2006-08-21 23:35 ` [nikita-1936] assertion failed: reiser4_no_counters_are_held() Andrew James Wade
2006-08-25 13:18 ` Alexander Zarochentsev
2006-09-02 0:35 ` [patch] Fix use after free in jrelse_tail Andrew James Wade
2006-08-22 5:23 ` Reiser4 stress test Hans Reiser
2006-08-22 21:57 ` Andrew James Wade
2006-08-22 22:07 ` Andrew James Wade
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=200608301426.12602.zam@namesys.com \
--to=zam@namesys.com \
--cc=andrew.j.wade@gmail.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.