All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Stephen Buckmelter <stephen.buckmelter@sun.com>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: reiserfsck
Date: Fri, 07 Mar 2003 23:19:58 +0300	[thread overview]
Message-ID: <3E68FEEE.3080102@namesys.com> (raw)
In-Reply-To: <1047064848.2129.65.camel@bucklinux.buckmelter.net>

Stephen Buckmelter wrote:

>Getting the following error when running reiserfsck.  Submitting per the
>man page.
>
>Thanks!
>
>--Steve
>
>
>bucklinux:/ # reiserfsck --rebuild-tree --logfile rebuild.log /dev/sda1
>reiserfsck 3.6.2 (2002)
>  **********************************************************
>  ** This  is  an  experimental  version  of  reiserfsck, **
>  **              !! MAKE A BACKUP FIRST !!               **
>  ** Don't run this program unless something  is  broken. **
>  ** Some types of random FS damage can be recovered from **
>  ** by  this  program,   which  basically   throws  away **
>  ** the internal nodes of the tree and then reconstructs **
>  ** them. This program is for use only by the desperate, **
>  ** and is  of only beta quality.  If you are using  the **
>  ** latest  reiserfsprogs  and  it  fails  please  email **
>  ** bug reports to reiserfs-list@namesys.com.            **
>  **********************************************************
>
>Will rebuild the filesystem (/dev/sda1) tree
>Will put log info to 'rebuild.log'
>
>Do you want to run this program?[N/Yes] (note need to type Yes):Yes
>Replaying journal..
>No transactions found
>###########
>reiserfsck --rebuild-tree started at Fri Mar  7 10:27:28 2003
>###########
>
>Pass 0:
>Loading on-disk bitmap .. ok, 802632 blocks marked used
>Skipping 8345 blocks (super block, journal, bitmaps) 794287 blocks will
>be read
>0%.                                                      left 752867,
>3765 /sec
>bread: Cannot read a block # 449052.
>
>
>
>Aborted
>bucklinux:/ #
>
>
>  
>
This is a bad block on the hard drive.  Vitaly, the newer fscks give 
instructions about bad blocks, yes?

Stephen, you can read our faq and act accordingly, or pay $25 and we'll 
handle everything for you if you give a login or provide personalized 
instructions otherwise (but workday is over for today....)

-- 
Hans



  reply	other threads:[~2003-03-07 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 19:20 reiserfsck Stephen Buckmelter
2003-03-07 20:19 ` Hans Reiser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-22 14:16 reiserfsck Peter Herklotz
2002-08-22 14:44 ` reiserfsck Vitaly Fertman

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=3E68FEEE.3080102@namesys.com \
    --to=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=stephen.buckmelter@sun.com \
    --cc=vitaly@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.