Re: odd VFS message

Bill Hawes (
Sun, 28 Sep 1997 09:00:09 -0400

firewind wrote:
> After upgrading to kernel 2.1.57, I began getting this message whenever I
> do 'umount /dev/hdb1', an MSDOS FAT partition:
> Sep 28 00:05:32 metroid kernel: VFS: Busy inodes after unmount. Self-destruct
> in 5 seconds. Bye-bye..
> This message never appeared before 2.1.57, does not appear on umount'ing
> of other FAT partitions, and a quick reboot to DOS and a run of NDD shows
> no errors on the drive, so apparently VFS was exaggerating about the
> self-destruct part. :)
> So what is it that VFS is trying to tell me here?

The self-destruct message is one of those never-supposed-to-appear
types. It means that the device appeared to unmount successfully, but
afterwards there were still busy inodes for that device.

It probably means there's a programming error in the msdos fs that's
leaving an elevated inode use count. Unfortunately, the inodes don't
really self-destruct, so there's a small probability the msdos inode
could get used with whatever you mount next on the same superblock. (Not

Is this problem repeatable for you? Someone familiar with msdos fs
should track it down, and it would help to have a test case.