From: Gerrit Hannaert <degerrit@web.de>
To: Vitaly Fertman <vitaly@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Corruption: --fix-fixable results in all nlink values = 0
Date: Sat, 17 Aug 2002 02:54:48 +0200 [thread overview]
Message-ID: <200208170254.48383.degerrit@web.de> (raw)
In-Reply-To: <200208161205.00550.vitaly@namesys.com>
Hi again,
I skimmed over the bad-block-handling page but it's not very clear what you
should do if a filesystem already exists, as is obviously the case with me.
Are these badblock patches in the newer kernels, by the way?
Anyway, my first instinct told me to try Maxtor's 'Powermax' tool, and lo and
behold the 'Advanced Test' here found errors, and 'fixed' them, whatever that
means. (Can you believe these guys make you download a 3MB Windows executable
in order to write a 1.44Mb floppy image which is less than half full?? I had
to bloody install Windows for this... grr....)
Anyway, this time 'reiserfsck --rebuild-tree' finished successfully, and I was
able to see my filesystem for the first time in 2 days and many hours of
sweating.
Here's the pretty impressive summary of errors:
Pass 0:
Loading on-disk bitmap .. ok, 12812325 blocks marked used
Skipping 8749 blocks (super block, journal, bitmaps) 12803576 blocks will be
read
...
"r5" hash is selected
Flushing..done
Read blocks (but not data blocks) 12803576
Leaves among those 86209
- corrected leaves 1
Objectids found 382476
Pass 1 (will try to insert 86209 leaves):
Looking for allocable blocks .. ok
...
Flushing..done
Leaves inserted item by item 170
Pass 3 (semantic):
####### Pass 0 #######
pass0: vpf-10420: block 983630, item (61), make 4459536 4462153 0x1 IND (1)
fixed to DIRECT
"r5" got 382518 hits
####### Pass 1 #######
is_leaf_bad: block 983630L 60-th item (4459536 4462153 0x1 IND (1), len 28,
location 1792 entry count 0, fsck need 0, format new) and the next
one (4459536 4462153 0x7001 IND (1), len 280, location 1512 entry count
65535, fsck need 0, format new) are in wrong order
pass1: (is_leaf_bad) bad leaf (983630)
####### Pass 2 #######
...
Flushing..done
Objects without names 185
Empty lost dirs removed 602
Dirs linked to /lost+found: 12
Dirs without stat data found 60
Files linked to /lost+found 161
Objects having used objectids: 10
files fixed 66
dirs fixed 3
Pass 4
Deleted unreachable items 5
Flushing..done
Syncing..done
###########
reiserfsck finished at Sat Aug 17 02:20:46 2002
I think I will spend the next week working out a better backup solution...
Will Reiserfs4 have better bad block handling than this? When I see all the
trouble involved in rescuing this filesystem, as much as I'm impressed with
it I would think twice about using Reiserfs on any non-redundant (and
certainly IDE) disks from now on. I hope I don't make any enemies by saying
so.
Cheers, and thanks for all your help, especially Vitaly!
- Gerrit
next prev parent reply other threads:[~2002-08-17 0:54 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 18:07 Corruption: --fix-fixable results in all nlink values = 0 Gerrit Hannaert
2002-08-15 18:27 ` Vitaly Fertman
2002-08-15 18:36 ` Gerrit Hannaert
2002-08-15 18:53 ` Vitaly Fertman
2002-08-15 19:06 ` Gerrit Hannaert
2002-08-15 19:44 ` Stefan Fleiter
2002-08-15 20:02 ` Gerrit Hannaert
2002-08-16 10:42 ` Matthias Andree
2002-08-16 17:34 ` Vitaly Fertman
2002-08-17 0:18 ` search for mailing archive on geocrawler bo
2002-08-17 1:03 ` Manuel Krause
2002-08-15 21:29 ` Corruption: --fix-fixable results in all nlink values = 0 Gerrit Hannaert
2002-08-16 8:05 ` Vitaly Fertman
2002-08-16 8:59 ` Gerrit Hannaert
2002-08-16 10:50 ` Matthias Andree
2002-08-16 13:11 ` Gerrit Hannaert
2002-08-16 14:12 ` Matthias Andree
2002-08-16 14:24 ` Hans Reiser
2002-08-16 14:42 ` bscott
2002-08-16 14:58 ` Matthias Andree
2002-08-18 21:08 ` Brian Tinsley
2002-08-19 8:38 ` Hans Reiser
2002-08-17 0:54 ` Gerrit Hannaert [this message]
2002-08-17 10:00 ` Matthias Andree
2002-08-17 19:00 ` Hans Reiser
2002-08-19 5:20 ` Oleg Drokin
2002-08-19 8:42 ` Hans Reiser
2002-08-19 8:46 ` Oleg Drokin
2002-08-19 9:14 ` Hans Reiser
2002-08-19 9:22 ` Oleg Drokin
2002-08-19 10:07 ` Hans Reiser
2002-08-19 10:20 ` Oleg Drokin
2002-08-19 10:27 ` Hans Reiser
2002-08-19 10:40 ` Oleg Drokin
2002-08-19 11:14 ` Hans Reiser
2002-08-19 11:20 ` Oleg Drokin
2002-08-19 13:29 ` Hans Reiser
2002-08-19 13:31 ` Oleg Drokin
2002-08-19 13:55 ` Matthias Andree
2002-08-19 14:25 ` Hans Reiser
2002-08-20 20:24 ` Chris Mason
2002-08-21 6:04 ` Oleg Drokin
2002-08-21 10:33 ` Hans Reiser
2002-08-21 16:17 ` Gerrit Hannaert
2002-08-21 17:14 ` Hans Reiser
2002-08-21 17:33 ` Valdis.Kletnieks
2002-08-21 17:36 ` Hans Reiser
2002-08-22 11:00 ` Vitaly Fertman
2002-08-22 12:55 ` Chris Mason
2002-08-22 13:00 ` Oleg Drokin
2002-08-22 16:42 ` Hans Reiser
2002-08-23 4:56 ` Oleg Drokin
2002-08-23 10:53 ` Hans Reiser
2002-08-23 10:56 ` Oleg Drokin
2002-08-23 11:01 ` 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=200208170254.48383.degerrit@web.de \
--to=degerrit@web.de \
--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.