All,

Since bringing up an installation of Coda, I have been getting a lot of
this in the logs on the server box:

Feb 12 18:55:18 cy kernel: iput: device 00:00 inode 28550 still has aliases!
Feb 12 18:55:18 cy kernel: iput: device 00:00 inode 28558 still has aliases!
Feb 12 18:55:18 cy kernel: iput: device 08:05 inode 127278 still has aliases!
Feb 12 18:55:20 cy kernel: VFS: bad count for in-use inode, count=243
Feb 12 18:55:33 cy last message repeated 3 times
Feb 12 18:55:34 cy kernel: iput: device 00:04 inode 285871 still has aliases!
Feb 12 18:55:34 cy kernel: iput: device 00:04 inode 285804 still has aliases!
Feb 12 18:55:34 cy kernel: iput: device 00:04 inode 74023 still has aliases!
Feb 12 18:55:41 cy kernel: VFS: bad count for in-use inode, count=243
Feb 12 18:56:17 cy last message repeated 3 times
Feb 12 18:57:17 cy last message repeated 4 times
Feb 12 18:58:17 cy last message repeated 3 times
Feb 12 18:59:17 cy last message repeated 4 times
Feb 12 19:00:17 cy last message repeated 3 times
Feb 12 19:01:17 cy last message repeated 3 times
Feb 12 19:01:37 cy kernel: VFS: bad count for in-use inode, count=243
Feb 12 19:01:37 cy kernel: iput: device 00:04 inode 285871 still has aliases!
Feb 12 19:01:37 cy kernel: iput: device 00:04 inode 285804 still has aliases!
Feb 12 19:01:37 cy kernel: iput: device 00:04 inode 74023 still has aliases!
Feb 12 19:01:47 cy kernel: VFS: bad count for in-use inode, count=243
Feb 12 19:02:18 cy last message repeated 2 times
Feb 12 19:03:18 cy last message repeated 3 times
Feb 12 19:04:18 cy last message repeated 4 times

(and on, and on..)


Bill, the 'VFS: bad count..' warning is from your d_cache debugging patch,
so I thought this might be of particular interest.  Do the messages
necessarily indicate filesystem problems?

Steve