From: Vitaly Fertman <vitaly@namesys.com>
To: reiserfs-list@namesys.com
Cc: Adrian Ulrich <reiser4@blinkenlights.ch>
Subject: Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
Date: Tue, 7 Jun 2005 11:00:44 +0400 [thread overview]
Message-ID: <200506071100.44749.vitaly@namesys.com> (raw)
In-Reply-To: <20050606203914.3271673f.reiser4@blinkenlights.ch>
On Monday 06 June 2005 22:39, Adrian Ulrich wrote:
> I upgraded to Linux 2.6.11.11 using the -5 reiser4 patch.
>
>
> It fixed it.. somewhat.. it's still funky:
>
>
> * mkisofs doesn't crash with the new kernel, yeah!
> * after running mkisofs, grub can't read the filesystem anymore..
> The filesystem got corrupted. (It was ok before i booted
> into 2.6.11.11 and ran mkisofs !)
>
> So i bootet my rescue-system
> (Same kernel, reiser4progs 1.0.4. It's on /dev/md3)
>
> Running fsck:
>
> root@fuzzy:~# fsck.reiser4 /dev/md1
> *******************************************************************
> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
> *******************************************************************
>
> Fscking the /dev/md1 block device.
> Will check the consistency of the Reiser4 SuperBlock.
> Will check the consistency of the Reiser4 FileSystem.
> Continue?
> (Yes/No): Yes
> ***** fsck.reiser4 started at Mon Jun 6 20:07:51 2005
> Reiser4 fs was detected on /dev/md1.
> Master super block (16):
> magic: ReIsEr4
> blksize: 4096
> format: 0x0 (format40)
> uuid: c3fc85d3-be0d-4d71-9413-376cefcdf8fd
> label: <none>
>
> Format super block (17):
> plugin: format40
> description: Disk-format for reiser4.
> magic: ReIsEr40FoRmAt
> flushes: 0
> mkfs id: 0x5bedb66f
> blocks: 9765488
> free blocks: 2035573
> root block: 4270052
> tail policy: 0x2 (smart)
> next oid: 0x62d63
> file count: 180460
> tree height: 4
> key policy: LARGE
>
>
> CHECKING STORAGE TREE
> 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).
> FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat data.
> FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: broken item found.
> FSCK: Node (411219): the node is broken. Pointed from the node (411211), item (0), unit (0). The whole subtree is skipped.
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.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2005-06-07 7:00 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 [this message]
2005-06-07 11:01 ` Adrian Ulrich
2005-06-07 10:32 ` Vitaly Fertman
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=200506071100.44749.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.