All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Fertman <vitaly@namesys.com>
To: Adrian Ulrich <reiser4@blinkenlights.ch>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
Date: Tue, 7 Jun 2005 14:32:11 +0400	[thread overview]
Message-ID: <200506071432.11752.vitaly@namesys.com> (raw)
In-Reply-To: <20050607130111.39bda1f2.reiser4@blinkenlights.ch>

On Tuesday 07 June 2005 15:01, Adrian Ulrich wrote:
> Hi Vitaly,
> 
> > there was a format change to work with encryption plugin in 
> > -5 reiser4 patch. progs do not have its support yet. grub works 
> > through the progs code so its the same problem, mkisofs is not 
> > relevant here.
> 
> I don't think thats the problem:

I am about the particular fsck message that appeares when you 
use -5 reiser4 patch: 

> > FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look 
> > like a valid SD plugin set extention: wrong pset member count detected (12). 



> It looks like a remount bug:
>  See <20050607065750.4dd203b9.reiser4@blinkenlights.ch> (my other mail)
> 

  reply	other threads:[~2005-06-07 10:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 14:50 reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super) Adrian Ulrich
2005-06-06  8:43 ` E.Gryaznova
2005-06-06  8:25   ` Adrian Ulrich
2005-06-06  8:55 ` Vitaly Fertman
2005-06-06 18:39   ` Adrian Ulrich
2005-06-07  4:57     ` Adrian Ulrich
2005-06-07  7:00     ` Vitaly Fertman
2005-06-07 11:01       ` Adrian Ulrich
2005-06-07 10:32         ` Vitaly Fertman [this message]
2005-06-07 12:10           ` Adrian Ulrich
2005-06-07 11:17             ` Raymond A. Meijer
2005-06-07 16:58               ` Adrian Ulrich
2005-06-06 10:31 ` E.Gryaznova
2005-06-06 10:23   ` Adrian Ulrich

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=200506071432.11752.vitaly@namesys.com \
    --to=vitaly@namesys.com \
    --cc=reiser4@blinkenlights.ch \
    --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.