From: Diego Calleja <grundig@teleline.es>
To: linux-kernel@vger.kernel.org
Cc: Jurgen Botz <jurgen@botz.org>
Subject: Re: Reiserfs corruption on 2.4.17-rc1!
Date: Tue, 18 Dec 2001 00:33:59 +0100 [thread overview]
Message-ID: <20011218003359.A555@diego> (raw)
In-Reply-To: <20011217025856.A1649@diego> <13425.1008580831@nova.botz.org>
In-Reply-To: <13425.1008580831@nova.botz.org>; from jurgen@botz.org on Mon, Dec 17, 2001 at 10:20:31 +0100
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:~#
It takes about 6 hours to check this...but perhaps I should repeat again
in 2.4.17-rc1.
It works in 2.4.16, but ls /hdc5/etc
Dec 18 00:22:32 diego kernel: reiserfs: checking transaction log (device
16:05) ...
Dec 18 00:22:32 diego kernel: Using r5 hash to sort names
Dec 18 00:22:32 diego kernel: ReiserFS version 3.6.25
Dec 18 00:22:40 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:40 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:40 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68722 0x0 SD]
Dec 18 00:22:40 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:40 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:40 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 18 00:22:41 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:41 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:41 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 64508 0x0 SD]
Dec 18 00:22:41 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:41 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:41 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 63049 0x0 SD]
Dec 18 00:22:41 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:41 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:41 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68673 0x0 SD]
Dec 18 00:22:41 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 18 00:22:41 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 18 00:22:41 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68377 0x0 SD]
This is my opinion:
-Something (reiserfs, anything) has caused fs corruption
-It should be repaired by reiserfsck, but it's broken :-((
-This corruption should NOT have happened, reiserfsck shouldn't
have to be used.
-I'm not a kernel hacker, so I can't try anything...what I know is
that
/etc in hc5 doesn't work. /usr, /var....works correctly.
Well, I'd like to know what's happened in my drive. Can somebody try to
give an explanation?
Diego Calleja
next prev parent reply other threads:[~2001-12-17 23:34 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
2001-12-17 21:01 ` Sakari Ailus
[not found] ` <13425.1008580831@nova.botz.org>
2001-12-17 23:33 ` Diego Calleja [this message]
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=20011218003359.A555@diego \
--to=grundig@teleline.es \
--cc=jurgen@botz.org \
--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.