Weird File Change in Debian Sarge
My box is a P4 Xeon whitebox server w/ 1Gram, 3ware
7506-8 raid card hooked
with 4x 160G maxtor HDD as RAID 5.
Debian Sarge
Plain 2.6.3 kernel
LVM on root partition.
XFS(built as module) filesystem on all partitions
except /boot which runs on
reiserfs
I have lots of stories to tell about this server.
The first weird thing is I found file write operatoin
cannot be sync to HD
timely.
Check this link for detail.
http://bugzilla.kernel.org/show_bug.cgi?id=2155
The second weird thing is
couple of days ago, I installed debsums on my sarge
box. debsums reported
some files under /usr are checksum mismatch.
(I am sure system is not compromised)
I reinstalled those damaged file and keep observing.
Since then, everyday, there will be one or two files
got reported as
checksum mismatch.
I copied these files to other sarge box and run diff
to recheck. The files
are definitely modified, they are still usable tho.
And if I just leave those changed files alone,
sometimes, couple of hours
later, debsums might report no error.
I don't think it's a hardware problem.
So anyone have the similiar experience or hear of this
kind of weirdness?
Any information is appreciated.
The following files are checksum mismatch mostly.
debsums: checksum mismatch links file
usr/bin/links.main
debsums: checksum mismatch dpkg file usr/bin/dpkg
debsums: checksum mismatch libglib2.0-0 file
usr/lib/libglib-2.0.so.0.200.3
debsums: checksum mismatch sysstat file usr/bin/iostat
debsums: checksum mismatch libglib2.0-0 file
usr/lib/libglib-2.0.so.0.200.3
debsums: checksum mismatch python2.3 file
usr/lib/python2.3/Cookie.py
__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
Reply to: