All of lore.kernel.org
 help / color / mirror / Atom feed
From: Silviu Marin-Caea <silviu@genesys.ro>
To: reiserfs-list@namesys.com
Subject: bad blocks in the wrong place
Date: Tue, 23 Sep 2003 09:24:13 +0300	[thread overview]
Message-ID: <3F6FE70D.9090700@genesys.ro> (raw)

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

I have a large hard-disk (120 GB) on which some blocks went bad.

Now, it cannot be mounted.  Attached is what debugreiserfs says.  What 
can I do; I'm newbie to reiserfs architecture.  I thought that ReiserFS 
keeps copies of the superblock or something, like ext2/3 does.

reiserfsck says "error occured looks like hardware problem.  bread 
cannot read block 13271040".  That's the actual number it displays.

Thank you

I hope this is the right list for the question.

[-- Attachment #2: debugreiser --]
[-- Type: text/plain, Size: 825 bytes --]


Filesystem state: consistency is not checked after last mounting

Reiserfs super block in block 16 on 0x1642 of format 3.6 with standard journal
Count of blocks on the device: 29945160
Number of bitmaps: 914
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 29154954
Root block: 14969
Filesystem is NOT clean
Tree height: 4
Hash function used to sort names: "r5"
Objectid map size 10, max 972
Journal parameters:
	Device [0x0]
	Magic [0x34ae2c74]
	Size 8193 blocks (including 1 for journal header) (first block 18)
	Max transaction length 1024 blocks
	Max batch size 900 blocks
	Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0
sb_version: 2
inode generation number: 35482
UUID: 48d29ced-fe37-4c68-adf8-32ace9f2be45
LABEL: 
Set flags in SB:
	ATTRIBUTES CLEAN

                 reply	other threads:[~2003-09-23  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F6FE70D.9090700@genesys.ro \
    --to=silviu@genesys.ro \
    --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.