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: Thu, 15 Aug 2002 20:36:35 +0200 [thread overview]
Message-ID: <200208152036.35333.degerrit@web.de> (raw)
In-Reply-To: <200208152227.21766.vitaly@namesys.com>
>
> why did you decided to run fix-fixable? You run --check just before it
> and it said to run --fix-fixable or what?
Er... I confess it was just a hunch, I did run --check but as I recall it did
not tell me to, it did say there were corruptions in any case. The filesystem
needed fixing and fix-fixable seemed less drastic than rebuild... (The
undeletable files were basically a thorn in my eye and I just wanted to be
sure there were no corruptions other than these clearly visible ones).
>
> Did reiserfsck finish its work or (was)stopped/failed?
Yes, reiserfsck finished properly.
> > What went wrong here?
> > Will reiserfsck --rebuild-tree fix this? Or is the error some compilation
> > thing? What are my chances to recover the filesystem?
>
> Chances are good. No data ware lost and I am checking how reiserfsck handle
> direcory nlinks now.
It would be nice to recover most of the fs. I'd probably be better using some
standard, tested reiserfsck-binaries over my own this time I suppose?
Thanks a lot, Vitaly.
- Gerrit
next prev parent reply other threads:[~2002-08-15 18:36 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 [this message]
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
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=200208152036.35333.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.