From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Jeff Breidenbach <jbreiden@parc.com>, reiserfs-list@namesys.com
Subject: Re: disk or reiserfs problem?
Date: Mon, 02 Jun 2003 22:36:00 +0400 [thread overview]
Message-ID: <3EDB9910.7040005@namesys.com> (raw)
In-Reply-To: <20030529054511.GA30925@namesys.com>
Oleg Drokin wrote:
>Hello!
>
>On Wed, May 28, 2003 at 01:07:27PM -0700, Jeff Breidenbach wrote:
>
>
>>This is after a hard (power switch) reboot (due to I/O errors). The
>>disk in question has about 125 GB of data on a single 200GB reiserfs
>>partition. Do people think the disk is toast, or is this possibly some
>>correctable filesystem problem? The machine is remote, so I can't
>>hdb1: bad access: block=35, count=5
>>end_request: I/O error, dev 03:41 (hdb), sector 35
>>
>>
>
>Looks like disk have gone bad. If you are lucky enough, some of the data
>still can be recovered. Try to copy entire disk into a file/to another
>disk to see how much bad sectors are there.
>
>Bye,
> Oleg
>
>
>
>
You should provide more details in such advice, such as telling him
about dd_rescue and why it is better than dd, etc. You should also
explain that if it is only a few blocks that are bad, writing to the bad
blocks can make them go away most of the time (the drive will remap them).
--
Hans
next prev parent reply other threads:[~2003-06-02 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 20:07 disk or reiserfs problem? Jeff Breidenbach
2003-05-29 5:45 ` Oleg Drokin
2003-06-02 18:36 ` Hans Reiser [this message]
2003-06-02 20:00 ` Jeff Breidenbach
2003-06-03 5:33 ` Oleg Drokin
2003-06-03 17:49 ` Prereading block device doesn't help filesystems Mike Fedyk
2003-06-03 18:19 ` Chris Mason
2003-06-05 13:20 ` disk or reiserfs problem? Hans Reiser
2003-06-05 13:38 ` Nikita Danilov
2003-06-03 5:23 ` 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=3EDB9910.7040005@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=jbreiden@parc.com \
--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.