From: Oleg Drokin <green@namesys.com>
To: grobe@gmx.net
Cc: reiserfs-list@namesys.com
Subject: Re: corrupted fs: bitmap does not match to the correct one....
Date: Wed, 15 May 2002 18:06:09 +0400 [thread overview]
Message-ID: <20020515180609.A2073@namesys.com> (raw)
In-Reply-To: <19890.1021471126@www22.gmx.net>
Hello!
On Wed, May 15, 2002 at 03:58:46PM +0200, grobe@gmx.net wrote:
> > > I have a bad problem with my reiserfs. I got a lot of SCSI-errors in the
> > > Hm. SCSI errors are bad, and you have performed everything on the same
> > hardware?
> Yes, a Serveraid 4M with a EXP15 Raid 5 attached. Curent kernel (2.4.16),
> current firmware, current driver (and UNCHANGED!).
> > What kind of errors was there, by the way?
> May 15 12:54:01 Zeus kernel: I/O error: dev 08:11, sector 211045693
> [... a lot of these ...]
Ah, failing hardware.
Unfortunatelly we only deal with failing harddrive based on
http://namesys.com/support.html terms.
> > What version of reiserfsprogs was used?
> 3.x.0j
That's way too old.
> > How about more error messages about scsi errors in the logs?
> As I mentioned, I can't mount any more, so no more messages...
Hm. So you read corrupted on-disk infortmation with reiserfsck, then wrote it
back. That'd going to hurt for sure.
> > There is always a chance, another question (rather important in your case,
> > it seems) is what option would be faster.
> That's what I need to know ;-) In fact, the backup is on an IDE-Array, I
> dont get more than 10MB/s from the backup server, and i have 300GB of data...
I'd say you'd better stay using your backups (on a different hard drive(s)).
Also you probably want to ask whoever sold you the failing harddrive to replace
it.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-15 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 12:59 corrupted fs: bitmap does not match to the correct one grobe
2002-05-15 13:08 ` Oleg Drokin
2002-05-15 13:58 ` grobe
2002-05-15 14:06 ` Oleg Drokin [this message]
2002-05-15 15:56 ` grobe
2002-05-15 17:04 ` Valdis.Kletnieks
2002-05-16 5:13 ` Oleg Drokin
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=20020515180609.A2073@namesys.com \
--to=green@namesys.com \
--cc=grobe@gmx.net \
--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.