Skip to contentSkip to conversation

active after unmount?

DISCUSSION Brian J. Watson 4 participants 6 messages Apr 19, 2001 – Apr 20, 2001

lore
Share & tools
lore
#1 lore raw
In reply to Brian J. Watson
Quoted 10 lines · Brian J. Watson
Quoted 8 lines

Unmounting a SCSI disk device succeeded, and yielded:

Red Hat Linux release 6.2 (Zoot)
Kernel 2.4.3 on a 2-processor i686

chico login: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...

Quoted 6 lines

This message comes out of kill_super(). I would guess that somebody's mismanaging VFS refcounts, but there's not enough info here to diagnose the problem. What filesystem are you using? Is this reproducible? What do you have to do between mounting and unmounting to reproduce the problem?

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

ext2<<<<<<, haven't reproduced it yet, on a 2x686 256MB memory,

SCSI midlayer default, with 2.4.3.

-matt

Brian J. Watson

author
#0 lore raw
Quoted 8 lines

Unmounting a SCSI disk device succeeded, and yielded:

Red Hat Linux release 6.2 (Zoot)
Kernel 2.4.3 on a 2-processor i686

chico login: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...

This message comes out of kill_super(). I would guess that somebody's mismanaging VFS refcounts, but there's not enough info here to diagnose the problem. What filesystem are you using? Is this reproducible? What do you have to do between mounting and unmounting to reproduce the problem?

--
Brian Watson
Compaq Computer

#2 lore raw
Quoted 14 lines · Matthew Jacob
Quoted 10 lines · Brian J. Watson
Quoted 8 lines

Unmounting a SCSI disk device succeeded, and yielded:

Red Hat Linux release 6.2 (Zoot)
Kernel 2.4.3 on a 2-processor i686

chico login: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...

Quoted 7 lines
Quoted 6 lines

This message comes out of kill_super(). I would guess that somebody's mismanaging VFS refcounts, but there's not enough info here to diagnose the problem. What filesystem are you using? Is this reproducible? What do you have to do between mounting and unmounting to reproduce the problem?

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

ext2<<<<<<, haven't reproduced it yet, on a 2x686 256MB memory,

SCSI midlayer default, with 2.4.3.

I've seen it a lot with the autofs. You can check what it is with the following small debug patch.

Index: fs/inode.c
===================================================================
RCS file: /cvs/linux/fs/inode.c,v
retrieving revision 1.122

inode.c +7 -0
diff -u -u -r1.122 inode.c
@@ -443,6 +443,13 @@
 			count++;
 			continue;
 		}
+#if 1
+		printk("inode %u:%lu busy\n", inode->i_dev, inode->i_ino); 
+		if (inode->i_dentry.next != &inode->i_dentry) 
+			printk("for file %s\n", 
+	list_entry(inode->i_dentry.next, struct dentry, d_alias)->d_name.name);  
+#endif		
+		
 		busy = 1;
 	}
 	/* only unused inodes may be cached with i_count zero */

-Andi

#3 lore raw

'kay, great, thanks.. I'll put it in and see if things show up again

#4 lore raw
Quoted 2 lines · Matthew Jacob

'kay, great, thanks.. I'll put it in and see if things show up again

Guys, it's a known bug, fixed in 2.4.4-pre3. See the change to fs/super.c between 2.4.4-pre2 and 2.4.4-pre3 - it's quite small.

#5 lore raw

Double cool then.

Quoted 10 lines · Matthew Jacob
Quoted 3 lines

'kay, great, thanks.. I'll put it in and see if things show up again

Guys, it's a known bug, fixed in 2.4.4-pre3. See the change to fs/super.c between 2.4.4-pre2 and 2.4.4-pre3 - it's quite small.