[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

oops in ext3_new_block / 2.2.19/0.0.7a



Hi,
i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a
fsck 1.21


ksymoops 2.3.4 on i686 2.2.19.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.2.19/ (default)
     -m /boot/System.map-2.2.19 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Unable to handle kernel paging request at virtual address 4ed2e400
current->tss.cr3 = 0aacf000, %cr3 = 0aacf000
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c0142ba3>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 00000000   ebx: 00000400   ecx: 00000100   edx: 00000000
esi: ce24cc00   edi: 4ed2e400   ebp: caac9e1c   esp: caac9dec
ds: 0018   es: 0018   ss: 0018
Process mutt (pid: 1172, process nr: 64, stackpage=caac9000)
Stack: c7c4e4c8 c014ff63 c7233a20 ced65160 ced31620 ce24cc30 cec44000 cec44440 
       cfa176c0 00000002 ce8e16a0 cf531020 ced66734 c014574d c7233a20 c7c4e4c8 
       00004a41 00000000 00000000 caac9f74 00000000 c014ffa8 00000000 00000023 
Call Trace: [<c014ff63>] [<c014574d>] [<c014ffa8>] [<c014fffd>] [<c0145d5a>] [<c0146136>] [<c0143bd2>] 
       [<c01267c0>] [<c010b018>] [<c010a0b8>] [<c010002b>] 
Code: f3 ab f6 c3 02 74 02 66 ab f6 c3 01 74 01 aa 83 c4 f8 6a 01 

>>EIP; c0142ba3 <ext3_new_block+557/6c8>   <=====
Trace; c014ff63 <do_get_write_access+403/42c>
Trace; c014574d <ext3_alloc_block+39/44>
Trace; c014ffa8 <journal_get_write_access+1c/7c>
Trace; c014fffd <journal_get_write_access+71/7c>
Trace; c0145d5a <block_getblk+16a/31c>
Trace; c0146136 <ext3_getblk+22a/238>
Trace; c0143bd2 <ext3_file_write+566/95c>
Trace; c01267c0 <sys_write+d4/104>
Trace; c010b018 <common_interrupt+18/20>
Trace; c010a0b8 <system_call+34/38>
Trace; c010002b <startup_32+2b/11d>
Code;  c0142ba3 <ext3_new_block+557/6c8>
00000000 <_EIP>:
Code;  c0142ba3 <ext3_new_block+557/6c8>   <=====
   0:   f3 ab                     repz stos %eax,%es:(%edi)   <=====
Code;  c0142ba5 <ext3_new_block+559/6c8>
   2:   f6 c3 02                  test   $0x2,%bl
Code;  c0142ba8 <ext3_new_block+55c/6c8>
   5:   74 02                     je     9 <_EIP+0x9> c0142bac <ext3_new_block+560/6c8>
Code;  c0142baa <ext3_new_block+55e/6c8>
   7:   66 ab                     stos   %ax,%es:(%edi)
Code;  c0142bac <ext3_new_block+560/6c8>
   9:   f6 c3 01                  test   $0x1,%bl
Code;  c0142baf <ext3_new_block+563/6c8>
   c:   74 01                     je     f <_EIP+0xf> c0142bb2 <ext3_new_block+566/6c8>
Code;  c0142bb1 <ext3_new_block+565/6c8>
   e:   aa                        stos   %al,%es:(%edi)
Code;  c0142bb2 <ext3_new_block+566/6c8>
   f:   83 c4 f8                  add    $0xfffffff8,%esp
Code;  c0142bb5 <ext3_new_block+569/6c8>
  12:   6a 01                     push   $0x1


1 warning issued.  Results may not be reliable.


I guess this is due to a write on /usr which is full:


root ping:~# df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/sda6               253856     55578    185122  23% /
/dev/sda7              1240608   1181764         0 100% /usr
/dev/sda8               744768    181140    525178  26% /var
/dev/sda9               496789      8247    462892   2% /tmp
/dev/sda10             5682768   5236668    152674  97% /home
/dev/hda5              6099652   3802760   1982024  66% /var/tmp
root ping:~# tune3fs -l /dev/sda7
tune2fs 1.21-WIP, 01-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          565f9dec-eabe-11d3-987c-00a0c94be5f8
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal needs_recovery
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              320640
Block count:              640504
Reserved block count:     32025
Free blocks:              29422
Free inodes:              257386
First block:              0
Block size:               2048
Fragment size:            2048
Blocks per group:         16384
Fragments per group:      16384
Inodes per group:         8016
Inode blocks per group:   501
Last mount time:          Thu Jun 21 19:21:28 2001
Last write time:          Thu Jun 21 19:21:28 2001
Mount count:              7
Maximum mount count:      20
Last checked:             Fri Jun 15 17:49:26 2001
Check interval:           15552000 (6 months)
Next check after:         Wed Dec 12 16:49:26 2001
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:		  128
Journal UUID:             <none>
Journal inode:            1054
Journal device:	          0x0000
First orphan inode:       0


Flo
-- 
Florian Lohoff                  flo rfc822 org             +49-5201-669912
     Why is it called "common sense" when nobody seems to have any?





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]