Messages in this thread | | | Date | Tue, 8 Dec 1998 00:48:51 +0100 (CET) | From | Rik van Riel <> | Subject | Re: WTF is this in fs/super.c |
| |
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).
regards,
Rik -- the flu hits, the flu hits, the flu hits -- MORE +-------------------------------------------------------------------+ | Linux memory management tour guide. H.H.vanRiel@phys.uu.nl | | Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ | +-------------------------------------------------------------------+
- 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/
| |