From: kenny gorman <kgorman@panix.com>
To: reiserfs-list@namesys.com
Subject: Re: corruption? how do I fix?
Date: Wed, 13 Nov 2002 07:14:41 -0800 [thread overview]
Message-ID: <3DD26C61.6000103@panix.com> (raw)
In-Reply-To: 3DD26A74.3090800@namesys.com
Yury,
Thx for the quick response. Is there a way to 'see' if the
reiserfsck --fix-fixable .... command would work? like a dry run?
Running another backup is going to take a while, so I need to gauge the
risks. What is this command going to do? Is it permanent when I do it
(seems like it from the docs)
-kg
Yury Umanets wrote:
> kenny gorman wrote:
>
>> downloaded and built the latest reiserfsprogs, and ran debugreiserfs
>> and reiserfsck here is the output.. Notice the '1 round of corruption
>> can be fixed msg' at the bottom.
>>
>> <-------------debugreiserfs, 2001------------->
>> reiserfsprogs 3.x.0j
>> reiserfs_open: bitmap 45 was marked free
>> reiserfs_open: bitmap 46 was marked free
>> <continued until>
>> reiserfs_open: bitmap 67 was marked free
>> reiserfs_open: bitmap 68 was marked free
>> reiserfs_open: bitmap 69 was marked free
>> Super block of format 3.5 found on the 0x3 in block 16
>> Block count 7752704
>> Blocksize 4096
>> Free blocks 2361789
>> Busy blocks (skipped 16, bitmaps - 237, journal blocks - 8193
>> 1 super blocks, 5382468 data blocks
>> Root block 8384
>> Journal block (first) 18
>> Journal dev 0
>> Journal orig size 8192
>> Filesystem state VALID
>> Tree height 4
>> Hash function used to sort names: "r5"
>> Objectid map size 2, max 1004
>> Version 0
>>
>> reiserfsck:<-------------reiserfsck, 2002------------->
>> reiserfsprogs 3.6.4
>>
>> *************************************************************
>> ** If you are using the latest reiserfsprogs and it fails **
>> ** please email bug reports to reiserfs-list@namesys.com, **
>> ** providing as much information as possible -- your **
>> ** hardware, kernel, patches, settings, all reiserfsk **
>> ** messages (including version), the reiserfsck logfile, **
>> ** check the syslog file for any related information. **
>> ** If you would like advice on using this program, support **
>> ** is available for $25 at www.namesys.com/support.html. **
>> *************************************************************
>>
>> Will read-only check consistency of the filesystem on /dev/datagrp/datavol
>> Will put log info to 'stdout'
>>
>> Do you want to run this program?[N/Yes] (note need to type Yes if you
>> do):Yes
>> ###########
>> reiserfsck --check started at Wed Nov 13 07:00:41 2002
>> ###########
>> Replaying journal..
>> 0 transactions replayed
>> Checking internal tree..finished
>> Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
>> Checking Semantic tree:
>> finished
>> 1 found corruptions can be fixed with --fix-fixable
>> ###########
>> reiserfsck finished at Wed Nov 13 07:00:48 2002
>> ###########
>>
> Okay, now you should backup your data and type:
> reiserfsck --fix-fixable /dev/datagrp/datavol
>
> What does it say?
>
next prev parent reply other threads:[~2002-11-13 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 5:11 corruption? how do I fix? kenny gorman
2002-11-13 5:38 ` kenny gorman
2002-11-13 8:44 ` Dieter Nützel
[not found] ` <3DD2304E.70500@namesys.com>
2002-11-13 15:02 ` kenny gorman
[not found] ` <3DD26A74.3090800@namesys.com>
2002-11-13 15:14 ` kenny gorman [this message]
2002-11-13 21:41 ` Vitaly Fertman
2002-11-14 0:13 ` Ed Tomlinson
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=3DD26C61.6000103@panix.com \
--to=kgorman@panix.com \
--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.