* Reiserfs corruption on 2.4.17-rc1!
@ 2001-12-16 17:48 Diego Calleja
2001-12-16 17:57 ` Diego Calleja
2001-12-16 20:12 ` Ragnar Kjørstad
0 siblings, 2 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-16 17:48 UTC (permalink / raw)
To: linux-kernel
Problem:
I've boot up my linux box (2.4.17-rc1). I was readin the lkml when
I tried to mount my vfat partition on /win to listen mp3. (as a normal
user, of course). But I couldn't mount it. Reason?:
ls: mtab: permission denied
Then I log as root, but ls -l /etc/mtab said:
ls: mtab: permission denied
any chmod in /etc/mtab: (as root)
chmod: getting attributes of mtab: Permission denied
/etc/mtab is a reiserfs partition.
After this, the filesystem started to fail a lot in all other programs
Here is /var/log/messages. As you'll see, I tried to boot another time with
2.4.5-pre10 (This was my fault, I boot unstable kernels in another
partition,
where I'm running now and where I tried to run reiserfsck). I'll paste
bootup messages, too. I think I did a very,very hard reboot before this,
i'm not sure (shutting it down the power, without syncing)
---------------------------------------------------
Dec 16 16:54:41 diego kernel: Linux version 2.4.17-rc1 (root@diego) (gcc
version 2.95.4 20011006 (Debian prerelease)) #1 Fri Dec 14 00:37:21 CET
2001
Dec 16 16:54:41 diego kernel: BIOS-provided physical RAM map:
Dec 16 16:54:41 diego kernel: BIOS-e820: 0000000000000000 -
00000000000a0000 (usable)
Dec 16 16:54:41 diego kernel: BIOS-e820: 00000000000f0000 -
0000000000100000 (reserved)
Dec 16 16:54:41 diego kernel: BIOS-e820: 0000000000100000 -
0000000002000000 (usable)
Dec 16 16:54:41 diego kernel: BIOS-e820: 00000000ffff0000 -
0000000100000000 (reserved)
Dec 16 16:54:41 diego kernel: On node 0 totalpages: 8192
Dec 16 16:54:41 diego kernel: zone(0): 4096 pages.
Dec 16 16:54:41 diego kernel: zone(1): 4096 pages.
Dec 16 16:54:41 diego kernel: zone(2): 0 pages.
Dec 16 16:54:41 diego kernel: Kernel command line: ro root=/dev/hdc5
vga=0x30a
Dec 16 16:54:41 diego kernel: Initializing CPU#0
Dec 16 16:54:41 diego kernel: Detected 200.454 MHz processor.
Dec 16 16:54:41 diego kernel: Console: colour VGA+ 132x43
Dec 16 16:54:41 diego kernel: Calibrating delay loop... 399.76 BogoMIPS
Dec 16 16:54:41 diego kernel: Memory: 30444k/32768k available (807k kernel
code, 1940k reserved, 193k data, 180k init, 0k highmem)
Dec 16 16:54:41 diego kernel: Checking if this processor honours the WP bit
even in supervisor mode... Ok.
Dec 16 16:54:41 diego kernel: Dentry-cache hash table entries: 4096 (order:
3, 32768 bytes)
Dec 16 16:54:41 diego kernel: Inode-cache hash table entries: 2048 (order:
2, 16384 bytes)
Dec 16 16:54:41 diego kernel: Mount-cache hash table entries: 512 (order:
0, 4096 bytes)
Dec 16 16:54:41 diego kernel: Buffer-cache hash table entries: 1024 (order:
0, 4096 bytes)
Dec 16 16:54:41 diego kernel: Page-cache hash table entries: 8192 (order:
3, 32768 bytes)
Dec 16 16:54:41 diego kernel: CPU: Cyrix 6x86MX 3x Core/Bus Clock stepping
07
Dec 16 16:54:41 diego kernel: Checking 'hlt' instruction... OK.
Dec 16 16:54:41 diego kernel: POSIX conformance testing by UNIFIX
Dec 16 16:54:41 diego kernel: mtrr: v1.40 (20010327) Richard Gooch
(rgooch@atnf.csiro.au)
Dec 16 16:54:41 diego kernel: mtrr: detected mtrr type: Cyrix ARR
Dec 16 16:54:41 diego kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb3b0,
last bus=0
Dec 16 16:54:41 diego kernel: PCI: Using configuration type 1
Dec 16 16:54:41 diego kernel: PCI: Probing PCI hardware
Dec 16 16:54:41 diego kernel: Linux NET4.0 for Linux 2.4
Dec 16 16:54:41 diego kernel: Based upon Swansea University Computer
Society NET3.039
Dec 16 16:54:41 diego kernel: Initializing RT netlink socket
Dec 16 16:54:41 diego kernel: Starting kswapd
Dec 16 16:54:41 diego kernel: pty: 256 Unix98 ptys configured
Dec 16 16:54:41 diego kernel: block: 64 slots per queue, batch=16
Dec 16 16:54:41 diego kernel: Uniform Multi-Platform E-IDE driver Revision:
6.31
Dec 16 16:54:41 diego kernel: ide: Assuming 33MHz system bus speed for PIO
modes; override with idebus=xx
Dec 16 16:54:41 diego kernel: SIS5513: IDE controller on PCI bus 00 dev 09
Dec 16 16:54:41 diego kernel: SIS5513: chipset revision 193
Dec 16 16:54:41 diego kernel: SIS5513: not 100%% native mode: will probe
irqs later
Dec 16 16:54:41 diego kernel: ide0: BM-DMA at 0x1000-0x1007, BIOS
settings: hda:pio, hdb:pio
Dec 16 16:54:41 diego kernel: ide1: BM-DMA at 0x1008-0x100f, BIOS
settings: hdc:pio, hdd:pio
Dec 16 16:54:41 diego kernel: hda: ST32122A, ATA DISK drive
Dec 16 16:54:41 diego kernel: hdb: LG CD-ROM CRD-8522B, ATAPI CD/DVD-ROM
drive
Dec 16 16:54:41 diego kernel: hdc: ST340016A, ATA DISK drive
Dec 16 16:54:41 diego kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec 16 16:54:41 diego kernel: ide1 at 0x170-0x177,0x376 on irq 15
Dec 16 16:54:41 diego kernel: hda: 4124736 sectors (2112 MB) w/128KiB
Cache, CHS=1023/64/63
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: hda: hda1 hda2
Dec 16 16:54:41 diego kernel: hdc: [DM6:DDO] [remap +63] [4865/255/63]
hdc1 < hdc5 hdc6 > hdc2
Dec 16 16:54:41 diego kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Dec 16 16:54:41 diego kernel: IP Protocols: ICMP, UDP, TCP
Dec 16 16:54:41 diego kernel: IP: routing cache hash table of 512 buckets,
4Kbytes
Dec 16 16:54:41 diego kernel: TCP: Hash tables configured (established 2048
bind 2048)
Dec 16 16:54:41 diego kernel: NET4: Unix domain sockets 1.0/SMP for Linux
NET4.0.
Dec 16 16:54:41 diego kernel: reiserfs: checking transaction log (device
16:05) ...
Dec 16 16:54:41 diego kernel: Using r5 hash to sort names
Dec 16 16:54:41 diego kernel: ReiserFS version 3.6.25
Dec 16 16:54:41 diego kernel: VFS: Mounted root (reiserfs filesystem)
readonly.
Dec 16 16:54:41 diego kernel: Freeing unused kernel memory: 180k freed
Dec 16 16:54:41 diego kernel: Adding Swap: 96352k swap-space (priority -1)
Dec 16 16:54:41 diego kernel: Real Time Clock Driver v1.10e
Dec 16 16:54:41 diego kernel: Serial driver version 5.05c (2001-07-08) with
MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
Dec 16 16:54:41 diego kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Dec 16 16:54:41 diego kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Dec 16 16:54:41 diego kernel: ttyS03 at 0x02e8 (irq = 3) is a 16550A
Dec 16 16:54:45 diego kernel: parport0: PC-style at 0x378 [PCSPP]
Dec 16 16:54:45 diego kernel: lp0: using parport0 (polling).
Dec 16 16:54:45 diego kernel: lp0: compatibility mode
Dec 16 16:54:45 diego last message repeated 2 times
Dec 16 16:54:59 diego kernel: CSLIP: code copyright 1989 Regents of the
University of California
Dec 16 16:54:59 diego kernel: PPP generic driver version 2.4.1
Dec 16 16:55:19 diego kernel: [drm] Initialized tdfx 1.0.0 20010216 on
minor 0
Dec 16 16:54:59 diego pppd[259]: pppd 2.4.1 started by root, uid 0
<pppd dialing>
Dec 16 17:14:40 diego -- MARK --
Dec 16 17:34:40 diego -- MARK --
Dec 16 17:40:40 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:40 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
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]
Dec 16 17:40:40 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:40 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
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]
Dec 16 17:40:41 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:41 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:40:41 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 16 17:40:45 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:45 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:40:45 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 16 17:40:47 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:47 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:40:47 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 16 17:40:55 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:40:55 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:40:55 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 16 17:41:28 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:41:28 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:41:28 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68722 0x0 SD]
Dec 16 17:41:28 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:41:28 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:41:28 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 64508 0x0 SD]
Dec 16 17:41:28 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:41:28 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:41:28 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 63049 0x0 SD]
Dec 16 17:41:28 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:41:28 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:41:28 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68673 0x0 SD]
Dec 16 17:41:28 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:41:28 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:41:28 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68377 0x0 SD]
Dec 16 17:41:36 diego kernel: SysRq : Emergency Sync
Dec 16 17:41:36 diego kernel: Syncing device 16:05 ... OK
Dec 16 17:41:36 diego kernel: Done.
Dec 16 17:41:45 diego kernel: SysRq : HELP : loglevel0-8 reBoot tErm kIll
saK killalL showMem showPc unRaw Sync showTasks Unmount
Dec 16 17:42:43 diego syslogd 1.4.1#8: restart.
Dec 16 17:42:43 diego kernel: klogd 1.4.1#8, log source = /proc/kmsg
started.
Dec 16 17:42:43 diego kernel: Cannot find map file.
Dec 16 17:42:43 diego kernel: Loaded 5 symbols from 1 module.
Dec 16 17:42:43 diego kernel: Linux version 2.5.1-pre10 (root@diego) (gcc
version 2.95.4 20011006 (Debian prerelease)) #1 Tue Dec 11 21:20:18 CET
2001
Dec 16 17:42:43 diego kernel: BIOS-provided physical RAM map:
Dec 16 17:42:43 diego kernel: BIOS-e820: 0000000000000000 -
00000000000a0000 (usable)
Dec 16 17:42:43 diego kernel: BIOS-e820: 00000000000f0000 -
0000000000100000 (reserved)
Dec 16 17:42:43 diego kernel: BIOS-e820: 0000000000100000 -
0000000002000000 (usable)
Dec 16 17:42:43 diego kernel: BIOS-e820: 00000000ffff0000 -
0000000100000000 (reserved)
Dec 16 17:42:43 diego kernel: On node 0 totalpages: 8192
Dec 16 17:42:43 diego kernel: zone(0): 4096 pages.
Dec 16 17:42:43 diego kernel: zone(1): 4096 pages.
Dec 16 17:42:43 diego kernel: zone(2): 0 pages.
Dec 16 17:42:43 diego kernel: Initializing CPU#0
Dec 16 17:42:43 diego kernel: Detected 200.457 MHz processor.
Dec 16 17:42:43 diego kernel: Console: colour VGA+ 132x43
Dec 16 17:42:43 diego kernel: Calibrating delay loop... 399.76 BogoMIPS
Dec 16 17:42:43 diego kernel: Memory: 30440k/32768k available (801k kernel
code, 1944k reserved, 192k data, 180k init, 0k highmem)
Dec 16 17:42:43 diego kernel: Checking if this processor honours the WP bit
even in supervisor mode... Ok.
Dec 16 17:42:43 diego kernel: Dentry-cache hash table entries: 4096 (order:
3, 32768 bytes)
Dec 16 17:42:43 diego kernel: Inode-cache hash table entries: 2048 (order:
2, 16384 bytes)
Dec 16 17:42:43 diego kernel: Mount-cache hash table entries: 512 (order:
0, 4096 bytes)
Dec 16 17:42:43 diego kernel: Buffer-cache hash table entries: 1024 (order:
0, 4096 bytes)
Dec 16 17:42:43 diego kernel: Page-cache hash table entries: 8192 (order:
3, 32768 bytes)
Dec 16 17:42:43 diego kernel: CPU: Cyrix 6x86MX 3x Core/Bus Clock stepping
07
Dec 16 17:42:43 diego kernel: Checking 'hlt' instruction... OK.
Dec 16 17:42:43 diego kernel: POSIX conformance testing by UNIFIX
Dec 16 17:42:43 diego kernel: mtrr: v1.40 (20010327) Richard Gooch
(rgooch@atnf.csiro.au)
Dec 16 17:42:43 diego kernel: mtrr: detected mtrr type: Cyrix ARR
Dec 16 17:42:43 diego kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb3b0,
last bus=0
Dec 16 17:42:43 diego kernel: PCI: Using configuration type 1
Dec 16 17:42:43 diego kernel: PCI: Probing PCI hardware
Dec 16 17:42:43 diego kernel: Linux NET4.0 for Linux 2.4
Dec 16 17:42:43 diego kernel: Based upon Swansea University Computer
Society NET3.039
Dec 16 17:42:43 diego kernel: Starting kswapd
Dec 16 17:42:43 diego kernel: BIO: pool of 256 setup, 14Kb (56 bytes/bio)
Dec 16 17:42:43 diego kernel: biovec: init pool 0, 1 entries, 12 bytes
Dec 16 17:42:43 diego kernel: biovec: init pool 1, 4 entries, 48 bytes
Dec 16 17:42:43 diego kernel: biovec: init pool 2, 16 entries, 192 bytes
Dec 16 17:42:43 diego kernel: biovec: init pool 3, 64 entries, 768 bytes
Dec 16 17:42:43 diego kernel: biovec: init pool 4, 128 entries, 1536 bytes
Dec 16 17:42:43 diego kernel: biovec: init pool 5, 256 entries, 3072 bytes
Dec 16 17:42:43 diego kernel: pty: 256 Unix98 ptys configured
Dec 16 17:42:43 diego kernel: block: 64 slots per queue, batch=16
Dec 16 17:42:43 diego kernel: Uniform Multi-Platform E-IDE driver Revision:
6.32
Dec 16 16:54:41 diego kernel: ide: Assuming 33MHz system bus speed for PIO
modes; override with idebus=xx
Dec 16 17:42:43 diego kernel: SIS5513: IDE controller on PCI slot 00:01.1
Dec 16 17:42:43 diego kernel: SIS5513: chipset revision 193
Dec 16 17:42:43 diego kernel: SIS5513: not 100%% native mode: will probe
irqs later
Dec 16 17:42:43 diego kernel: ide0: BM-DMA at 0x1000-0x1007, BIOS
settings: hda:pio, hdb:pio
Dec 16 17:42:43 diego kernel: ide1: BM-DMA at 0x1008-0x100f, BIOS
settings: hdc:pio, hdd:pio
Dec 16 17:42:43 diego kernel: hda: ST32122A, ATA DISK drive
Dec 16 17:42:43 diego kernel: hdb: LG CD-ROM CRD-8522B, ATAPI CD/DVD-ROM
drive
Dec 16 17:42:43 diego kernel: hdc: ST340016A, ATA DISK drive
Dec 16 17:42:43 diego kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec 16 17:42:43 diego kernel: ide1 at 0x170-0x177,0x376 on irq 15
Dec 16 17:42:43 diego kernel: hda: 4124736 sectors (2112 MB) w/128KiB
Cache, CHS=1023/64/63
Dec 16 17:42:43 diego kernel: hdc: 78165360 sectors (40021 MB) w/2048KiB
Cache, CHS=77545/16/63
Dec 16 17:42:43 diego kernel: Partition check:
Dec 16 17:42:43 diego kernel: hda: hda1 hda2
Dec 16 17:42:43 diego kernel: hdc: [DM6:DDO] [remap +63] [4865/255/63]
hdc1 < hdc5 hdc6 > hdc2
Dec 16 17:42:43 diego kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Dec 16 17:42:43 diego kernel: IP Protocols: ICMP, UDP, TCP
Dec 16 17:42:43 diego kernel: IP: routing cache hash table of 512 buckets,
4Kbytes
Dec 16 17:42:43 diego kernel: TCP: Hash tables configured (established 2048
bind 2048)
Dec 16 17:42:43 diego kernel: NET4: Unix domain sockets 1.0/SMP for Linux
NET4.0.
Dec 16 17:42:43 diego kernel: reiserfs: checking transaction log (device
16:05) ...
Dec 16 17:42:43 diego kernel: Using r5 hash to sort names
Dec 16 17:42:43 diego kernel: ReiserFS version 3.6.25
Dec 16 17:42:43 diego kernel: VFS: Mounted root (reiserfs filesystem)
readonly.
Dec 16 17:42:43 diego kernel: Freeing unused kernel memory: 180k freed
Dec 16 17:42:43 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:42:43 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:42:43 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68669 0x0 SD]
Dec 16 17:42:43 diego kernel: Adding Swap: 96352k swap-space (priority -1)
Dec 16 17:42:43 diego kernel: Real Time Clock Driver v1.10e
Dec 16 17:42:43 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:42:43 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:42:43 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 68673 0x0 SD]
Dec 16 17:42:47 diego /usr/sbin/gpm[247]: Removing stale pid file
/var/run/gpm.pid
Dec 16 17:42:48 diego kernel: is_tree_node: node level 18771 does not match
to the expected one 1
Dec 16 17:42:48 diego kernel: vs-5150: search_by_key: invalid format found
in block 10667. Fsck?
Dec 16 17:42:48 diego kernel: vs-13070: reiserfs_read_inode2: i/o failure
occurred trying to find stat data of [4160 63049 0x0 SD]
Dec 16 17:42:48 diego kernel: Kernel logging (proc) stopped.
I did a Sysrq + sync and sysrq + reboot, I've tried to
do fsck, but:
<-------------reiserfsck, 2001------------->
reiserfsprogs 3.x.0j
Will read-only check consistency of the partition
Will put log info to 'stderr'
Do you want to run this program?[N/Yes] (note you need to type Yes):Yes
Analyzing journal..nothing to replay (no transactions older than last
flushed one found)
Fetching on-disc bitmap..done
Checking S+tree../ 1 (of 2)/ 3 (of 110)/ 15 (of 149)node (10667) with
wrong level (18771) found in the tree (should be 1)
Segmentation fault.
Last version of reiserfsprogs fix this?
Now, I see that when I run ls /mnt/etc as root I get several file
permissions error:
ls: /mnt/etc/rpc: Permission denied
ls: /mnt/etc/mtab: Permission denied
ls: /mnt/etc/t1lib: Permission denied
ls: /mnt/etc/hotplug: Permission denied
ls: /mnt/etc/serial.conf: Permission denied
ls: /mnt/etc/sprucesig: Permission denied
and kernel:
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 68722 0x0 SD]
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 68669 0x0 SD]
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 64508 0x0 SD]
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 63049 0x0 SD]
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 68673 0x0 SD]
is_tree_node: node level 18771 does not match to the expected one 1
vs-5150: search_by_key: invalid format found in block 10667. Fsck?
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
data of [4160 68377 0x0 SD]
Perhaps this can be fixed with reiserfsprogs last version, but I think that
this should never happen
in journaling filesystem (or it should be very difficult, it shouldn't
happen in a normal 200mhz box)
I'll send any information about my computer, if you need.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
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
1 sibling, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-16 17:57 UTC (permalink / raw)
To: linux-kernel
Sorry :-)
> /etc/mtab is a reiserfs partition.
/etc/mtab is IN a reiserfs partition.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
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
1 sibling, 1 reply; 16+ messages in thread
From: Ragnar Kjørstad @ 2001-12-16 20:12 UTC (permalink / raw)
To: Diego Calleja; +Cc: linux-kernel
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
--
Ragnar Kjørstad
Big Storage
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
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>
0 siblings, 2 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-17 1:58 UTC (permalink / raw)
To: linux-kernel
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
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
2001-12-17 1:58 ` Diego Calleja
@ 2001-12-17 21:01 ` Sakari Ailus
[not found] ` <13425.1008580831@nova.botz.org>
1 sibling, 0 replies; 16+ messages in thread
From: Sakari Ailus @ 2001-12-17 21:01 UTC (permalink / raw)
To: Diego Calleja; +Cc: linux-kernel
Diego Calleja wrote:
> 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?
No, it is what it says, AFAIK.
read/write/whatever system call tries to access past end of device
although it isn't asked to (or the problem is somewhere deeper). This
has happened to me on swap partition which had fairly dramatic effect.
;-) Not using last few blocks solved the problem. Of course, this
shouldn't be the case...
--
Sakari Ailus
sakari.ailus@retiisi.dyndns.org
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
[not found] ` <13425.1008580831@nova.botz.org>
@ 2001-12-17 23:33 ` Diego Calleja
2001-12-18 5:01 ` Ross Vandegrift
` (2 more replies)
0 siblings, 3 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-17 23:33 UTC (permalink / raw)
To: linux-kernel; +Cc: Jurgen Botz
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
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
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] ` <20011218125852.A1159@namesys.com>
2 siblings, 2 replies; 16+ messages in thread
From: Ross Vandegrift @ 2001-12-18 5:01 UTC (permalink / raw)
To: Diego Calleja; +Cc: linux-kernel, Jurgen Botz
> 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?
I've seen this happen when being careless about partitioning my drive. If
you changed your partition table and created the filesystem without a reboot
you could be in for this problem. If fdisk was unable to update the
partition table after writing it out and you ran mkreiserfs, you just made a
filesystem on the *old* partition, according to the *old* partition table.
Upon rebooting, the disk will be synced to the new partition table. If you
happened to shrink the parition a bit, the filsystem is suddenly longer than
the partition.
Ross Vandegrift
ross@willow.seitz.com
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
2001-12-18 5:01 ` Ross Vandegrift
@ 2001-12-18 6:19 ` Jurgen Botz
2001-12-18 21:45 ` Diego Calleja
1 sibling, 0 replies; 16+ messages in thread
From: Jurgen Botz @ 2001-12-18 6:19 UTC (permalink / raw)
To: Ross Vandegrift; +Cc: Diego Calleja, linux-kernel, Jurgen Botz
Ross Vandegrift wrote:
> > 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?
>
> I've seen this happen when being careless about partitioning my drive. If
> you changed your partition table and created the filesystem without a reboot
> you could be in for this problem. If fdisk was unable to update the
> partition table after writing it out and you ran mkreiserfs, you just made a
> filesystem on the *old* partition, according to the *old* partition table.
> Upon rebooting, the disk will be synced to the new partition table. If you
> happened to shrink the parition a bit, the filsystem is suddenly longer than
> the partition.
But that doesn't account for badblocks trying to read past the end of the
device (which Diego reported in his previous post) unlesss... unless that
was still the same session (boot) during which he changed partitions...
Diego?
:j
--
Jürgen Botz | While differing widely in the various
jurgen@botz.org | little bits we know, in our infinite
| ignorance we are all equal. -Karl Popper
^ permalink raw reply [flat|nested] 16+ messages in thread
* [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!]
[not found] ` <20011218220828.A381@diego>
@ 2001-12-18 21:11 ` Diego Calleja
2001-12-19 9:18 ` Nikita Danilov
1 sibling, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-18 21:11 UTC (permalink / raw)
To: linux-kernel; +Cc: Nikita
On Tue, 18 Dec 2001 22:08:28 Diego Calleja wrote:
On Tue, 18 Dec 2001 12:58:46 Nikita Danilov wrote:
> Diego Calleja writes:
> > Well, I've run badblocks in 2.4.16
> > results:
> >
> >
> > 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 :-((
>
> You mean you cannot access /sbin/reiserfsck, because root file system is
> unstable? Sorry, probably I missed start of this thread on lkml.
I mean this:
root@diego:~# reiserfsck /dev/hdc5
<-------------reiserfsck, 2001------------->
reiserfsprogs 3.x.0j
Will read-only check consistency of the partition
Will put log info to 'stderr'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
Analyzing journal..nothing to replay (no transactions older than last
flushed one found)
Fetching on-disk bitmap..done
Checking S+tree../ 1 (of 2)/ 3 (of 110)/ 15 (of 149)node (10667) with
wrong level (18771) found in the tree (should be 1)
Segmentation fault
root@diego:~#
>
> > -This corruption should NOT have happened, reiserfsck
> shouldn't
> > have to be used.
>
> Unfortunately this looks like "standard" reiserfs tree corruption.
> Take
>
> ftp://ftp.namesys.com/pub/reiserfsprogs/pre/reiserfsprogs-3.x.0k_pre11.tar.gz,
>
> build it and run reiserfsck from there. If your root file system is
> dead, you will have to do this from some other media (like floppy).
Well, I've a copy of all data in another partition...I'm running from it.
I've downloaded that version....well, it don't crash, here's output:
root@diego:~/reiserfsprogs-3.x.0k_pre11/fsck# ./reiserfsck -i /dev/hdc5
<-------------reiserfsck, 2001------------->
reiserfsprogs 3.x.0k_pre11
Will read-only check consistency of the filesystem on /dev/hdc5
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --check started at Tue Dec 18 21:59:12 2001
###########
Replaying journal..
0 transactions replayed
reserved=8193
Checking S+tree../ 1 (of 2)/ 3 (of 110)/ 15 (of 149)node (10667) with
wrong level (18771) found in the tree (should be 1)
whole subtree skipped
ok
Comparing bitmaps..free block count 1970606 mismatches with a correct one
1971004.
on-disk bitmap does not match to the correct one. 91 bytes differ
Bad nodes were found, Semantic pass skipped
There were found 3 corruptions which can be fixed only during
--rebuild-tree
###########
reiserfsck finished at Tue Dec 18 22:06:23 2001
###########
If I do --rebuild tree, will I lose my data?
>
> > -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
>
> Nikita.
Diego Calleja
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [reiserfs-list] Re: Reiserfs corruption on 2.4.17-rc1!
[not found] ` <3C1F3FDA.5050601@namesys.com>
@ 2001-12-18 21:35 ` Diego Calleja
0 siblings, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-18 21:35 UTC (permalink / raw)
To: Hans Reiser; +Cc: linux-kernel, reiserfs-list
On Tue, 18 Dec 2001 14:08:42 Hans Reiser wrote:
> Nikita Danilov wrote:
>
> >Diego Calleja writes:
> >
> >
> >Unfortunately this looks like "standard" reiserfs tree corruption.
> >Take
> >
> A little more precisely: nobody at Namesys has ever hit this bug using
> our known healthy hardware. Various users have. Bad hardware (e.g
> media defect) could cause this bug, and maybe cause it in just about the
> number of users that we see it in. This does NOT mean that it is due
> to bad hardware. If you, or anyone, can reproduce this bug, we would be
> very interested to learn how to do so.
>
> Hans
I'm afraid I can't. It just happened. I only can describe what was I doing,
although it must be useless....
The system booted with linux 2.4.17-rc1. I was readin mail in kde
when I tried to mount my vfat partition on /win to listen mp3. (as a
normal
user, of course). But I couldn't mount it. Reason?:
ls: mtab: permission denied
Then I log as root, but ls -l /etc/mtab said:
ls: mtab: permission denied
any chmod in /etc/mtab: (as root)
chmod: getting attributes of mtab: Permission denied
After this, the filesystem started to fail a lot in all other programs
, the problem is in some files in /etc.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
2001-12-18 5:01 ` Ross Vandegrift
2001-12-18 6:19 ` Jurgen Botz
@ 2001-12-18 21:45 ` Diego Calleja
1 sibling, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-18 21:45 UTC (permalink / raw)
To: linux-kernel; +Cc: ross
On Tue, 18 Dec 2001 06:01:45 Ross Vandegrift wrote:
> > 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?
>
> I've seen this happen when being careless about partitioning my drive.
> If
> you changed your partition table and created the filesystem without a
> reboot
> you could be in for this problem. If fdisk was unable to update the
> partition table after writing it out and you ran mkreiserfs, you just
> made a
> filesystem on the *old* partition, according to the *old* partition
> table.
> Upon rebooting, the disk will be synced to the new partition table. If
> you
> happened to shrink the parition a bit, the filsystem is suddenly longer
> than
> the partition.
Before partitioning as now it is, I had the same problem. Perhaps it's due
to a fdisk bug.
If I see the message "Partitioning table couldn't be re-read" or something
like that, I always reboot. Perhaps I forgot rebooting, and this is the
problem, but it's very improbable
>
> Ross Vandegrift
> ross@willow.seitz.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [grundig@teleline.es: Re: Reiserfs corruption on 2.4.17-rc1!]
[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
1 sibling, 0 replies; 16+ messages in thread
From: Nikita Danilov @ 2001-12-19 9:18 UTC (permalink / raw)
To: Diego Calleja; +Cc: linux-kernel, Reiserfs mail-list
Diego Calleja writes:
>
> On Tue, 18 Dec 2001 22:08:28 Diego Calleja wrote:
>
[...]
> >
> > ftp://ftp.namesys.com/pub/reiserfsprogs/pre/reiserfsprogs-3.x.0k_pre11.tar.gz,
> >
> > build it and run reiserfsck from there. If your root file system is
> > dead, you will have to do this from some other media (like floppy).
> Well, I've a copy of all data in another partition...I'm running from it.
> I've downloaded that version....well, it don't crash, here's output:
> root@diego:~/reiserfsprogs-3.x.0k_pre11/fsck# ./reiserfsck -i /dev/hdc5
>
> <-------------reiserfsck, 2001------------->
> reiserfsprogs 3.x.0k_pre11
>
> Will read-only check consistency of the filesystem on /dev/hdc5
> Will put log info to 'stdout'
>
> Do you want to run this program?[N/Yes] (note need to type Yes):Yes
> ###########
> reiserfsck --check started at Tue Dec 18 21:59:12 2001
> ###########
> Replaying journal..
> 0 transactions replayed
> reserved=8193
> Checking S+tree../ 1 (of 2)/ 3 (of 110)/ 15 (of 149)node (10667) with
> wrong level (18771) found in the tree (should be 1)
> whole subtree skipped
> ok
> Comparing bitmaps..free block count 1970606 mismatches with a correct one
> 1971004.
> on-disk bitmap does not match to the correct one. 91 bytes differ
> Bad nodes were found, Semantic pass skipped
> There were found 3 corruptions which can be fixed only during
> --rebuild-tree
> ###########
> reiserfsck finished at Tue Dec 18 22:06:23 2001
> ###########
>
> If I do --rebuild tree, will I lose my data?
You shouldn't. But backup is always your best friend.
And, I am sorry, for misguiding you, last reiserfsprogs are
ftp://ftp.namesys.com/pub/reiserfsprogs/pre/reiserfsprogs-3.x.0k-pre13.tar.gz
use them in stead.
>
>
> >
> > > -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
> >
Nikita.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
[not found] ` <20011219095303.A11409@namesys.com>
@ 2001-12-20 0:20 ` Diego Calleja
0 siblings, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-20 0:20 UTC (permalink / raw)
To: linux-kernel; +Cc: green, reiserfs-list
On Wed, 19 Dec 2001 07:53:03 Oleg Drokin wrote:
> Hello!
>
> So why didn't you run reiserfsck --rebuild-tree then?
I've done it, under 2.4.17-rc2, It seems it's solved (although I can't know
what happened). reiserfsck -l -->
####### Pass 0 #######
"r5" got 142629 hits
####### Pass 1 #######
####### Pass 2 #######
####### Pass 3 #########
name "rpc" in directory 2 4160 points to nowhere 4160 68722 - removed
name "mtab" in directory 2 4160 points to nowhere 4160 68669 - removed
name "t1lib" in directory 2 4160 points to nowhere 4160 64508 - removed
name "hotplug" in directory 2 4160 points to nowhere 4160 63049 - removed
name "serial.conf" in directory 2 4160 points to nowhere 4160 68673 -
removed
name "sprucesig" in directory 2 4160 points to nowhere 4160 68377 - removed
dir 2 4160 has wrong sd_size 5792, has to be 5632
dir 1 2 has wrong sd_size 480, has to be 512
####### Pass 3a (lost+found pass) #########
Version 3.x.0K-pre13 (the last I found)
It seems all is working correctly). I'll try to reproduce the bug, althouh
I think it's no possible
Diego Calleja
>
> Bye,
> Oleg
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
2001-12-19 16:56 ` Edward Muller
@ 2001-12-19 22:17 ` Diego Calleja
0 siblings, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-19 22:17 UTC (permalink / raw)
To: linux-kernel; +Cc: Edward Muller
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
> -------------------------------
>
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
[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
1 sibling, 1 reply; 16+ messages in thread
From: Edward Muller @ 2001-12-19 16:56 UTC (permalink / raw)
To: Diego Calleja; +Cc: linux-kernel
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.
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?
--
-------------------------------
Edward Muller
Director of IS
973-715-0230 (cell)
212-487-9064 x115 (NYC)
http://www.learningpatterns.com
-------------------------------
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Reiserfs corruption on 2.4.17-rc1!
[not found] <20011217002350.D418@diego>
@ 2001-12-17 1:45 ` Diego Calleja
2001-12-19 16:56 ` Edward Muller
1 sibling, 0 replies; 16+ messages in thread
From: Diego Calleja @ 2001-12-17 1:45 UTC (permalink / raw)
To: linux-kernel
> > 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
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.
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2001-12-20 0:18 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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] ` <3C1F3FDA.5050601@namesys.com>
2001-12-18 21:35 ` [reiserfs-list] " Diego Calleja
[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] ` <20011218125852.A1159@namesys.com>
[not found] ` <20011218224848.C377@diego>
[not found] ` <20011219095303.A11409@namesys.com>
2001-12-20 0:20 ` Reiserfs corruption on 2.4.17-rc1! 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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).