From: "Yura Umanets" <umanets@priocom.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: about crash
Date: Thu, 25 Apr 2002 19:40:34 +0300 [thread overview]
Message-ID: <3CC83182.4020500@priocom.com> (raw)
In-Reply-To: 1685846437.20020425182146@tnonline.net
Anders Widman wrote:
> ok.. This is the output I get when running "debugreiserfs
> /dev/Server/FTPRoot -B"
>
>
> <-------------debugreiserfs, 2002------------->
> reiserfsprogs 3.x.1c-pre2
>
> debugreiserfs: option requires an argument -- B
>
> Filesystem state: consistent
>
> Reiserfs super block in block 16 on 0x3a00 of format 3.6 with standard journal
> Count of blocks on the device: 213532672
> Number of bitmaps: 6517
> Blocksize: 4096
> Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks):
> 20694828
> Root block: 67992
> Filesystem is cleanly umounted
> Tree height: 5
> Hash function used to sort names: "r5"
> Objectid map size 550, max 972
> Journal parameters:
> Device [0x0]
> Magic [0x0]
> Size 8193 blocks (including 1 for journal header) (first block 18)
> Max transaction length 0 blocks
> Max batch size 0 blocks
> Max commit age 0
> Blocks reserved by journal: 0
> Fs state field: 0x0
> sb_version: 2
> inode generation number: 52783
> UUID: ce0c6cd1-e381-4597-bd30-edc0074968ab
> LABEL:
> Set flags in SB:
>
>
>
> This is what I get when running "debugreiserfs /dev/Server/FTPRoot -B
> 669227":
>
>
> [root@server /]# debugreiserfs /dev/Server/FTPRoot -B 669227
>
> <-------------debugreiserfs, 2002------------->
> reiserfsprogs 3.x.1c-pre2
>
> Will try to extract list of bad blocks and save it to '669227' file
> Done
>
>
> I end up with a file called 669227 which is 0 bytes long. I'll try
> with the same version of debugreiserfs as you are running.
>
>
You should be using
debugreiserfs /dev/Server/FTPRoot -1 669227
--
Yury Umanets,
IT Engeneer of Priocom Corp.
Phone: +380 44 4924636, ICQ: 55494590
next prev parent reply other threads:[~2002-04-25 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 14:48 about crash Yura Umanets
[not found] ` <1061290531.20020425170549@tnonline.net>
[not found] ` <3CC81E0F.90000@priocom.com>
[not found] ` <1672863140.20020425173202@tnonline.net>
2002-04-25 15:57 ` Yura Umanets
[not found] ` <1294772062.20020425180352@tnonline.net>
2002-04-25 16:17 ` Yura Umanets
[not found] ` <1685846437.20020425182146@tnonline.net>
2002-04-25 16:40 ` Yura Umanets [this message]
[not found] ` <888141406.20020425190001@tnonline.net>
[not found] ` <3CC8377F.6010400@priocom.com>
[not found] ` <918425062.20020425190444@tnonline.net>
2002-04-25 17:39 ` Yura Umanets
[not found] ` <310382968.20020425193723@tnonline.net>
2002-04-25 17:57 ` Yura Umanets
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=3CC83182.4020500@priocom.com \
--to=umanets@priocom.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.