On Tue, 2008-01-29 at 14:12 +0100, Stephen Berman wrote: > On Mon, 28 Jan 2008 20:25:22 -0600 Kevin Dupuy <[EMAIL PROTECTED]> wrote:
> >> > 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). These appear to be file system errors. If they are indeed related to beagle its probably because its trying to read something on the filesystem that is corrupt or has dangling symlinks . Its noticeable that the errors show up 4 minutes after the beagle system wide index process starts, not immediately. Possibly you want to try fsck (and maybe back up your data). I added a comment to your bug as well. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
