After booting with 2.4.15pre7 for the first time, I got a screeful of
messages saying: "invalidate: busy buffer".
>From my syslog:
Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
Nov 20 21:20:27 oberon last message repeated 55 times
Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
Since I do not know what this should tell me, I'd appreciate if
somebody told me what this is all about. I can, of course, provide
more information if necessary. But since I don't have a clue on what
this would be related to (other that the printk seems to be in
buffer.c) I have no idea of what information might be useful.
Suonp??...
Hello,
I am use 2.4.15-pre5, hardware M/B Intel L440GX+ with onboard AIC7890.
After boot:
...
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
...
I use ext3.
Once you wrote about "2.4.15pre7: kernel: invalidate: busy buffer":
> After booting with 2.4.15pre7 for the first time, I got a screeful of
> messages saying: "invalidate: busy buffer".
>
> From my syslog:
>
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon last message repeated 55 times
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
>
> Since I do not know what this should tell me, I'd appreciate if
> somebody told me what this is all about. I can, of course, provide
> more information if necessary. But since I don't have a clue on what
> this would be related to (other that the printk seems to be in
> buffer.c) I have no idea of what information might be useful.
>
> Suonp??...
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
bye.
Andrey Nekrasov, SpyLOG.
On Nov 20, 2001 21:31 +0200, Samuli Suonpaa wrote:
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon last message repeated 55 times
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
> Nov 20 21:20:27 oberon kernel: invalidate: dirty buffer
> Nov 20 21:20:27 oberon kernel: invalidate: busy buffer
>
> Since I do not know what this should tell me, I'd appreciate if
> somebody told me what this is all about. I can, of course, provide
> more information if necessary. But since I don't have a clue on what
> this would be related to (other that the printk seems to be in
> buffer.c) I have no idea of what information might be useful.
It means you are using LVM on a new kernel. Some day, the LVM code
will be changed so it doesn't do that. For now it is not a real
error, just a warning. It doesn't cause any real problems.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/