From: Diego Calleja <grundig@teleline.es>
To: linux-kernel@vger.kernel.org
Cc: Edward Muller <emuller@learningpatterns.com>
Subject: Re: Reiserfs corruption on 2.4.17-rc1!
Date: Wed, 19 Dec 2001 23:17:44 +0100 [thread overview]
Message-ID: <20011219231744.A378@diego> (raw)
In-Reply-To: <20011217002350.D418@diego> <20011217024529.E418@diego> <1008780992.8835.2.camel@akira.learningpatterns.com>
In-Reply-To: <1008780992.8835.2.camel@akira.learningpatterns.com>; from emuller@learningpatterns.com on Wed, Dec 19, 2001 at 17:56:31 +0100
On Wed, 19 Dec 2001 17:56:31 Edward Muller wrote:
> On Sun, 2001-12-16 at 20:45, Diego Calleja wrote:
> [snip]
>
> > As you said, i've tested the drive:
> >
> > root@diego:~# badblocks -n -vv /dev/hdc5
> > attempt to access beyond end of device
> > 16:05: rw=0, want=9671068, limit=9671067
> > 967106456/ 9671067
> > attempt to access beyond end of device
> > 16:05: rw=0, want=9671068, limit=9671067
> > 9671065
> > attempt to access beyond end of device
> > 16:05: rw=0, want=9671068, limit=9671067
> > 9671066
> > done
> > Pass completed, 3 bad blocks found.
> [snip]
>
> From an earlier email...
> Well, I've run badblocks in 2.4.16
> results:
>
>
> root@diego:~# badblocks -n -vv /dev/hdc5
> Initializing random test data
> Checking for bad blocks in non-destructive read-write mode
> From block 0 to 9671067
> Checking for bad blocks (non-destructive read-write test): done
> Pass completed, 0 bad blocks found.
> root@diego:~#
>
>
> So under 2.4.17-rc1 Diego gets the '...access beyond end of device' and
> with 2.4.16 he doesn't.
I've made a partition, about 1500 MB.
-Boot 2.4.16-->fdisk-->reboot-->boot 2.4.16-->mkreiserfs-->badblocks -n -vv
(no "..accesbeyond of device)-->reboot-->boot 2.4.17-rc1-->badblocks -n
-vv--> no "..access beyond of device"
>
> For some reason the badblocks program under 2.4.16 ends at block
> 9671067, while the 2.4.17-rc1 test tries to go beyond that for some
> reason.
>
> Diego, what happens when you run the fsk/try to access /etc/mtab (and
> the like) under 2.4.16?
ls /etc/mtab && reiserfsck --> same results, in 2.4.16 and in 2.4.17-rc1
--my reiserfs partition is now corrupted, there's no difference between
using 2.4.16 or 2.4.17-rc1--
Now I'll compile 2.4.17-rc2 and I'll run reiserfsck --rebuild-tree. I think
this will sove the problem. But nobody knows know why it happened. I'll
try to test if I can reproduce the bug, but I don't think I can.
Diego Calleja
>
>
> --
> -------------------------------
> Edward Muller
> Director of IS
>
> 973-715-0230 (cell)
> 212-487-9064 x115 (NYC)
>
> http://www.learningpatterns.com
> -------------------------------
>
>
next prev parent reply other threads:[~2001-12-19 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011217002350.D418@diego>
2001-12-17 1:45 ` Reiserfs corruption on 2.4.17-rc1! Diego Calleja
2001-12-19 16:56 ` Edward Muller
2001-12-19 22:17 ` Diego Calleja [this message]
2001-12-16 17:48 Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
2001-12-17 1:58 ` Diego Calleja
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] ` <20011218125852.A1159@namesys.com>
[not found] ` <20011218224848.C377@diego>
[not found] ` <20011219095303.A11409@namesys.com>
2001-12-20 0:20 ` 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=20011219231744.A378@diego \
--to=grundig@teleline.es \
--cc=emuller@learningpatterns.com \
--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.