All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: reiserfs-list@namesys.com
Cc: sikkh@wp.pl
Subject: Tree issues, fsck output
Date: Tue, 29 Jun 2004 23:19:56 +0300	[thread overview]
Message-ID: <20040629201956.GK4990@nysv.org> (raw)

Hi!

***** Tree Traverse Pass: scanning the reiser4 internal tree.
FSCK: Node (2013064): The last key [377f5f:4(FB):2e616339375f63:3a45d8:99] in 2 the node is greater then the right delimiting key [2fa6e:4(FB):6c69626d70342e:1e88ad:1f7c].
FSCK: Node (469959), item (28), unit (0): Points to the node [2013064] with wrong delimiting keys. The whole subtree is skipped.
Error: Can't open node 2014146.
FSCK: Node (2014146): failed to open the node pointed by the node (469959), item(29), unit (0) on the level (2). The whole subtree is skipped.
Error: Can't open node 2014147.
FSCK: Node (2014147): failed to open the node pointed by the node (469959), item(30), unit (0) on the level (2). The whole subtree is skipped.
FSCK: Node (469959), item (31), unit (0): Points to the block (2014148) which isin the tree already. The whole subtree is skipped.

How deep is the shit I'm in? :P

What brought this on?

I'll just send this post now, I'll send a follow-up when I'm re-doing
fsck with some switches. This was just a basic fsck /dev/hda1, so maybe
no need to panic yet...

-- 
mjt


             reply	other threads:[~2004-06-29 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 20:19 mjt [this message]
2004-06-30  6:45 ` Tree issues, fsck output mjt
2004-06-30  9:03   ` mjt
2004-06-30  9:24     ` Vitaly Fertman
2004-06-30  9:42       ` mjt
2004-06-30 10:43         ` mjt

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=20040629201956.GK4990@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    --cc=sikkh@wp.pl \
    /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.