lkml.org 
[lkml]   [1998]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: WTF is this in fs/super.c


On Tue, 8 Dec 1998, Rik van Riel wrote:

> On Mon, 7 Dec 1998, Shaw Carruthers wrote:
>
> > This witty message just made my day( kernel 2.1.131 + ac4):
> >
> > /* Forget any remaining inodes */
> > if (invalidate_inodes(sb)) {
> > printk("VFS: Busy inodes after unmount. "
> ^
> Hey! Somebody found the missing 'n'. I guess it's time
> to return it to Bell Labs (or take it to the OpenGroup).
>
> > "Self-destruct in 5 seconds. Have a nice
> > day...\n");
> > }
> >
> > What's up Doc?
>
> It means that there were still busy inodes left in a filesystem
> after the filesystem was umounted. This is something that should
> never happen. Instead the filesystem should refuse to umount if
> there are still files/inodes in use on it.
>
> This could either be a bug in the filesystem (what filesystem
> were you trying to umount?), some strange locking problem
> (Alan, what changed?) or random memory corruption...
>
> If you answer the above questions I'm pretty sure it'll
> ring a bell with somebody (who in turn will fix it).

VFAT? That's what the bug in rename() should give.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:0.123 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site