http://bugme.osdl.org/show_bug.cgi?id=2155
------- Additional Comments From geek@xxxxxxxxxxxx 2004-04-01 21:42 -------
Hi, Emilio
Sorry for my delayed response.
The kernel that I encountered I/O sync problem (beginning message submitted in
this bugreport) was compiled by GCC 3.3.3.
However, for the comment #3, it seems to be an independent issue. I've tried it
with 2.4.25 and XFS/Reiserfs/Ext3 with or without LVM, the problem can be
reproduced under all these conditions.
Here is some interesting message you might be interested, and it happens on my
box rulelessly and daily.
############################################################################
tux:/etc/init.d# debsums -s
debsums: checksum mismatch python2.3 file usr/lib/python2.3/Cookie.py
#debsums is a debian file integrity-check tool like tripwire
#Then I copied an intact Cookie.py from another system to diff
tux:/etc/init.d# diff /usr/lib/python2.3/Cookie.py /home/geek/Cookie.py
467,469c467,468
< uration state."""
< if self._defaults:
< fp.writ self.key, repr(self.value) )
---
> return '<%s: %s=%s>' % (self.__class__.__name__,
> self.key, repr(self.value) )
#Look at the first line: uration state."""
#Let's run grep -r 'uration state.\"\"\"' in /usr/lib/python2.3/
tux:/usr/lib/python2.3# grep -r 'uration state.\"\"\"' *
ConfigParser.py: """Write an .ini-format representation of the
configuration state."""
Cookie.py: uration state."""
#The mismatched content is actually some string from another file in the same
direcotry.
########################################################################
Really odd, huh?
I am not sure if the above two problems has any relation between them, or maybe
I'd better submit the comment #3 as an indepdent bug?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|