freeing free inodes & ring corruption...

Jeremy Boulton (boultonj@torch.caltech.edu)
Wed, 6 Nov 1996 20:45:30 -0800


Hi, all. I'm getting some unusual messages, and I can't tell exactly what
is causing them, so I am hoping someone can interpret them for me. Although
these look to me like things that should not happen, my system has not
crashed at this point. I have the impression that this might be related to
mounting and unmounting with samba, but I'm not sure if that's the case.
It doesn't happen immediately after an unmount, but I think these might all
have been not long after one.

Kernel is 2.1.7, no modules. Let me know if anything else is relevant.

Nov 3 03:12:11 torch kernel: VFS: iput: trying to free free inode
Nov 3 03:12:11 torch kernel: VFS: device 00:00, inode 6049, mode=00100644

Nov 6 20:15:58 torch kernel: iput: inode 2385 on device 03:05 still has mappings.
Nov 6 20:15:58 torch kernel: Inode i_mmap ring corrupted
Nov 6 20:15:58 torch kernel: VFS: iput: trying to free free inode
Nov 6 20:15:58 torch kernel: VFS: device 00:00, inode 2385, mode=00100755
Nov 6 20:17:58 torch kernel: VFS: iput: trying to free free inode
Nov 6 20:17:58 torch kernel: VFS: device 00:00, inode 5020, mode=00100644
Nov 6 20:17:58 torch kernel: VFS: iput: trying to free free inode
Nov 6 20:17:58 torch kernel: VFS: device 00:00, inode 11, mode=00040755
Nov 6 20:17:59 torch kernel: iput: inode 3985 on device 03:01 still has mappings.
Nov 6 20:17:59 torch kernel: Inode i_mmap ring corrupted
Nov 6 20:17:59 torch kernel: VFS: iput: trying to free free inode
Nov 6 20:17:59 torch kernel: VFS: device 00:00, inode 3985, mode=00100755

Nov 6 20:33:37 torch kernel: VFS: iput: trying to free free inode
Nov 6 20:33:37 torch kernel: VFS: device 00:00, inode 20570, mode=00100644

Thanks,

Jeremy Boulton <boultonj@ugcs.caltech.edu>