Re: /var/log messages question

Alejandro Lopez <[email protected]> Sat, 29 Jan 2011 10:14:23 +0100
Newsgroups gmane.linux.mandrake.expert
Message-ID <1296292463.22253.2.camel@Nokia-N900>
----- Mensaje original -----
> On Fri, 28 Jan 2011 08:53:01 pm Barry Jackson wrote:
> > On 28/01/11 02:01, Phil wrote:
> > > Thank you for reading this.
> > > 
> > > The following is being written to the /var/log/messages file twice
> > > every second.
> > > 
> > > Jan 28 11:47:17 localhost kernel: VFS: busy inodes on changed media
> > > or resized disk sr0
> > > 
> > > This has only occurred since a fresh installation of 2010.2 and it
> > > seems to occur after I have connected to the Internet and so I
> > > suspect it has something to do with the fetched update list. If I
> > > disconnect and then reboot the message doesn't seem to reappear
> > > until the next time that I connect to the Internet. Beyond that I
> > > don't have much of an idea of how to prevent this.
> > > 
> > > Can anyone offer a suggestion?
> > 
> > Just a very wild guess, but have you still got the CD/DVD install media
> > listed in your media sources? If so try removing them.
> 
> Thank you Barry for your reply.
> 
> I do have the following DVD sources listed plus many other on-line
> sources:
> 
> CD-ROM Main media
> CD-ROM updates media
> CD-ROM contrib updates media
> CD-ROM Contrib media

If you have the official Mandriva online sources, you don't need the CD/DVD sources as everything on those is also present on the online ones.

Alejandro

> 
> I notice that the message is written to the /var/log/messages file once
> the     "you have updates" dialogue is displayed, but only if the DVD is
> not mounted.
> 
> So the easy fix is to leave the DVD in the drive during the time that
> I'm on- line. Something that I'm very likely to forget to do.
> 
> I haven't removed the DVD sources from the list because I may want to
> add a   new application at some time without the need to go on-line and
> this problem   has never occurred during the past 12 years.
> 
> A Google search shows that this problem has occurred in the past and
> that it   was due to a bug of some kind. Could that be the case again or
> have I simply   misunderstood something very basic?
>   
> -- 
> Regards,
> Phil