All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Weissenbacher <webmaster@dermichi.com>
To: grossnik.mailinglists@hispeed.ch
Cc: vs@namesys.com, reiserfs-list@namesys.com
Subject: Re: reiserfsck (3.6.19) --rebuild-tree failed
Date: Sat, 09 Sep 2006 17:25:54 +0200	[thread overview]
Message-ID: <4502DD02.500@dermichi.com> (raw)
In-Reply-To: <200609081442.k88Eggwv029431@smtp.hispeed.ch>

Hi,
 > I'm 100% happy. Now it did not stop.
 > Either it would haven been nessesary to run it twice or the new 
version I've got from did the trick.
Good to hear that!
 > I thank you so much!
 > Now I go any buy a new disk!!!
Usually when a disk goes bad you should get a new disk FIRST, then make 
an image from the old disk with dd_rescue and then use fsck. It is much 
safer this way and you don't have to fiddle around with the badblock 
options at all.

Useful links:
[1] http://www.garloff.de/kurt/linux/ddrescue/
[2] http://www.knopper.net/knoppix/
[3] http://www.extremetech.com/article2/0,1697,1928206,00.asp

kind regards,
Michael

  reply	other threads:[~2006-09-09 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 14:42 Re: reiserfsck (3.6.19) --rebuild-tree failed grossnik.mailinglists
2006-09-09 15:25 ` Michael Weissenbacher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08 12:04 grossnik.mailinglists
2006-09-08 12:48 ` Vladimir V. Saveliev
2006-09-08 11:30 grossnik.mailinglists
2006-09-08 11:22 ` Vladimir V. Saveliev
2006-09-08 10:51 grossnik.mailinglists
2006-09-08 10:48 ` Vladimir V. Saveliev
2006-09-08  9:51 grossnik.mailinglists
2006-09-08 10:05 ` Vladimir V. Saveliev

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=4502DD02.500@dermichi.com \
    --to=webmaster@dermichi.com \
    --cc=grossnik.mailinglists@hispeed.ch \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.