All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Calleja <grundig@teleline.es>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs corruption on 2.4.17-rc1!
Date: Mon, 17 Dec 2001 02:58:56 +0100	[thread overview]
Message-ID: <20011217025856.A1649@diego> (raw)
In-Reply-To: <20011216184836.A418@diego> <20011216211208.D5226@vestdata.no>
In-Reply-To: <20011216211208.D5226@vestdata.no>; from kernel@ragnark.vestdata.no on Sun, Dec 16, 2001 at 21:12:08 +0100


On Sun, 16 Dec 2001 21:12:08 Ragnar Kjørstad wrote:
> On Sun, Dec 16, 2001 at 06:48:36PM +0100, Diego Calleja wrote:
> > Dec 16 17:40:40 diego kernel: vs-13070: reiserfs_read_inode2: i/o
> failure
> > occurred trying to find stat data of [4160 68669 0x0 SD]
> 
> It appears you have a broken harddrive. You can verify this with the
> "badblocks" program

badblocks -n (non-destructive write-test) -vv /dev/hdc5
results in:
attempt to access beyond end of device
16:05: rw=0, want=9671068, limit=9671067
attempt to access beyond end of device
16:05: rw=0, want=9671068, limit=9671067
attempt to access beyond end of device
16:05: rw=0, want=9671068, limit=9671067
3 bad blocks found

This means it's broken? 
More info: (hdc5 is the drive):

Dec 16 17:48:12 diego kernel: hdc: 78165360 sectors (40021 MB) w/2048KiB
Cache, CHS=77545/16/63
Dec 16 17:48:12 diego kernel: Partition check:
Dec 16 17:48:12 diego kernel:  hdc: [DM6:DDO] [remap +63] [4865/255/63]
hdc1 < hdc5 hdc6 > hdc2

cat /proc/partitions:
major minor  #blocks  name

  22     0   39082648 hdc
  22     1          1 hdc1
  22     2   10241437 hdc2
  22     5    9671067 hdc5
  22     6      96358 hdc6

fdisk -lu /dev/hdc:
Disk /dev/hdc: 255 heads, 63 sectors, 4865 cylinders
Units = sectors of 1 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1            63  19535039   9767488+   5  Extended
/dev/hdc2   *  19535040  40017914  10241437+  83  Linux
/dev/hdc5   *       126  19342259   9671067   83  Linux
/dev/hdc6      19342323  19535039     96358+  82  Linux swap


The drive is a seagate 40 GB UDMA 100, the bios doesn't support drives >
8'4 GB,
I've to boot from a seagate 2 GB drive, which have real bad-blocks.(IT was
my fault).
And when I used it with linux, the error messages were very different (and
they are different today).
Those messages doesn't appears here. I don't think it's broken.
If someone can confirm that it's broken, please mail me. I bought it a
month ago and I can change it.

> 
> 
> -- 
> Ragnar Kjørstad
> Big Storage
> 



  reply	other threads:[~2001-12-17  1:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 17:48 Reiserfs corruption on 2.4.17-rc1! Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
2001-12-17  1:58   ` Diego Calleja [this message]
2001-12-17 21:01     ` Sakari Ailus
     [not found]     ` <13425.1008580831@nova.botz.org>
2001-12-17 23:33       ` Diego Calleja
2001-12-18  5:01         ` Ross Vandegrift
2001-12-18  6:19           ` Jurgen Botz
2001-12-18 21:45           ` Diego Calleja
     [not found]         ` <15391.12150.650359.33792@laputa.namesys.com>
     [not found]           ` <20011218220828.A381@diego>
2001-12-18 21:11             ` [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!] Diego Calleja
2001-12-19  9:18               ` Nikita Danilov
     [not found]           ` <3C1F3FDA.5050601@namesys.com>
2001-12-18 21:35             ` [reiserfs-list] Re: Reiserfs corruption on 2.4.17-rc1! Diego Calleja
     [not found]         ` <20011218125852.A1159@namesys.com>
     [not found]           ` <20011218224848.C377@diego>
     [not found]             ` <20011219095303.A11409@namesys.com>
2001-12-20  0:20               ` Diego Calleja
     [not found] <20011217002350.D418@diego>
2001-12-17  1:45 ` Diego Calleja
2001-12-19 16:56   ` Edward Muller
2001-12-19 22:17     ` Diego Calleja

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=20011217025856.A1649@diego \
    --to=grundig@teleline.es \
    --cc=linux-kernel@vger.kernel.org \
    /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.