From: Matthias Barremaecker <info@mh.be>
To: Valdis.Kletnieks@vt.edu
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs 1300G partition on lvm problem ...
Date: Mon, 30 May 2005 08:17:00 +0200 [thread overview]
Message-ID: <429AAFDC.4050208@mh.be> (raw)
In-Reply-To: <200505292137.j4TLbarw017197@turing-police.cc.vt.edu>
Hi,
Thanx for your reply.
The data is not THAT importend, all our importend data is backuped 4
times, inc. original (well, 3 times now, since the 1300gig machine is
broke).
I did a bit furtur reasearch and maybe this is something to think about
if you use reiserfs :
I did a bad block check and I have 10 bad blocks of 4096bytes on 1300Gig
and ... that is the reason reiserfs will not work anymore.
I guess this sux. I rather have that the data on the bad blocks is just
corupted but the rest is accesseble.
I'm doing a --rebuild-tree with the bad block list. Hopes this works.
Aren't there any tools to substract data from a broken reiserfs partition ?
kind regardes,
Matthias.
Valdis.Kletnieks@vt.edu wrote:
> On Sun, 29 May 2005 21:25:54 +0200, Matthias Barremaecker said:
>
>
>>but that sais it is a fysical drive error
>
>
> Physical drive errors. Your hardware is broken. Isn't much that Reiserfs
> can do about it.
>
>
>>What can I do.
>
>
> 1) Call whoever you get hardware support from.
>
> 2) Be ready to restore from backups.
>
> 3) If you didn't have RAID-5 (or similar) set up, or a good backup, consider
> it a learning experience.
>
> If your data is important enough that you'll care if you lose it, you should take
> steps to make sure you won't lose it... It's that simple.
>
> (Just for the record, if we have important info, it gets at least RAID5, a
> backup to tape or other device, *and* a *second* backup off-site. And my shop
> is far from the most paranoid about such things.)
>
--
Matthias Barremaecker, MH.BE - Arta nv
0495 30 31 72
http://mh.be/
SERVER HOUSING per 1HE € 50 per maand
20Gig traffic, 100Mbit netwerk
Center te Antwerpen.
next prev parent reply other threads:[~2005-05-30 6:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1117392967.29669.ezmlm@namesys.com>
2005-05-29 19:25 ` Reiserfs 1300G partition on lvm problem Matthias Barremaecker
2005-05-29 21:37 ` Valdis.Kletnieks
2005-05-30 6:17 ` Matthias Barremaecker [this message]
2005-05-30 7:37 ` Valdis.Kletnieks
2005-06-24 11:38 ` Minor note FYI Artem B. Bityuckiy
2005-05-31 13:51 ` Reiserfs 1300G partition on lvm problem Dan Oglesby
2005-05-31 14:14 ` Matthias Barremaecker
2005-05-31 15:09 ` Dan Oglesby
2005-05-31 17:31 ` Christian
2005-06-01 6:47 ` Reiserfsck 1300Gig failed with following error Matthias Barremaecker
2005-06-01 10:06 ` Vitaly Fertman
2005-06-01 10:57 ` Matthias Barremaecker
2005-06-01 11:12 ` Vitaly Fertman
2005-06-01 12:28 ` Matthias Barremaecker
2005-06-01 12:52 ` Vitaly Fertman
2005-06-01 13:32 ` Matthias Barremaecker
2005-06-02 14:37 ` 13000Gig partition badblock check is the same -- do a reiserfsck again ? Matthias Barremaecker
2005-06-02 14:28 ` Dan Oglesby
2005-06-02 15:16 ` Matthias Barremaecker
2005-06-02 15:04 ` Dan Oglesby
2005-06-02 15:28 ` Matthias Barremaecker
2005-06-02 21:03 ` Valdis.Kletnieks
2005-06-02 21:32 ` Dan Oglesby
2005-06-03 7:10 ` 13000Gig partition badblock check is the same -- do a reiserfsck again ? -> ran badblocks Matthias Barremaecker
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=429AAFDC.4050208@mh.be \
--to=info@mh.be \
--cc=Valdis.Kletnieks@vt.edu \
--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.