I try to use log4j to record log to a disk

Project:JNode FS
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:won't fix
Description

I try to use log4j to record log to a disk file(ext2, or fat) so that to make debug easy.

log4j.properties is:

log4j.rootLogger=DEBUG, A1, A2

log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.Threshold=INFO
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%-5p [%c{1}]: %m%n

log4j.appender.A2=org.apache.log4j.FileAppender
log4j.appender.A2.File=/devices/hdd0/jnode.log
log4j.appender.A2.Append=true

log4j.appender.A2.layout=org.apache.log4j.PatternLayout
log4j.appender.A2.layout.ConversionPattern=%r [%t] %p %c %x - %m%n

on the command line, type : log4j log4j.properties
it come out a kernel panic.
devices/hdd0 is ext3 filesystem mount as ext2.
after panic, the inode seem to be corrupted.

A possible reason

Submitted by lsantha on Wed, 10/19/2005 - 05:22.

might be a stack overflow produced by an exception thrown and logged in the file system code which is writing a logrecord to a file.
Look for the kernel debugger feature which sends its output to a serial line. You might need a second PC for this though.

Levente

#1

Submitted by Peter on Thu, 08/21/2008 - 19:18.

Both ext2 and jfat are known to still have bugs but the supplied information is to unspecific to work on it. Please supply additional debug output (using kdb) or a testcase. Marking it as won't fix for the moment.