Reiserfs corruption on 2.4.17-rc1!
Quoted 6 lines
Quoted 1 line
Dec 16 17:40:40 diego kernel: vs-13070: reiserfs_read_inode2: i/ofailure
Quoted 1 line
occurred trying to find stat data of [4160 68669
0x0SD]It appears you have a broken harddrive. You can verify this with the "badblocks" program
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.
This means it's broken?, affected partition is hdc5
Dec 16 16:54:41 diego kernel: hdc: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=77545/16/63 Dec 16 16:54:41 diego kernel: Partition check: Dec 16 16:54:41 diego kernel: hdc: [DM6:DDO] [remap +63] [4865/255/63]
hdc1 < hdc5 hdc6 > hdc2
root@diego:~# 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
root@diego:~# 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 3 0 2062368 hda 3 1 42304 hda1 3 2 2018016 hda2
This drive is a seagate UDMA 40 GB. My BIOS doesn't
support drives > 8'4 GB, I've to boot from an old 2 GB seagate IDE drive. This old drive have bad sectors.(It was my fault). When I used it, the bad blocks message was very different. Shouldn't the bad block be reported by the IDE driver?.
Can someone say me if this drive is really broken?. I've bought it a month ago,
i could try to change it.
On Sun, 2001-12-16 at 20:45, Diego Calleja wrote:
[snip]
Quoted 14 lines
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]
Quoted 1 line
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
Quoted 1 line
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.
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?
Signature · 9 lines
------------------------------- Edward Muller Director of IS 973-715-0230 (cell) 212-487-9064 x115 (NYC) http://www.learningpatterns.com -------------------------------
Quoted 33 lines · On Wed, 19 Dec 2001 17:56:31 Edward Muller wrote:
On Sun, 2001-12-16 at 20:45, Diego Calleja wrote:
[snip]Quoted 14 lines
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:~#
Quoted 2 lines
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"
Quoted 7 lines
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
Quoted 14 lines
Signature · 10 lines
-- ------------------------------- Edward Muller Director of IS 973-715-0230 (cell) 212-487-9064 x115 (NYC) http://www.learningpatterns.com -------------------------------