All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Israel <israel@tux.org>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: a hosed reiserfs
Date: Sun, 4 Jul 2004 12:20:21 -0400	[thread overview]
Message-ID: <20040704122021.A25785@tux.org> (raw)
In-Reply-To: <40E0595D.8060106@namesys.com>; from reiser@namesys.com on Mon, Jun 28, 2004 at 10:46:05AM -0700

On Mon, Jun 28, 2004 at 10:46:05AM -0700, Hans Reiser wrote:
>
> www.namesys.com/support.html takes credit cards.  Thanks for being our 
> customer.

OK, done.

Here's the current situation:

My partition doesn't mount.  reiserfsck says there are bad blocks.  The
output of 'debugreiserfs' is as follows:

    Filesystem state: consistency is not checked after last mounting

    Reiserfs super block in block 16 on 0x2148 of format 3.6 with standard journal
    Count of blocks on the device: 4885760
    Number of bitmaps: 150
    Blocksize: 4096
    Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 1095151
    Root block: 9426
    Filesystem is NOT cleanly umounted
    Tree height: 4
    Hash function used to sort names: "r5"
    Objectid map size 602, max 972
    Journal parameters:
	    Device [0x0]
	    Magic [0x4edee6b]
	    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: 2033166
    UUID: af13ddfc-8726-4732-bbf5-db17b6c6671d
    LABEL: 
    Set flags in SB:
	    ATTRIBUTES CLEAN

The partition table looks fine (and hasn't changed in the last 6 months or
so). 

I've tried running dd_rescue to copy the partition over; I've run it both
forward and reverse.  Whenever I run it, it copies for a while and then
hangs my system (Linux 2.6.5-gentoo-r1; also hangs a 2.6.3 kernel).

When I say it hangs, I mean that all other shells and virtual consoles are
non-responsive, and the only thing that works is the reset button on the
front panel.

I also tried /sbin/badblocks which hung the sytem as well.

When I run dd_rescue forward, it copies about 4.5GB (out of 20GB total),
before hanging, resulting in the following file:

4511808 -rw-r-----    1 root     4615569408 Jul  2 23:50 hdf8

I've also run it forward and then reverse on the same file.  It seems to
only copy about 20 Meg or so in the reverse direction.  The most recent
effort resulted in:

4520612 -rw-r-----    1 root     20012073984 Jul  4 12:04 hdf8-2

I've tried giving it starting byte counts of the size (or 1K less), but it
still hangs, just a lot quicker.  Turning on dd_rescue's logging doesn't
help; it appears that the system is locked up before anything is either
written or flushed.

This is a very slow process since I have to reboot after each time I run
it. 

What should I do?

Bruce

  reply	other threads:[~2004-07-04 16:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 15:52 a hosed reiserfs Bruce Israel
2004-06-25 16:06 ` Vitaly Fertman
2004-06-25 16:54   ` Hans Reiser
2004-06-25 18:45     ` Bruce Israel
2004-06-28 17:46       ` Hans Reiser
2004-07-04 16:20         ` Bruce Israel [this message]
2004-07-04 22:56           ` Hans Reiser
2004-07-06 23:17           ` Philip Miller
2004-06-25 19:13   ` Bruce Israel
2004-06-25 16:48 ` Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2004-07-06 16:25 Burnes, James
2004-07-06 19:05 ` Hans Reiser
2004-07-06 22:23   ` Redeeman
2004-07-06 22:40 Burnes, James
2004-07-07  5:54 ` mjt
2004-07-07  7:08   ` Hans Reiser
2004-07-07  7:54     ` mjt
2004-07-08  8:13       ` Hans Reiser
2004-07-08 17:13         ` Philip Miller
2004-07-08 17:29           ` mjt
2004-07-08 19:56             ` Hans Reiser
2004-07-08 19:54           ` Hans Reiser
2004-07-07  9:55   ` Philippe Gramoullé
2004-07-07 19:18     ` Hans Reiser
2004-07-07 19:34       ` mjt
2004-07-07  6:57 ` Hans Reiser

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=20040704122021.A25785@tux.org \
    --to=israel@tux.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.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.