I just inherited a 7.2 RedHat server to admin. I noticed that the backup
failed and started to investigate. I looked in the /var/log/messages and
noticed the following errors:

Sep 16 04:30:01 ftpsrvr kernel:  <1>Unable to handle kernel paging
request at v
irtual address 3fa920d0
Sep 16 04:30:01 ftpsrvr kernel:  printing eip:
Sep 16 04:30:01 ftpsrvr kernel: c0147224
Sep 16 04:30:01 ftpsrvr kernel: *pde = 00000000
Sep 16 04:30:01 ftpsrvr kernel: Oops: 0000
Sep 16 04:30:01 ftpsrvr kernel: CPU:    0
Sep 16 04:30:01 ftpsrvr kernel: EIP:    0010:[d_lookup+100/272]
Sep 16 04:30:01 ftpsrvr kernel: EIP:    0010:[<c0147224>]
Sep 16 04:30:01 ftpsrvr kernel: EFLAGS: 00010203
Sep 16 04:30:01 ftpsrvr kernel: eax: c13c0000   ebx: 3fa920c0   ecx:
0000000f  
 edx: dba8d71f
Sep 16 04:30:01 ftpsrvr kernel: esi: c8cb9f9c   edi: 00007fff   ebp:
3fa920d0  
 esp: c8cb9ee8
Sep 16 04:30:01 ftpsrvr kernel: ds: 0018   es: 0018   ss: 0018
Sep 16 04:30:01 ftpsrvr kernel: Process chmod (pid: 10962,
stackpage=c8cb9000)
Sep 16 04:30:01 ftpsrvr kernel: Stack: c13fa920 c2dbd035 dba8d71f
00000015 c2db
d035 c8cb9f9c c8cb9f54 c2dbd04a 
Sep 16 04:30:01 ftpsrvr kernel:        c013ed00 cd5c5e40 c8cb9f54
c2dbd035 c013
f479 cd5c5e40 c8cb9f54 00000000 
Sep 16 04:30:01 ftpsrvr kernel:        00000008 00000000 00000000
c01497b7 0000
0041 c8cb9f98 00000286 c013ecd0 
Sep 16 04:30:01 ftpsrvr kernel: Call Trace: [<dba8d71f>]
[cached_lookup+16/80] 
[path_walk+1401/2016] [notify_change+231/288] [path_release+16/48] 
Sep 16 04:30:01 ftpsrvr kernel: Call Trace: [<dba8d71f>] [<c013ed00>]
[<c013f47
9>] [<c01497b7>] [<c013ecd0>] 
Sep 16 04:30:01 ftpsrvr kernel:    [<dba8d71f>] [__user_walk+58/96]
[sys_lstat6
4+19/112] [system_call+51/56] 
Sep 16 04:30:01 ftpsrvr kernel:    [<dba8d71f>] [<c013fbaa>]
[<c013ca23>] [<c01
06f2b>] 
Sep 16 04:30:01 ftpsrvr kernel: 
Sep 16 04:30:01 ftpsrvr kernel: Code: 8b 6d 00 39 53 44 0f 85 80 00 00
00 8b 44
 24 24 39 43 0c 75 

I tried to run "ksymoops", but got no output even after I let it run for
45 minutes.

I noticed that it happened when anything hit a certain file. I tried to
delete the file, then it's directory, but would only get a "segmentation
fault". I then moved the directory to see if I could delete it after
that, but still no luck. I than reboot the server and finally was able
to remove the file. 

I was able to solve the problem, but I have no clue what the actual
problem was or if it's a sign of bigger things to come. I would be
forever grateful if someone could actually explain what had happen.

Thanks,


CWilson


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to