All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Worley <cworley@liberate.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] reiserfs oops at init
Date: Mon Jan 14 15:11:01 2002	[thread overview]
Message-ID: <3C434EB9.8060504@liberate.com> (raw)
In-Reply-To: 451550000.1011030447@tiny

Chris Mason wrote:

>>>If you want to send the errors from reiserfsck --check, I can confirm
>>>things a little better.
>>>
>>
>>It's going to be a big file... do you just want the tail?
>>
>>
> 
> Lets start with the tail, my internet connection isn't that hot right now.


Every error I could see was of the form:

bad_directory_item: block 141874: item 698385 744805 0x1 DIR (3), len 
350, location 2576 entry count 14, fsck need 0, format old has entry 
".." with wrong deh_state 140744 - expected 4 - fixed

This goes on for ~11MB.

The tail is:

free block count 3306944 mismatches with a correct one 4783644.
on-disk bitmap does not match to the correct one. 1476700 bits differ

With the new reiserfs version, it actually says "fixed", the older 
version didn't say that (except at the beginning), and I don't think 
they really fixed anything.

Although those "free block count mismatch/correct" numbers look like 
they did for all previous runs, this run with the new software said 
nothing of (something like) "10 ... must be fixed with 
--rebuild-tree".  It still doesn't boot.

On to the "--rebuild-tree" pass.  Wish me luck.

Chris

  reply	other threads:[~2002-01-14 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 11:26 [linux-lvm] reiserfs oops at init Chris Worley
2002-01-14 11:48 ` Chris Mason
2002-01-14 15:11   ` Chris Worley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14  9:14 Chris Worley
2002-01-14  9:24 ` Chris Mason

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=3C434EB9.8060504@liberate.com \
    --to=cworley@liberate.com \
    --cc=linux-lvm@sistina.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.