Displaying 2 results from an estimated 2 matches for "ext2_read_sup".
Did you mean:
ext2_read_super
2002 Jun 11
1
another oops, this time with 2.4.18-4
...Ignoring ksyms_base entry
Warning (compare_maps): ksyms_base symbol vmalloc_to_page_R__ver_vmalloc_to_page not found in System.map. Ignoring ksyms_base entry
Jun 11 12:11:31 castor kernel: invalid operand: 0000
Jun 11 12:11:31 castor kernel: CPU: 3
Jun 11 12:11:31 castor kernel: EIP: 0010:[ext2_read_super+810/1956] Not tainted
Jun 11 12:11:31 castor kernel: EFLAGS: 00010282
Jun 11 12:11:31 castor kernel: eax: 0000001d ebx: 00000000 ecx: c034de48 edx: 00005c81
Jun 11 12:11:31 castor kernel: esi: d3a5bab0 edi: f795b800 ebp: 00000018 esp: f7463e40
Jun 11 12:11:31 castor kernel: ds:...
2005 Jul 25
1
Strange corruption (?) problem
...t all.
This partition was corrupted somehow in the past, but was completely
recovered by fsck, although probably it now makes use of a backup
superblock (when I try to mount the partition without any parameters
the kernel mounts it as ext2 with the warning "EXT2-fs warning (device
ide0(3,65)): ext2_read_super: mounting ext3 filesystem as ext2", so I always
specify the fs type by -t ext3 parameter). I don't know whether this is relevant
to the current problem.
Any ideas?