Gord Sipko(deleted)
|
Proc32 Crash, tracelogger Q's...
|
Gord Sipko(deleted)
03/08/2008 3:59 PM
post5638
|
Proc32 Crash, tracelogger Q's...
I had a crash of Proc32 4.25Q. Fortunately tracelogger was running and has captured some useful info. I need some help
with the translation and interpretation of two traceinfo messages.
1) "tiomestamp 00003011 bmap failure 102 on /". etc/config/traceinfo shows this message comes from Fsys, w/ minor code
17, but what does the 102 mean?
2) "timestamp 00002007 000003F8". There is no entry in /etc/config/traceinfo for Dev with this minor code. 3F8 must
pointing to /dev/ser1. The problem is ..?
The raw tracelogger file for 2hrs runtime on the day of the crash is 33Meg and most of the messages are the two shown
above. I have seperated the "crash" cpu & hd to assist in problem isolation. The hd in another cpu is operating
without any problem and I have been able to recover most files, however some are truncated. dcheck is running as this
message is being typed.
Gord
|
|
|