On Mon, 28 Jan 2008 20:25:22 -0600 Kevin Dupuy
On Sat, 2008-01-26 at 06:02 -0500, Aaron Kulkis wrote:
Stephen Berman wrote:
Starting four days ago, the kernel sends bogus i_mode messages after automatic beagle indexing, like this:
Jan 25 21:15:02 escher su: (to beagleindex) root on none Jan 25 21:15:02 escher su: (to beagleindex) root on none Jan 25 21:18:09 escher syslog-ng[2198]: SIGHUP received, restarting syslog-ng Jan 25 21:18:10 escher syslog-ng[2198]: new configuration initialized Jan 25 21:18:36 escher kernel: klogd 1.4.1, ---------- state change ---------- Jan 25 21:19:07 escher su: (to nobody) root on none Jan 25 21:19:07 escher su: (to nobody) root on none Jan 25 21:19:11 escher su: (to nobody) root on none Jan 25 21:19:20 escher syslog-ng[2198]: last message repeated 4 times Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (33060) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30072) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (31460) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30060) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (30462) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (31462) Jan 25 21:19:20 escher kernel: init_special_inode: bogus i_mode (57553) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (30057) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (30170) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (72145) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (71145) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (55440) Jan 25 21:19:21 escher kernel: init_special_inode: bogus i_mode (35063)
Can anyone tell me what this means, and is it a cause for concern?
What it means is that Beagle has serious problems, something which several people on this list seem to have a very great difficulty in understanding.
I'm afraid this may be independent of whatever problems beagle may have; I suspect a hardware problem, maybe (and if so, hopefully only) bad RAM, though I ran memtest for seven hours (15 full passes) without getting a single error. Still, it might be helpful to find out why beagle is eliciting these messages (and continues to do so).
Delete beagle. It's junk.
You'll probably want to file a bug. I haven't seen that before. Thanks.
I will, perhaps it will generate useful feedback. Steve Berman -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org