From: Bruce Israel <israel@tux.org>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: a hosed reiserfs
Date: Fri, 25 Jun 2004 15:13:04 -0400 [thread overview]
Message-ID: <20040625151304.B5159@tux.org> (raw)
In-Reply-To: <200406252006.55426.vitaly@namesys.com>; from vitaly@namesys.com on Fri, Jun 25, 2004 at 08:06:55PM +0400
On Fri, Jun 25, 2004 at 08:06:55PM +0400, Vitaly Fertman wrote:
> Hello,
>
> On Friday 25 June 2004 19:52, Bruce Israel wrote:
>
> It would be better to use a newer version of reiserfsprogs.
OK, when I get home I'll download and install the latest. 3.6.17?
> > bread: Cannot read the block (4161536): (Input/output error).
>
> what do you see in the syslog? any related message about IO
> error or about an access beyond end of the device? It could also
> be the case that the partition end is beyond the harddrive size.
> check it please.
>
> --
No, that's not the case. /dev/hdf8 has the problems, but the partition
right after it, hdf9, is also a reiserfs partion, and it doesn't have any
problems. The partion table for the disk is below.
I'll check out the logs, though I think I had looked in them at the time
and found nothing informative.
Bruce
root@exsolent / # fdisk /dev/hdf
The number of cylinders for this disk is set to 9729.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hdf: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdf1 1 13 104391 83 Linux
/dev/hdf2 14 75 498015 82 Linux swap
/dev/hdf3 76 9729 77545755 5 Extended
/dev/hdf5 76 1292 9775521 83 Linux
/dev/hdf6 1293 2509 9775521 83 Linux
/dev/hdf7 2510 3726 9775521 83 Linux
/dev/hdf8 3727 6159 19543041 83 Linux
/dev/hdf9 6160 9729 28675993+ 83 Linux
next prev parent reply other threads:[~2004-06-25 19:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 15:52 a hosed reiserfs Bruce Israel
2004-06-25 16:06 ` Vitaly Fertman
2004-06-25 16:54 ` Hans Reiser
2004-06-25 18:45 ` Bruce Israel
2004-06-28 17:46 ` Hans Reiser
2004-07-04 16:20 ` Bruce Israel
2004-07-04 22:56 ` Hans Reiser
2004-07-06 23:17 ` Philip Miller
2004-06-25 19:13 ` Bruce Israel [this message]
2004-06-25 16:48 ` Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2004-07-06 16:25 Burnes, James
2004-07-06 19:05 ` Hans Reiser
2004-07-06 22:23 ` Redeeman
2004-07-06 22:40 Burnes, James
2004-07-07 5:54 ` mjt
2004-07-07 7:08 ` Hans Reiser
2004-07-07 7:54 ` mjt
2004-07-08 8:13 ` Hans Reiser
2004-07-08 17:13 ` Philip Miller
2004-07-08 17:29 ` mjt
2004-07-08 19:56 ` Hans Reiser
2004-07-08 19:54 ` Hans Reiser
2004-07-07 9:55 ` Philippe Gramoullé
2004-07-07 19:18 ` Hans Reiser
2004-07-07 19:34 ` mjt
2004-07-07 6:57 ` 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=20040625151304.B5159@tux.org \
--to=israel@tux.org \
--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.