All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Vander Jagt <benjamin@winchesterpc.com>
To: reiserfs-list@namesys.com
Subject: Re: [nikita-3002]: assertion failed: carry_level_invariant(doing, CARRY_DOING)
Date: Fri, 18 Aug 2006 18:39:59 -0700 (PDT)	[thread overview]
Message-ID: <5880857.post@talk.nabble.com> (raw)
In-Reply-To: <200608171634.13172.ajwade@cpe001346162bf9-cm0011ae8cd564.cpe.net.cable.rogers.com>




Andrew James Wade-3 wrote:
> 
>      I've been getting occasional short freezes of a couple of minutes.
> But that's probably unrelated: as I have debugging turned on and am
> deliberately stressing the fs poor performance is not unexpected.
> ...
>> Andrew, may I ask for the contents of your /proc/meminfo file? 
> 
> Sure:
> 
> MemTotal:       512648 kB
> MemFree:         70612 kB
> Buffers:          2800 kB
> Cached:         105236 kB
> SwapCached:      33812 kB
> Active:         335988 kB
> Inactive:        63028 kB
> SwapTotal:     9791608 kB
> SwapFree:      9757768 kB
> Dirty:              84 kB
> Writeback:           0 kB
> AnonPages:      267960 kB
> Mapped:          52792 kB
> Slab:            22760 kB
> PageTables:       3148 kB
> NFS Unstable:        0 kB
> Bounce:              0 kB
> CommitLimit:  10047932 kB
> Committed_AS:   686084 kB
> VmallocTotal:   515796 kB
> VmallocUsed:     25572 kB
> VmallocChunk:   489680 kB
> HugePages_Total:     0
> HugePages_Free:      0
> HugePages_Rsvd:      0
> Hugepagesize:     4096 kB
> 
> I am currently trying to distill a test-case for crashing the fs.
> It is going slowly, but I have managed to provoke a few panics,
> including some new ones:
> 
> reiser4 panicked cowardly: reiser4[scatteredwrites(4506)]:
> reiser4_writepage (fs/reiser4/page_cache.c:522)[]:
> assertion failed: can_hit_entd(ctx, s)
> Kernel panic - not syncing: reiser4[scatteredwrites(4506)]:
> reiser4_writepage (fs/reiser4/page_cache.c:522)[]:
> assertion failed: can_hit_entd(ctx, s)
> 
> reiser4 panicked cowardly: reiser4[tar(4238)]: reiser4_update_extent
> (fs/reiser4/plugin/item/extent_file_ops.c:807)[]:
> assertion failed: reiser4_lock_counters()->d_refs == 0
> Kernel panic - not syncing: reiser4[tar(4238)]: reiser4_update_extent
> (fs/reiser4/plugin/item/extent_file_ops.c:807)[]:
> assertion failed: reiser4_lock_counters()->d_refs == 0
> 
> reiser4 panicked cowardly: reiser4[patch(9302)]:
> reiser4_set_page_dirty_internal (fs/reiser4/page_cache.c:475)[]:
> assertion failed: JF_ISSET(jprivate(page), JNODE_DIRTY)
> Kernel panic - not syncing: reiser4[patch(9302)]:
> reiser4_set_page_dirty_internal (fs/reiser4/page_cache.c:475)[]:
> assertion failed: JF_ISSET(jprivate(page), JNODE_DIRTY)
> 
> These are all for 2.6.18-rc4-mm1 + the small patch upthread.
> 
> Andrew Wade
> 

I will watch for your results.  Turning on the swap *blush* seems to have
eliminated all dmesg warnings and errors, but I'm still hanging at shutdown
time.  It now sounds like we have two different circumstances that resulted
in the same error, so I'll just watch the results of your testing. 
Meanwhile, I'll run the same kernel + patch you're running on another
computer and watch.

-Benjamin Vander Jagt
-- 
View this message in context: http://www.nabble.com/-nikita-3002-%3A-assertion-failed%3A-carry_level_invariant%28doing%2C-CARRY_DOING%29-tf2042550.html#a5880857
Sent from the ReiserFS - General forum at Nabble.com.


      reply	other threads:[~2006-08-19  1:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 21:49 [nikita-3002]: assertion failed: carry_level_invariant(doing, CARRY_DOING) Andrew James Wade
2006-08-03 12:51 ` Andrew James Wade
2006-08-03 15:28   ` Alexander Zarochentsev
2006-08-04  0:53     ` Andrew James Wade
2006-08-07  2:24     ` Andrew James Wade
2006-08-10 17:55       ` Andrew James Wade
2006-08-11  9:15         ` Vladimir V. Saveliev
2006-08-11 18:37           ` Andrew James Wade
2006-08-16 13:32           ` Benjamin Vander Jagt
2006-08-17 20:34             ` Andrew James Wade
2006-08-19  1:39               ` Benjamin Vander Jagt [this message]

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=5880857.post@talk.nabble.com \
    --to=benjamin@winchesterpc.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.