* reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
@ 2005-06-05 14:50 Adrian Ulrich
2005-06-06 8:43 ` E.Gryaznova
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-05 14:50 UTC (permalink / raw)
To: reiserfs-list
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hi,
Well, i managed to crash reiser4 ;-)
I created an iso-image on my reiser4 filesystem (it's my rootfs)
using mkisofs. mkisofs aborted because the filesystem was full.
After freeing up some space, i ran mkisofs again and: *bam*
fsck.reiser4 told me to run '--rebuild-sb' but looks like
it didn't help:
The System still crashes while creating the ISO
(Should be 4.1 GiB, but crashes at ~ 3.7 GiB..)
# fsck.reiser4 --version
fsck.reiser4 1.0.4
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed
by reiser4progs/COPYING.
# uname -a
Linux fuzzy 2.6.11.10 #1 SMP Sat May 21 13:17:21 CEST 2005 i686 unknown
unknown GNU/Linux
* I attached the Syslog output
* I rand 'debugfs.reiserf -P $device' and can
provide the output to namesys if they need it
(9.3 MiB)
--
We're working on it, slowly but surely...or not-so-surely in the spots
we're not so sure... -- Larry Wall
[-- Attachment #2: syslog20050605.txt --]
[-- Type: text/plain, Size: 15074 bytes --]
Jun 5 15:59:23 fuzzy kernel: Linux version 2.6.11.10 (root@fuzzy) (gcc version 3.3.4) #1 SMP Sat May 21 13:17:21 CEST 2005
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 0000000000100000 - 000000003fe30000 (usable)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fe30000 - 000000003fe414a0 (ACPI NVS)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fe414a0 - 000000003ff30000 (usable)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003ff30000 - 000000003ff40000 (ACPI data)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003ff40000 - 000000003fff0000 (ACPI NVS)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000fecf0000 - 00000000fecf1000 (reserved)
Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
Jun 5 15:59:23 fuzzy kernel: Processor #0 15:2 APIC version 20
Jun 5 15:59:23 fuzzy kernel: Processor #1 15:2 APIC version 20
Jun 5 15:59:23 fuzzy kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Jun 5 15:59:23 fuzzy kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Jun 5 15:59:23 fuzzy kernel: Allocating PCI resources starting at 40000000 (gap: 40000000:becf0000)
Jun 5 15:59:23 fuzzy kernel: Built 1 zonelists
Jun 5 15:59:23 fuzzy kernel: Kernel command line: root=/dev/md1 sbp2_serialize_io=1 sbp2_max_speed=2
Jun 5 15:59:23 fuzzy kernel: PID hash table entries: 4096 (order: 12, 65536 bytes)
Jun 5 15:59:23 fuzzy kernel: Detected 2992.449 MHz processor.
Jun 5 15:59:23 fuzzy kernel: Console: colour VGA+ 80x25
Jun 5 15:59:23 fuzzy kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jun 5 15:59:23 fuzzy kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jun 5 15:59:23 fuzzy kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Jun 5 15:59:23 fuzzy kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Jun 5 15:59:23 fuzzy kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
Jun 5 15:59:23 fuzzy kernel: per-CPU timeslice cutoff: 1462.91 usecs.
Jun 5 15:59:23 fuzzy kernel: task migration cache decay timeout: 2 msecs.
Jun 5 15:59:23 fuzzy kernel: Booting processor 1/1 eip 3000
Jun 5 15:59:23 fuzzy kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
Jun 5 15:59:23 fuzzy kernel: ENABLING IO-APIC IRQs
Jun 5 15:59:23 fuzzy kernel: Brought up 2 CPUs
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-0158: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: PCI: Probing PCI hardware (bus 00)
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.SYSM._CRS] (Node c193ef40), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: ACPI-0158: *** Error: Method execution failed [\_SB_.SYSM._CRS] (Node c193ef40), AE_AML_BUFFER_LIMIT
Jun 5 15:59:23 fuzzy kernel: highmem bounce pool size: 64 pages
Jun 5 15:59:23 fuzzy kernel: ps_hash_table: 32 buckets
Jun 5 15:59:23 fuzzy kernel: Hangcheck: starting hangcheck timer 0.5.0 (tick is 180 seconds, margin is 60 seconds).
Jun 5 15:59:23 fuzzy kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jun 5 15:59:23 fuzzy kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Jun 5 15:59:23 fuzzy kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
Jun 5 15:59:23 fuzzy kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Jun 5 15:59:23 fuzzy kernel: PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
Jun 5 15:59:23 fuzzy kernel: hda: MAXTOR 6L080J4, ATA DISK drive
Jun 5 15:59:23 fuzzy kernel: hdb: _NEC DVD_RW ND-2500A, ATAPI CD/DVD-ROM drive
Jun 5 15:59:23 fuzzy kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jun 5 15:59:23 fuzzy kernel: hdc: ST380011A, ATA DISK drive
Jun 5 15:59:23 fuzzy kernel: ide1 at 0x170-0x177,0x376 on irq 15
Jun 5 15:59:23 fuzzy kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jun 5 15:59:23 fuzzy kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
Jun 5 15:59:23 fuzzy kernel: ACPI wakeup devices:
Jun 5 15:59:23 fuzzy kernel: TANA P0P3 AC97 USB0 USB1 USB2 USB3 USB7 UAR1 UAR2 SLPB
Jun 5 15:59:23 fuzzy kernel: md: hdc1 has different UUID to hdc3
Jun 5 15:59:23 fuzzy kernel: md: hda1 has different UUID to hdc3
Jun 5 15:59:23 fuzzy kernel: md5: setting max_sectors to 128, segment boundary to 32767
Jun 5 15:59:23 fuzzy kernel: raid0: looking at hdc3
Jun 5 15:59:23 fuzzy kernel: raid0: comparing hdc3(38596096) with hdc3(38596096)
Jun 5 15:59:23 fuzzy kernel: raid0: END
Jun 5 15:59:23 fuzzy kernel: raid0: ==> UNIQUE
Jun 5 15:59:23 fuzzy kernel: raid0: 1 zones
Jun 5 15:59:23 fuzzy kernel: raid0: looking at hda3
Jun 5 15:59:23 fuzzy kernel: raid0: comparing hda3(38620160) with hdc3(38596096)
Jun 5 15:59:23 fuzzy kernel: raid0: NOT EQUAL
Jun 5 15:59:23 fuzzy kernel: raid0: comparing hda3(38620160) with hda3(38620160)
Jun 5 15:59:23 fuzzy kernel: raid0: END
Jun 5 15:59:23 fuzzy kernel: raid0: ==> UNIQUE
Jun 5 15:59:23 fuzzy kernel: raid0: 2 zones
Jun 5 15:59:23 fuzzy kernel: raid0: FINAL 2 zones
Jun 5 15:59:23 fuzzy kernel: raid0: zone 1
Jun 5 15:59:23 fuzzy kernel: raid0: checking hda3 ... contained as device 0
Jun 5 15:59:23 fuzzy kernel: (38620160) is smallest!.
Jun 5 15:59:23 fuzzy kernel: raid0: checking hdc3 ... nope.
Jun 5 15:59:23 fuzzy kernel: raid0: zone->nb_dev: 1, size: 24064
Jun 5 15:59:23 fuzzy kernel: raid0: current zone offset: 38620160
Jun 5 15:59:23 fuzzy kernel: raid0: done.
Jun 5 15:59:23 fuzzy kernel: raid0 : md_size is 77216256 blocks.
Jun 5 15:59:23 fuzzy kernel: raid0 : conf->hash_spacing is 77192192 blocks.
Jun 5 15:59:23 fuzzy kernel: raid0 : nb_zone is 2.
Jun 5 15:59:23 fuzzy kernel: raid0 : Allocating 8 bytes for hash.
Jun 5 15:59:23 fuzzy kernel: md: kicking non-fresh hdc1 from array!
Jun 5 15:59:23 fuzzy kernel: ef_hash_table: 8192 buckets
Jun 5 15:59:23 fuzzy kernel: z_hash_table: 8192 buckets
Jun 5 15:59:23 fuzzy kernel: z_hash_table: 8192 buckets
Jun 5 15:59:23 fuzzy kernel: j_hash_table: 16384 buckets
Jun 5 15:59:23 fuzzy kernel: sda: asking for cache data failed
Jun 5 15:59:23 fuzzy kernel: sda: assuming drive cache: write through
Jun 5 15:59:23 fuzzy kernel: sda: asking for cache data failed
Jun 5 15:59:23 fuzzy kernel: sda: assuming drive cache: write through
Jun 5 15:59:23 fuzzy kernel: sdb: asking for cache data failed
Jun 5 15:59:23 fuzzy kernel: sdb: assuming drive cache: write through
Jun 5 15:59:23 fuzzy kernel: sdb: asking for cache data failed
Jun 5 15:59:23 fuzzy kernel: sdb: assuming drive cache: write through
Jun 5 15:59:23 fuzzy kernel: ...done (2229 jiffies)
Jun 5 15:59:23 fuzzy kernel: d_cursor_hash_table: 256 buckets
Jun 5 15:59:23 fuzzy kernel: VFS: Mounted root (reiser4 filesystem) readonly.
Jun 5 15:59:23 fuzzy kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Jun 5 15:59:23 fuzzy kernel: sdc: assuming drive cache: write through
Jun 5 15:59:23 fuzzy kernel: sdc: assuming drive cache: write through
Jun 5 16:00:50 fuzzy kernel: reiser4[mkisofs(3178)]: alloc_blocks_forward (fs/reiser4/plugin/space/bitmap.c:1074)[zam-397]:
Jun 5 16:00:50 fuzzy kernel: code: -2 at fs/reiser4/search.c:1159
Jun 5 16:00:50 fuzzy kernel: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
Jun 5 16:00:50 fuzzy kernel: pins held: jnode: 0, tree: 0 (r:0,w:0), dk: 0 (r:0,w:0)
Jun 5 16:00:50 fuzzy kernel: jload: 0, txnh: 0, atom: 0, stack: 0, txnmgr: 0, ktxnmgrd: 0, fq: 0, reiser4_sb: 0
Jun 5 16:00:50 fuzzy kernel: inode: 0, cbk_cache: 0 (r:0,w0), epoch: 0, eflush: 0, zlock: 0 (r:0, w:0)
Jun 5 16:00:50 fuzzy kernel: spin: 0, long: 1 inode_sem: (r:0,w:0)
Jun 5 16:00:50 fuzzy kernel: d: 2, x: 275850, t: 7
Jun 5 16:00:50 fuzzy kernel: ^Ilocks: jnode: 0, tree: 0 (r:0,w:0), dk: 0 (r:0,w:0)
Jun 5 16:00:50 fuzzy kernel: jload: 0, txnh: 0, atom: 0, stack: 0, txnmgr: 0, ktxnmgrd: 0, fq: 0, reiser4_sb: 0
Jun 5 16:00:50 fuzzy kernel: inode: 0, cbk_cache: 0 (r:0,w0), epoch: 0, eflush: 0, zlock: 0 (r:0, w:0)
Jun 5 16:00:50 fuzzy kernel: spin: 0, long: 1 inode_sem: (r:0,w:0)
Jun 5 16:00:50 fuzzy kernel: d: 2, x: 275850, t: 7
Jun 5 16:00:50 fuzzy kernel: pid: 3178, comm: mkisofs
Jun 5 16:00:50 fuzzy kernel: ^Ilock stack:
Jun 5 16:00:50 fuzzy kernel: .... nr_signaled 0
Jun 5 16:00:50 fuzzy kernel: .... curpri low
Jun 5 16:00:50 fuzzy kernel: .... current locks:
Jun 5 16:00:50 fuzzy kernel: ...... write: 6291574
Jun 5 16:00:50 fuzzy kernel: ^Iatom: refcount: 2 id: 30 flags: 0 txnh_count: 1 capture_count: 128619 stage: 1 start: 4294703571, flushed: 0
Jun 5 16:00:50 fuzzy kernel: ------------[ cut here ]------------
Jun 5 16:00:50 fuzzy kernel: kernel BUG at fs/reiser4/debug.c:141!
Jun 5 16:00:50 fuzzy kernel: invalid operand: 0000 [#1]
Jun 5 16:00:50 fuzzy kernel: SMP
Jun 5 16:00:50 fuzzy kernel: Modules linked in: e1000 reiserfs visor usbserial sr_mod
Jun 5 16:00:50 fuzzy kernel: CPU: 1
Jun 5 16:00:50 fuzzy kernel: EIP: 0060:[<c0192af0>] Not tainted VLI
Jun 5 16:00:50 fuzzy kernel: EFLAGS: 00010246 (2.6.11.10)
Jun 5 16:00:50 fuzzy kernel: EIP is at reiser4_do_panic+0x250/0x310
Jun 5 16:00:50 fuzzy kernel: eax: c061b644 ebx: c061b648 ecx: c061b648 edx: c061b648
Jun 5 16:00:50 fuzzy kernel: esi: f6528000 edi: 00000432 ebp: 00000000 esp: f6529538
Jun 5 16:00:50 fuzzy kernel: ds: 007b es: 007b ss: 0068
Jun 5 16:00:50 fuzzy kernel: Process mkisofs (pid: 3178, threadinfo=f6528000 task=f7793020)
Jun 5 16:00:50 fuzzy kernel: Stack: f7d51600 00000001 c04ca1b8 f6529564 c04cf9df 00000487 c04ad23d c04eaac0
Jun 5 16:00:50 fuzzy kernel: c02ab3cf c04ca1a3 c04eada0 c04d8379 c04ad23d c04eaac0 00000432 c0213bc7
Jun 5 16:00:50 fuzzy kernel: f7d51600 f65295c8 00000000 f652964c f6529e34 000146b4 00000000 c01cba69
Jun 5 16:00:50 fuzzy kernel: Call Trace:
Jun 5 16:00:50 fuzzy kernel: [<c02ab3cf>] alloc_blocks_forward+0xaf/0x310
Jun 5 16:00:50 fuzzy kernel: [<c0213bc7>] get_space_allocator+0x17/0xd0
Jun 5 16:00:50 fuzzy kernel: [<c01cba69>] reiser4_alloc_blocks+0xb9/0x6c0
Jun 5 16:00:50 fuzzy kernel: [<c0290d2f>] extent_unit_index+0x2f/0x120
Jun 5 16:00:50 fuzzy kernel: [<c0290a06>] extent_allocate_blocks+0x56/0xe0
Jun 5 16:00:50 fuzzy kernel: [<c0295a6c>] alloc_extent+0x31c/0x730
Jun 5 16:00:50 fuzzy kernel: [<c029866f>] item_length_by_coord+0x4f/0x1e0
Jun 5 16:00:50 fuzzy kernel: [<c02338db>] is_plugin_id_valid+0x1b/0xa0
Jun 5 16:00:50 fuzzy kernel: [<c029b2cf>] item_is_extent+0x1f/0x90
Jun 5 16:00:50 fuzzy kernel: [<c01ef721>] handle_pos_on_twig+0x71/0x1e0
Jun 5 16:00:50 fuzzy kernel: [<c01f1458>] squalloc+0x28/0x60
Jun 5 16:00:50 fuzzy kernel: [<c01e99c7>] jnode_flush+0x6a7/0xeb0
Jun 5 16:00:50 fuzzy kernel: [<c027f993>] nr_units_extent+0x23/0x90
Jun 5 16:00:50 fuzzy kernel: [<c01eaab6>] flush_current_atom+0x8b6/0x1180
Jun 5 16:00:50 fuzzy kernel: [<c01d766c>] flush_some_atom+0x76c/0xe10
Jun 5 16:00:50 fuzzy kernel: [<c0175db0>] iput+0x40/0x90
Jun 5 16:00:50 fuzzy kernel: [<c0220b4b>] writeout+0x7b/0xe0
Jun 5 16:00:50 fuzzy kernel: [<c0220c0e>] reiser4_sync_inodes+0x5e/0xf0
Jun 5 16:00:50 fuzzy kernel: [<c019dcce>] jnode_invariant_f+0x29e/0x2b0
Jun 5 16:00:50 fuzzy kernel: [<c017e9be>] sync_sb_inodes+0x2e/0x40
Jun 5 16:00:50 fuzzy kernel: [<c017eab2>] writeback_inodes+0xe2/0xf0
Jun 5 16:00:50 fuzzy kernel: [<c0141168>] balance_dirty_pages+0x98/0x160
Jun 5 16:00:50 fuzzy kernel: [<c01cfe82>] txn_restart_current+0x22/0x80
Jun 5 16:00:50 fuzzy kernel: [<c0289a29>] extent_balance_dirty_pages+0x109/0x1e0
Jun 5 16:00:50 fuzzy kernel: [<c0192d45>] schedulable+0x45/0xc0
Jun 5 16:00:50 fuzzy kernel: [<c028a1f9>] extent_write_flow+0x6f9/0x16e0
Jun 5 16:00:50 fuzzy kernel: [<c028b470>] write_extent+0x0/0x50
Jun 5 16:00:50 fuzzy kernel: [<c02b980d>] append_and_or_overwrite+0x48d/0xb00
Jun 5 16:00:50 fuzzy kernel: [<c02395e7>] key_by_inode_and_offset_common+0x27/0x250
Jun 5 16:00:50 fuzzy kernel: [<c02b9f5a>] write_flow+0xda/0x130
Jun 5 16:00:50 fuzzy kernel: [<c01cce45>] grabbed2free+0x145/0x290
Jun 5 16:00:50 fuzzy kernel: [<c02ba2fa>] write_file+0x9a/0x110
Jun 5 16:00:50 fuzzy kernel: [<c02ba6e4>] write_unix_file+0x374/0x560
Jun 5 16:00:50 fuzzy kernel: [<c0225512>] reiser4_write+0x92/0x1d0
Jun 5 16:00:50 fuzzy kernel: [<c011e4ad>] release_console_sem+0x7d/0xc0
Jun 5 16:00:50 fuzzy kernel: [<c015b0de>] vfs_write+0xae/0x130
Jun 5 16:00:50 fuzzy kernel: [<c015b231>] sys_write+0x51/0x80
Jun 5 16:00:50 fuzzy kernel: [<c0103123>] syscall_call+0x7/0xb
Jun 5 16:00:50 fuzzy kernel: Code: ff ff 8b 11 85 d2 0f 84 33 ff ff ff 8b 00 39 c8 0f 85 29 ff ff ff 39 42 04 0f 85 20 ff ff ff b8 44 b6 61 c0 e8 d2 ce 2c 00 89 f6 <0f> 0b 8d 00 b9 a1 4c c0 c7 04 24 ec 3f 4f c0 b8 e0 b1 61 c0 89
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-05 14:50 reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super) Adrian Ulrich
@ 2005-06-06 8:43 ` E.Gryaznova
2005-06-06 8:25 ` Adrian Ulrich
2005-06-06 8:55 ` Vitaly Fertman
2005-06-06 10:31 ` E.Gryaznova
2 siblings, 1 reply; 14+ messages in thread
From: E.Gryaznova @ 2005-06-06 8:43 UTC (permalink / raw)
To: Adrian Ulrich; +Cc: reiserfs-list
Hello.
Do you have more than one mounted reiser4 partition?
Thanks,
Lena
Adrian Ulrich wrote:
>Hi,
>
>Well, i managed to crash reiser4 ;-)
>
>I created an iso-image on my reiser4 filesystem (it's my rootfs)
>using mkisofs. mkisofs aborted because the filesystem was full.
>After freeing up some space, i ran mkisofs again and: *bam*
>
>fsck.reiser4 told me to run '--rebuild-sb' but looks like
>it didn't help:
> The System still crashes while creating the ISO
> (Should be 4.1 GiB, but crashes at ~ 3.7 GiB..)
>
>
># fsck.reiser4 --version
>fsck.reiser4 1.0.4
>Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed
>by reiser4progs/COPYING.
>
># uname -a
>Linux fuzzy 2.6.11.10 #1 SMP Sat May 21 13:17:21 CEST 2005 i686 unknown
>unknown GNU/Linux
>
>* I attached the Syslog output
>* I rand 'debugfs.reiserf -P $device' and can
> provide the output to namesys if they need it
> (9.3 MiB)
>
>
>
>
>
>
>------------------------------------------------------------------------
>
>Jun 5 15:59:23 fuzzy kernel: Linux version 2.6.11.10 (root@fuzzy) (gcc version 3.3.4) #1 SMP Sat May 21 13:17:21 CEST 2005
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 0000000000100000 - 000000003fe30000 (usable)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fe30000 - 000000003fe414a0 (ACPI NVS)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fe414a0 - 000000003ff30000 (usable)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003ff30000 - 000000003ff40000 (ACPI data)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003ff40000 - 000000003fff0000 (ACPI NVS)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000fecf0000 - 00000000fecf1000 (reserved)
>Jun 5 15:59:23 fuzzy kernel: BIOS-e820: 00000000fed20000 - 00000000feda0000 (reserved)
>Jun 5 15:59:23 fuzzy kernel: Processor #0 15:2 APIC version 20
>Jun 5 15:59:23 fuzzy kernel: Processor #1 15:2 APIC version 20
>Jun 5 15:59:23 fuzzy kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
>Jun 5 15:59:23 fuzzy kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
>Jun 5 15:59:23 fuzzy kernel: Allocating PCI resources starting at 40000000 (gap: 40000000:becf0000)
>Jun 5 15:59:23 fuzzy kernel: Built 1 zonelists
>Jun 5 15:59:23 fuzzy kernel: Kernel command line: root=/dev/md1 sbp2_serialize_io=1 sbp2_max_speed=2
>Jun 5 15:59:23 fuzzy kernel: PID hash table entries: 4096 (order: 12, 65536 bytes)
>Jun 5 15:59:23 fuzzy kernel: Detected 2992.449 MHz processor.
>Jun 5 15:59:23 fuzzy kernel: Console: colour VGA+ 80x25
>Jun 5 15:59:23 fuzzy kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
>Jun 5 15:59:23 fuzzy kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
>Jun 5 15:59:23 fuzzy kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
>Jun 5 15:59:23 fuzzy kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
>Jun 5 15:59:23 fuzzy kernel: CPU0: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
>Jun 5 15:59:23 fuzzy kernel: per-CPU timeslice cutoff: 1462.91 usecs.
>Jun 5 15:59:23 fuzzy kernel: task migration cache decay timeout: 2 msecs.
>Jun 5 15:59:23 fuzzy kernel: Booting processor 1/1 eip 3000
>Jun 5 15:59:23 fuzzy kernel: CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
>Jun 5 15:59:23 fuzzy kernel: ENABLING IO-APIC IRQs
>Jun 5 15:59:23 fuzzy kernel: Brought up 2 CPUs
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-0158: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: PCI: Probing PCI hardware (bus 00)
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0.SBRG.PS2M._STA] (Node c193c2a0), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\MCTH] (Node c191ee60), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\OSFL] (Node c191e540), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-1138: *** Error: Method execution failed [\_SB_.SYSM._CRS] (Node c193ef40), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: ACPI-0158: *** Error: Method execution failed [\_SB_.SYSM._CRS] (Node c193ef40), AE_AML_BUFFER_LIMIT
>Jun 5 15:59:23 fuzzy kernel: highmem bounce pool size: 64 pages
>Jun 5 15:59:23 fuzzy kernel: ps_hash_table: 32 buckets
>Jun 5 15:59:23 fuzzy kernel: Hangcheck: starting hangcheck timer 0.5.0 (tick is 180 seconds, margin is 60 seconds).
>Jun 5 15:59:23 fuzzy kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>Jun 5 15:59:23 fuzzy kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>Jun 5 15:59:23 fuzzy kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
>Jun 5 15:59:23 fuzzy kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
>Jun 5 15:59:23 fuzzy kernel: PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
>Jun 5 15:59:23 fuzzy kernel: hda: MAXTOR 6L080J4, ATA DISK drive
>Jun 5 15:59:23 fuzzy kernel: hdb: _NEC DVD_RW ND-2500A, ATAPI CD/DVD-ROM drive
>Jun 5 15:59:23 fuzzy kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>Jun 5 15:59:23 fuzzy kernel: hdc: ST380011A, ATA DISK drive
>Jun 5 15:59:23 fuzzy kernel: ide1 at 0x170-0x177,0x376 on irq 15
>Jun 5 15:59:23 fuzzy kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
>Jun 5 15:59:23 fuzzy kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
>Jun 5 15:59:23 fuzzy kernel: ACPI wakeup devices:
>Jun 5 15:59:23 fuzzy kernel: TANA P0P3 AC97 USB0 USB1 USB2 USB3 USB7 UAR1 UAR2 SLPB
>Jun 5 15:59:23 fuzzy kernel: md: hdc1 has different UUID to hdc3
>Jun 5 15:59:23 fuzzy kernel: md: hda1 has different UUID to hdc3
>Jun 5 15:59:23 fuzzy kernel: md5: setting max_sectors to 128, segment boundary to 32767
>Jun 5 15:59:23 fuzzy kernel: raid0: looking at hdc3
>Jun 5 15:59:23 fuzzy kernel: raid0: comparing hdc3(38596096) with hdc3(38596096)
>Jun 5 15:59:23 fuzzy kernel: raid0: END
>Jun 5 15:59:23 fuzzy kernel: raid0: ==> UNIQUE
>Jun 5 15:59:23 fuzzy kernel: raid0: 1 zones
>Jun 5 15:59:23 fuzzy kernel: raid0: looking at hda3
>Jun 5 15:59:23 fuzzy kernel: raid0: comparing hda3(38620160) with hdc3(38596096)
>Jun 5 15:59:23 fuzzy kernel: raid0: NOT EQUAL
>Jun 5 15:59:23 fuzzy kernel: raid0: comparing hda3(38620160) with hda3(38620160)
>Jun 5 15:59:23 fuzzy kernel: raid0: END
>Jun 5 15:59:23 fuzzy kernel: raid0: ==> UNIQUE
>Jun 5 15:59:23 fuzzy kernel: raid0: 2 zones
>Jun 5 15:59:23 fuzzy kernel: raid0: FINAL 2 zones
>Jun 5 15:59:23 fuzzy kernel: raid0: zone 1
>Jun 5 15:59:23 fuzzy kernel: raid0: checking hda3 ... contained as device 0
>Jun 5 15:59:23 fuzzy kernel: (38620160) is smallest!.
>Jun 5 15:59:23 fuzzy kernel: raid0: checking hdc3 ... nope.
>Jun 5 15:59:23 fuzzy kernel: raid0: zone->nb_dev: 1, size: 24064
>Jun 5 15:59:23 fuzzy kernel: raid0: current zone offset: 38620160
>Jun 5 15:59:23 fuzzy kernel: raid0: done.
>Jun 5 15:59:23 fuzzy kernel: raid0 : md_size is 77216256 blocks.
>Jun 5 15:59:23 fuzzy kernel: raid0 : conf->hash_spacing is 77192192 blocks.
>Jun 5 15:59:23 fuzzy kernel: raid0 : nb_zone is 2.
>Jun 5 15:59:23 fuzzy kernel: raid0 : Allocating 8 bytes for hash.
>Jun 5 15:59:23 fuzzy kernel: md: kicking non-fresh hdc1 from array!
>Jun 5 15:59:23 fuzzy kernel: ef_hash_table: 8192 buckets
>Jun 5 15:59:23 fuzzy kernel: z_hash_table: 8192 buckets
>Jun 5 15:59:23 fuzzy kernel: z_hash_table: 8192 buckets
>Jun 5 15:59:23 fuzzy kernel: j_hash_table: 16384 buckets
>Jun 5 15:59:23 fuzzy kernel: sda: asking for cache data failed
>Jun 5 15:59:23 fuzzy kernel: sda: assuming drive cache: write through
>Jun 5 15:59:23 fuzzy kernel: sda: asking for cache data failed
>Jun 5 15:59:23 fuzzy kernel: sda: assuming drive cache: write through
>Jun 5 15:59:23 fuzzy kernel: sdb: asking for cache data failed
>Jun 5 15:59:23 fuzzy kernel: sdb: assuming drive cache: write through
>Jun 5 15:59:23 fuzzy kernel: sdb: asking for cache data failed
>Jun 5 15:59:23 fuzzy kernel: sdb: assuming drive cache: write through
>Jun 5 15:59:23 fuzzy kernel: ...done (2229 jiffies)
>Jun 5 15:59:23 fuzzy kernel: d_cursor_hash_table: 256 buckets
>Jun 5 15:59:23 fuzzy kernel: VFS: Mounted root (reiser4 filesystem) readonly.
>Jun 5 15:59:23 fuzzy kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
>Jun 5 15:59:23 fuzzy kernel: sdc: assuming drive cache: write through
>Jun 5 15:59:23 fuzzy kernel: sdc: assuming drive cache: write through
>Jun 5 16:00:50 fuzzy kernel: reiser4[mkisofs(3178)]: alloc_blocks_forward (fs/reiser4/plugin/space/bitmap.c:1074)[zam-397]:
>Jun 5 16:00:50 fuzzy kernel: code: -2 at fs/reiser4/search.c:1159
>Jun 5 16:00:50 fuzzy kernel: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
>Jun 5 16:00:50 fuzzy kernel: pins held: jnode: 0, tree: 0 (r:0,w:0), dk: 0 (r:0,w:0)
>Jun 5 16:00:50 fuzzy kernel: jload: 0, txnh: 0, atom: 0, stack: 0, txnmgr: 0, ktxnmgrd: 0, fq: 0, reiser4_sb: 0
>Jun 5 16:00:50 fuzzy kernel: inode: 0, cbk_cache: 0 (r:0,w0), epoch: 0, eflush: 0, zlock: 0 (r:0, w:0)
>Jun 5 16:00:50 fuzzy kernel: spin: 0, long: 1 inode_sem: (r:0,w:0)
>Jun 5 16:00:50 fuzzy kernel: d: 2, x: 275850, t: 7
>Jun 5 16:00:50 fuzzy kernel: ^Ilocks: jnode: 0, tree: 0 (r:0,w:0), dk: 0 (r:0,w:0)
>Jun 5 16:00:50 fuzzy kernel: jload: 0, txnh: 0, atom: 0, stack: 0, txnmgr: 0, ktxnmgrd: 0, fq: 0, reiser4_sb: 0
>Jun 5 16:00:50 fuzzy kernel: inode: 0, cbk_cache: 0 (r:0,w0), epoch: 0, eflush: 0, zlock: 0 (r:0, w:0)
>Jun 5 16:00:50 fuzzy kernel: spin: 0, long: 1 inode_sem: (r:0,w:0)
>Jun 5 16:00:50 fuzzy kernel: d: 2, x: 275850, t: 7
>Jun 5 16:00:50 fuzzy kernel: pid: 3178, comm: mkisofs
>Jun 5 16:00:50 fuzzy kernel: ^Ilock stack:
>Jun 5 16:00:50 fuzzy kernel: .... nr_signaled 0
>Jun 5 16:00:50 fuzzy kernel: .... curpri low
>Jun 5 16:00:50 fuzzy kernel: .... current locks:
>Jun 5 16:00:50 fuzzy kernel: ...... write: 6291574
>Jun 5 16:00:50 fuzzy kernel: ^Iatom: refcount: 2 id: 30 flags: 0 txnh_count: 1 capture_count: 128619 stage: 1 start: 4294703571, flushed: 0
>Jun 5 16:00:50 fuzzy kernel: ------------[ cut here ]------------
>Jun 5 16:00:50 fuzzy kernel: kernel BUG at fs/reiser4/debug.c:141!
>Jun 5 16:00:50 fuzzy kernel: invalid operand: 0000 [#1]
>Jun 5 16:00:50 fuzzy kernel: SMP
>Jun 5 16:00:50 fuzzy kernel: Modules linked in: e1000 reiserfs visor usbserial sr_mod
>Jun 5 16:00:50 fuzzy kernel: CPU: 1
>Jun 5 16:00:50 fuzzy kernel: EIP: 0060:[<c0192af0>] Not tainted VLI
>Jun 5 16:00:50 fuzzy kernel: EFLAGS: 00010246 (2.6.11.10)
>Jun 5 16:00:50 fuzzy kernel: EIP is at reiser4_do_panic+0x250/0x310
>Jun 5 16:00:50 fuzzy kernel: eax: c061b644 ebx: c061b648 ecx: c061b648 edx: c061b648
>Jun 5 16:00:50 fuzzy kernel: esi: f6528000 edi: 00000432 ebp: 00000000 esp: f6529538
>Jun 5 16:00:50 fuzzy kernel: ds: 007b es: 007b ss: 0068
>Jun 5 16:00:50 fuzzy kernel: Process mkisofs (pid: 3178, threadinfo=f6528000 task=f7793020)
>Jun 5 16:00:50 fuzzy kernel: Stack: f7d51600 00000001 c04ca1b8 f6529564 c04cf9df 00000487 c04ad23d c04eaac0
>Jun 5 16:00:50 fuzzy kernel: c02ab3cf c04ca1a3 c04eada0 c04d8379 c04ad23d c04eaac0 00000432 c0213bc7
>Jun 5 16:00:50 fuzzy kernel: f7d51600 f65295c8 00000000 f652964c f6529e34 000146b4 00000000 c01cba69
>Jun 5 16:00:50 fuzzy kernel: Call Trace:
>Jun 5 16:00:50 fuzzy kernel: [<c02ab3cf>] alloc_blocks_forward+0xaf/0x310
>Jun 5 16:00:50 fuzzy kernel: [<c0213bc7>] get_space_allocator+0x17/0xd0
>Jun 5 16:00:50 fuzzy kernel: [<c01cba69>] reiser4_alloc_blocks+0xb9/0x6c0
>Jun 5 16:00:50 fuzzy kernel: [<c0290d2f>] extent_unit_index+0x2f/0x120
>Jun 5 16:00:50 fuzzy kernel: [<c0290a06>] extent_allocate_blocks+0x56/0xe0
>Jun 5 16:00:50 fuzzy kernel: [<c0295a6c>] alloc_extent+0x31c/0x730
>Jun 5 16:00:50 fuzzy kernel: [<c029866f>] item_length_by_coord+0x4f/0x1e0
>Jun 5 16:00:50 fuzzy kernel: [<c02338db>] is_plugin_id_valid+0x1b/0xa0
>Jun 5 16:00:50 fuzzy kernel: [<c029b2cf>] item_is_extent+0x1f/0x90
>Jun 5 16:00:50 fuzzy kernel: [<c01ef721>] handle_pos_on_twig+0x71/0x1e0
>Jun 5 16:00:50 fuzzy kernel: [<c01f1458>] squalloc+0x28/0x60
>Jun 5 16:00:50 fuzzy kernel: [<c01e99c7>] jnode_flush+0x6a7/0xeb0
>Jun 5 16:00:50 fuzzy kernel: [<c027f993>] nr_units_extent+0x23/0x90
>Jun 5 16:00:50 fuzzy kernel: [<c01eaab6>] flush_current_atom+0x8b6/0x1180
>Jun 5 16:00:50 fuzzy kernel: [<c01d766c>] flush_some_atom+0x76c/0xe10
>Jun 5 16:00:50 fuzzy kernel: [<c0175db0>] iput+0x40/0x90
>Jun 5 16:00:50 fuzzy kernel: [<c0220b4b>] writeout+0x7b/0xe0
>Jun 5 16:00:50 fuzzy kernel: [<c0220c0e>] reiser4_sync_inodes+0x5e/0xf0
>Jun 5 16:00:50 fuzzy kernel: [<c019dcce>] jnode_invariant_f+0x29e/0x2b0
>Jun 5 16:00:50 fuzzy kernel: [<c017e9be>] sync_sb_inodes+0x2e/0x40
>Jun 5 16:00:50 fuzzy kernel: [<c017eab2>] writeback_inodes+0xe2/0xf0
>Jun 5 16:00:50 fuzzy kernel: [<c0141168>] balance_dirty_pages+0x98/0x160
>Jun 5 16:00:50 fuzzy kernel: [<c01cfe82>] txn_restart_current+0x22/0x80
>Jun 5 16:00:50 fuzzy kernel: [<c0289a29>] extent_balance_dirty_pages+0x109/0x1e0
>Jun 5 16:00:50 fuzzy kernel: [<c0192d45>] schedulable+0x45/0xc0
>Jun 5 16:00:50 fuzzy kernel: [<c028a1f9>] extent_write_flow+0x6f9/0x16e0
>Jun 5 16:00:50 fuzzy kernel: [<c028b470>] write_extent+0x0/0x50
>Jun 5 16:00:50 fuzzy kernel: [<c02b980d>] append_and_or_overwrite+0x48d/0xb00
>Jun 5 16:00:50 fuzzy kernel: [<c02395e7>] key_by_inode_and_offset_common+0x27/0x250
>Jun 5 16:00:50 fuzzy kernel: [<c02b9f5a>] write_flow+0xda/0x130
>Jun 5 16:00:50 fuzzy kernel: [<c01cce45>] grabbed2free+0x145/0x290
>Jun 5 16:00:50 fuzzy kernel: [<c02ba2fa>] write_file+0x9a/0x110
>Jun 5 16:00:50 fuzzy kernel: [<c02ba6e4>] write_unix_file+0x374/0x560
>Jun 5 16:00:50 fuzzy kernel: [<c0225512>] reiser4_write+0x92/0x1d0
>Jun 5 16:00:50 fuzzy kernel: [<c011e4ad>] release_console_sem+0x7d/0xc0
>Jun 5 16:00:50 fuzzy kernel: [<c015b0de>] vfs_write+0xae/0x130
>Jun 5 16:00:50 fuzzy kernel: [<c015b231>] sys_write+0x51/0x80
>Jun 5 16:00:50 fuzzy kernel: [<c0103123>] syscall_call+0x7/0xb
>Jun 5 16:00:50 fuzzy kernel: Code: ff ff 8b 11 85 d2 0f 84 33 ff ff ff 8b 00 39 c8 0f 85 29 ff ff ff 39 42 04 0f 85 20 ff ff ff b8 44 b6 61 c0 e8 d2 ce 2c 00 89 f6 <0f> 0b 8d 00 b9 a1 4c c0 c7 04 24 ec 3f 4f c0 b8 e0 b1 61 c0 89
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-05 14:50 reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super) Adrian Ulrich
2005-06-06 8:43 ` E.Gryaznova
@ 2005-06-06 8:55 ` Vitaly Fertman
2005-06-06 18:39 ` Adrian Ulrich
2005-06-06 10:31 ` E.Gryaznova
2 siblings, 1 reply; 14+ messages in thread
From: Vitaly Fertman @ 2005-06-06 8:55 UTC (permalink / raw)
To: reiserfs-list; +Cc: Adrian Ulrich
On Sunday 05 June 2005 18:50, Adrian Ulrich wrote:
> Hi,
>
> Well, i managed to crash reiser4 ;-)
>
> I created an iso-image on my reiser4 filesystem (it's my rootfs)
> using mkisofs. mkisofs aborted because the filesystem was full.
> After freeing up some space, i ran mkisofs again and: *bam*
>
> fsck.reiser4 told me to run '--rebuild-sb' but looks like
> it didn't help:
> The System still crashes while creating the ISO
> (Should be 4.1 GiB, but crashes at ~ 3.7 GiB..)
what does 'fsck.reiser4 --check' say now running on this fs?
that no corruption found?
> # fsck.reiser4 --version
> fsck.reiser4 1.0.4
> Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed
> by reiser4progs/COPYING.
>
> # uname -a
> Linux fuzzy 2.6.11.10 #1 SMP Sat May 21 13:17:21 CEST 2005 i686 unknown
> unknown GNU/Linux
>
> * I attached the Syslog output
> * I rand 'debugfs.reiserf -P $device' and can
> provide the output to namesys if they need it
> (9.3 MiB)
>
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-06 8:55 ` Vitaly Fertman
@ 2005-06-06 18:39 ` Adrian Ulrich
2005-06-07 4:57 ` Adrian Ulrich
2005-06-07 7:00 ` Vitaly Fertman
0 siblings, 2 replies; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-06 18:39 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: reiserfs-list
I upgraded to Linux 2.6.11.11 using the -5 reiser4 patch.
It fixed it.. somewhat.. it's still funky:
* mkisofs doesn't crash with the new kernel, yeah!
* after running mkisofs, grub can't read the filesystem anymore..
The filesystem got corrupted. (It was ok before i booted
into 2.6.11.11 and ran mkisofs !)
So i bootet my rescue-system
(Same kernel, reiser4progs 1.0.4. It's on /dev/md3)
Running fsck:
root@fuzzy:~# fsck.reiser4 /dev/md1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Mon Jun 6 20:07:51 2005
Reiser4 fs was detected on /dev/md1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: c3fc85d3-be0d-4d71-9413-376cefcdf8fd
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x5bedb66f
blocks: 9765488
free blocks: 2035573
root block: 4270052
tail policy: 0x2 (smart)
next oid: 0x62d63
file count: 180460
tree height: 4
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid SD plugin set extention: wrong pset member count detected (12).
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat data.
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: broken item found.
FSCK: Node (411219): the node is broken. Pointed from the node (411211), item (0), unit (0). The whole subtree is skipped.
Read nodes 130082
Nodes left in the tree 130081
Leaves of them 127827, Twigs of them 2199
Broken of them 1
Leaves of them 1, Twigs of them 0
Time interval: Mon Jun 6 20:07:54 2005 - Mon Jun 6 20:09:12 2005
CHECKING EXTENT REGIONS.
Read twigs 2199
Time interval: Mon Jun 6 20:09:12 2005 - Mon Jun 6 20:09:15 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Mon Jun 6 20:09:15 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them.
.. ok, again with --build-fs
root@fuzzy:~# fsck.reiser4 --build-fs /dev/md1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will build the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Mon Jun 6 20:09:55 2005
Reiser4 fs was detected on /dev/md1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: c3fc85d3-be0d-4d71-9413-376cefcdf8fd
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x5bedb66f
blocks: 9765488
free blocks: 2035573
root block: 4270052
tail policy: 0x2 (smart)
next oid: 0x62d63
file count: 180460
tree height: 4
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid SD plugin set extention: wrong pset member count detected (12).
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat data.
FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: broken item found. Remove it.
FSCK: Node (411219): The left delimiting key [2a:0(NAME):0:0:0] in the parent node (411211), pos (0/4294967295) does not match the first key [29:1(SD):0:2a:0]
in the node. Fixed.
Read nodes 130082
Nodes left in the tree 130082
Leaves of them 127828, Twigs of them 2199
Corrected nodes 1
Leaves of them 1, Twigs of them 0
Time interval: Mon Jun 6 20:09:58 2005 - Mon Jun 6 20:11:29 2005
CHECKING EXTENT REGIONS.
Read twigs 2199
Time interval: Mon Jun 6 20:11:29 2005 - Mon Jun 6 20:11:32 2005
LOOKING FOR UNCONNECTED NODES
Read nodes 0
Good nodes 0
Leaves of them 0, Twigs of them 0
Time interval: Mon Jun 6 20:11:33 2005 - Mon Jun 6 20:11:33 2005
CHECKING EXTENT REGIONS.
Read twigs 0
Time interval: Mon Jun 6 20:11:33 2005 - Mon Jun 6 20:11:33 2005
INSERTING UNCONNECTED NODES
1. Twigs: done
2. Twigs by item: done
3. Leaves: done
4. Leaves by item: done
Twigs: read 0, inserted 0, by item 0, empty 0
Leaves: read 0, inserted 0, by item 0
Time interval: Mon Jun 6 20:11:33 2005 - Mon Jun 6 20:11:33 2005
CHECKING SEMANTIC TREE
FSCK: Failed to recognize the plugin for the directory [29:0:2a].
FSCK: Trying to recover the directory [29:0:2a] with the default plugin--dir40.
FSCK: The file [29:0:2a] does not have a StatData item. Creating a new one. Plugin dir40.
FSCK: Node (411219), item (0), [29:0:2a] (stat40): wrong size (0), Fixed to (23).
FSCK: Node (411219), item (0), [29:0:2a] (stat40): wrong bytes (0), Fixed to (1150).
Found 180460 objects.
Time interval: Mon Jun 6 20:11:33 2005 - Mon Jun 6 20:15:22 2005
CLEANUPING STORAGE TREE
Removed items 0
Time interval: Mon Jun 6 20:15:22 2005 - Mon Jun 6 20:17:42 2005
***** fsck.reiser4 finished at Mon Jun 6 20:17:42 2005
Closing fs...done
..running again fsck.reiser4 --check : No errors..
I mounted/umounted /dev/md1 3 times: No problems
..running fsck.reiser4 again: no errors.. fine..
So i booted again using /dev/md1 as my rootfs.. No errors so far.
After logging in, i rebooted again to /dev/md3 and started
a fsck on /dev/md1 ..
Now the same thing happens again :-/
# fsck.reiser4 /dev/md1
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************
Fscking the /dev/md1 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Mon Jun 6 20:33:27 2005
Reiser4 fs was detected on /dev/md1.
Master super block (16):
magic: ReIsEr4
blksize: 4096
format: 0x0 (format40)
uuid: c3fc85d3-be0d-4d71-9413-376cefcdf8fd
label: <none>
Format super block (17):
plugin: format40
description: Disk-format for reiser4.
magic: ReIsEr40FoRmAt
flushes: 0
mkfs id: 0x5bedb66f
blocks: 9765488
free blocks: 2035524
root block: 4270046
tail policy: 0x2 (smart)
next oid: 0x62de4
file count: 180460
tree height: 4
key policy: LARGE
CHECKING STORAGE TREE
FSCK: Node (35026), item (0), [29:1(SD):0:2a:0]: does not look like a valid SD
plugin set extention: wrong pset member count detected (12).
FSCK: Node (35026), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat
data.
FSCK: Node (35026), item (0), [29:1(SD):0:2a:0]: broken item found.
FSCK: Node (35026): the node is broken. Pointed from the node (35024), item (0),
unit (0). The whole subtree is skipped.
Read nodes 130082
Nodes left in the tree 130081
Leaves of them 127827, Twigs of them 2199
Broken of them 1
Leaves of them 1, Twigs of them 0
Time interval: Mon Jun 6 20:33:30 2005 - Mon Jun 6 20:34:47 2005
CHECKING EXTENT REGIONS.
Read twigs 2199
Time interval: Mon Jun 6 20:34:47 2005 - Mon Jun 6 20:34:50 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Mon Jun 6 20:34:50 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-06 18:39 ` Adrian Ulrich
@ 2005-06-07 4:57 ` Adrian Ulrich
2005-06-07 7:00 ` Vitaly Fertman
1 sibling, 0 replies; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-07 4:57 UTC (permalink / raw)
To: vitaly; +Cc: reiserfs-list
> Now the same thing happens again :-/
Ok, i know why it only got corrupted after using
the partition as rootfs :
My Reiser4 partition doesn't like to get remounted rw:
Running
1) mount /dev/md1 /somewhere
2) umount /dev/md1
3) mount -o ro /dev/md1 /somewhere
4) umount /dev/md1
works without any problems (fsck is happy)
But if i do:
1) mount -o ro /dev/md1 /somewhere
2) mount -o remount,rw /dev/md1
3) umount /dev/md1
(Almost the same thing would happen
if i use it as rootfs)
..fsck complains again:
CHECKING STORAGE TREE
FSCK: Node (35026), item
(0), [29:1(SD):0:2a:0]: does not look like a valid SD plugin set
extention: wrong pset member count detected (12).
FSCK: Node (35026), item (0), [29:1(SD):0:2a:0]: does not look like a
valid stat data. FSCK: Node (35026), item (0), [29:1(SD):0:2a:0]:
broken item found. FSCK: Node (35026): the node is broken. Pointed from
the node (35024), item (0), unit (0). The whole subtree is skipped.
Read nodes 130082
Nodes left in the
tree 130081 Leaves of them 127827, Twigs of them 2199
Broken of them 1
Leaves of them 1, Twigs of them 0
Time interval: Tue Jun 7 06:51:32 2005 - Tue Jun 7 06:52:48
2005 CHECKING EXTENT REGIONS.
Read twigs
2199
Time interval: Tue Jun 7 06:52:48 2005
- Tue Jun 7 06:52:51 2005 Warn : Fatal corruptions were found.
Semantic pass is skipped.
***** fsck.reiser4 finished at Tue Jun 7 06:52:51 2005
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs
option to fix them.
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-06 18:39 ` Adrian Ulrich
2005-06-07 4:57 ` Adrian Ulrich
@ 2005-06-07 7:00 ` Vitaly Fertman
2005-06-07 11:01 ` Adrian Ulrich
1 sibling, 1 reply; 14+ messages in thread
From: Vitaly Fertman @ 2005-06-07 7:00 UTC (permalink / raw)
To: reiserfs-list; +Cc: Adrian Ulrich
On Monday 06 June 2005 22:39, Adrian Ulrich wrote:
> I upgraded to Linux 2.6.11.11 using the -5 reiser4 patch.
>
>
> It fixed it.. somewhat.. it's still funky:
>
>
> * mkisofs doesn't crash with the new kernel, yeah!
> * after running mkisofs, grub can't read the filesystem anymore..
> The filesystem got corrupted. (It was ok before i booted
> into 2.6.11.11 and ran mkisofs !)
>
> So i bootet my rescue-system
> (Same kernel, reiser4progs 1.0.4. It's on /dev/md3)
>
> Running fsck:
>
> root@fuzzy:~# fsck.reiser4 /dev/md1
> *******************************************************************
> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
> *******************************************************************
>
> Fscking the /dev/md1 block device.
> Will check the consistency of the Reiser4 SuperBlock.
> Will check the consistency of the Reiser4 FileSystem.
> Continue?
> (Yes/No): Yes
> ***** fsck.reiser4 started at Mon Jun 6 20:07:51 2005
> Reiser4 fs was detected on /dev/md1.
> Master super block (16):
> magic: ReIsEr4
> blksize: 4096
> format: 0x0 (format40)
> uuid: c3fc85d3-be0d-4d71-9413-376cefcdf8fd
> label: <none>
>
> Format super block (17):
> plugin: format40
> description: Disk-format for reiser4.
> magic: ReIsEr40FoRmAt
> flushes: 0
> mkfs id: 0x5bedb66f
> blocks: 9765488
> free blocks: 2035573
> root block: 4270052
> tail policy: 0x2 (smart)
> next oid: 0x62d63
> file count: 180460
> tree height: 4
> key policy: LARGE
>
>
> CHECKING STORAGE TREE
> FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid SD plugin set extention: wrong pset member count detected (12).
> FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat data.
> FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: broken item found.
> FSCK: Node (411219): the node is broken. Pointed from the node (411211), item (0), unit (0). The whole subtree is skipped.
there was a format change to work with encryption plugin in
-5 reiser4 patch. progs do not have its support yet. grub works
through the progs code so its the same problem, mkisofs is not
relevant here.
--
Thanks,
Vitaly Fertman
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-07 7:00 ` Vitaly Fertman
@ 2005-06-07 11:01 ` Adrian Ulrich
2005-06-07 10:32 ` Vitaly Fertman
0 siblings, 1 reply; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-07 11:01 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: reiserfs-list
Hi Vitaly,
> there was a format change to work with encryption plugin in
> -5 reiser4 patch. progs do not have its support yet. grub works
> through the progs code so its the same problem, mkisofs is not
> relevant here.
I don't think thats the problem:
It looks like a remount bug:
See <20050607065750.4dd203b9.reiser4@blinkenlights.ch> (my other mail)
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-07 11:01 ` Adrian Ulrich
@ 2005-06-07 10:32 ` Vitaly Fertman
2005-06-07 12:10 ` Adrian Ulrich
0 siblings, 1 reply; 14+ messages in thread
From: Vitaly Fertman @ 2005-06-07 10:32 UTC (permalink / raw)
To: Adrian Ulrich; +Cc: reiserfs-list
On Tuesday 07 June 2005 15:01, Adrian Ulrich wrote:
> Hi Vitaly,
>
> > there was a format change to work with encryption plugin in
> > -5 reiser4 patch. progs do not have its support yet. grub works
> > through the progs code so its the same problem, mkisofs is not
> > relevant here.
>
> I don't think thats the problem:
I am about the particular fsck message that appeares when you
use -5 reiser4 patch:
> > FSCK: Node (411219), item (0), [29:1(SD):0:2a:0]: does not look
> > like a valid SD plugin set extention: wrong pset member count detected (12).
> It looks like a remount bug:
> See <20050607065750.4dd203b9.reiser4@blinkenlights.ch> (my other mail)
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-07 10:32 ` Vitaly Fertman
@ 2005-06-07 12:10 ` Adrian Ulrich
2005-06-07 11:17 ` Raymond A. Meijer
0 siblings, 1 reply; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-07 12:10 UTC (permalink / raw)
To: Vitaly Fertman; +Cc: reiserfs-list
> I am about the particular fsck message that appeares when you
> use -5 reiser4 patch:
Ok, but i think it's still strange:
This message only re-appears if i do a:
mount -o ro /dev/md1 /somewhere
mount -o remount,rw /dev/md1 /somewhere <--- !!!
umount /dev/md1
fsck.reiser4 /dev/md1 <-- fsck will complain..
If i do
mount /dev/md1 /somewhere
umount /dev/md1
fsck.resier4 /dev/md1
, fsck does *not* print any errors.
(I'm using -5 in both cases)
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-07 12:10 ` Adrian Ulrich
@ 2005-06-07 11:17 ` Raymond A. Meijer
2005-06-07 16:58 ` Adrian Ulrich
0 siblings, 1 reply; 14+ messages in thread
From: Raymond A. Meijer @ 2005-06-07 11:17 UTC (permalink / raw)
To: reiserfs-list
On Tuesday 7 June 2005 15:10, Adrian Ulrich wrote:
> Ok, but i think it's still strange:
>
> This message only re-appears if i do a:
>
> mount -o ro /dev/md1 /somewhere
> mount -o remount,rw /dev/md1 /somewhere <--- !!!
> umount /dev/md1
> fsck.reiser4 /dev/md1 <-- fsck will complain..
What happens if you do:
mount -o ro /dev/md1 /somewhere
mount -o remount,rw /dev/md1 <--- (no '/somewhere' !!!)
umount /dev/md1
fsck.reiser4 /dev/md1
???
Ray
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-07 11:17 ` Raymond A. Meijer
@ 2005-06-07 16:58 ` Adrian Ulrich
0 siblings, 0 replies; 14+ messages in thread
From: Adrian Ulrich @ 2005-06-07 16:58 UTC (permalink / raw)
To: reiserfs-list
> mount -o remount,rw /dev/md1 <--- (no '/somewhere' !!!)
Hmm... this seems to make fsck happy :)
But once i bootet using /dev/md1 as my rootfs, fsck.reiser4
complains again after the next reboot (into my rescue fs)
-- Adrian
--
We're working on it, slowly but surely...or not-so-surely in the spots
we're not so sure... -- Larry Wall
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super)
2005-06-05 14:50 reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super) Adrian Ulrich
2005-06-06 8:43 ` E.Gryaznova
2005-06-06 8:55 ` Vitaly Fertman
@ 2005-06-06 10:31 ` E.Gryaznova
2005-06-06 10:23 ` Adrian Ulrich
2 siblings, 1 reply; 14+ messages in thread
From: E.Gryaznova @ 2005-06-06 10:31 UTC (permalink / raw)
To: Adrian Ulrich; +Cc: reiserfs-list
Adrian Ulrich wrote:
>Hi,
>
>Well, i managed to crash reiser4 ;-)
>
>I created an iso-image on my reiser4 filesystem (it's my rootfs)
>using mkisofs. mkisofs aborted because the filesystem was full.
>After freeing up some space, i ran mkisofs again and: *bam*
>
>fsck.reiser4 told me to run '--rebuild-sb' but looks like
>it didn't help:
> The System still crashes while creating the ISO
> (Should be 4.1 GiB, but crashes at ~ 3.7 GiB..)
>
>
># fsck.reiser4 --version
>fsck.reiser4 1.0.4
>Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed
>by reiser4progs/COPYING.
>
># uname -a
>Linux fuzzy 2.6.11.10 #1 SMP Sat May 21 13:17:21 CEST 2005 i686 unknown
>unknown GNU/Linux
>
>
what reiser4 patch do you use for this kernel?
Thanks,
Lena
>* I attached the Syslog output
>* I rand 'debugfs.reiserf -P $device' and can
> provide the output to namesys if they need it
> (9.3 MiB)
>
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2005-06-07 16:58 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-05 14:50 reiser4 panicked cowardly: assertion failed: hint->blk < reiser4_block_count(super) Adrian Ulrich
2005-06-06 8:43 ` E.Gryaznova
2005-06-06 8:25 ` Adrian Ulrich
2005-06-06 8:55 ` Vitaly Fertman
2005-06-06 18:39 ` Adrian Ulrich
2005-06-07 4:57 ` Adrian Ulrich
2005-06-07 7:00 ` Vitaly Fertman
2005-06-07 11:01 ` Adrian Ulrich
2005-06-07 10:32 ` Vitaly Fertman
2005-06-07 12:10 ` Adrian Ulrich
2005-06-07 11:17 ` Raymond A. Meijer
2005-06-07 16:58 ` Adrian Ulrich
2005-06-06 10:31 ` E.Gryaznova
2005-06-06 10:23 ` Adrian Ulrich
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.