search for: wait_on_inode

...dic problem, and I can't seem to find any info on Google about it. I am running a variant of 2.4.9-34. A certain process is locking access to a filesystem, so that any subsequent access to it hangs the shell. I'm seeing: #ps xwo pid,command,wchan |grep inode 21062 <program name> wait_on_inode Looking at the source code, I can see that the inode attribute I_LOCK is getting set, but for some reason is not being cleared. At the very least, I'd like to know *which* inode is being locked so I can narrow the problem down to an application developed internally and a third-party database....

...teback_control wbc = { .nr_to_write = LONG_MAX, .sync_mode = WB_SYNC_ALL, @@ -569,10 +570,11 @@ might_sleep(); spin_lock(&inode_lock); - __writeback_single_inode(inode, &wbc); + err = __writeback_single_inode(inode, &wbc); spin_unlock(&inode_lock); if (sync) wait_on_inode(inode); + return err; } EXPORT_SYMBOL(write_inode_now); @@ -641,8 +643,11 @@ need_write_inode_now = 1; spin_unlock(&inode_lock); - if (need_write_inode_now) - write_inode_now(inode, 1); + if (need_write_inode_now) { + err2 = write_inode_now(inode, 1); + if (!err) + err = err2;...

Hi, Since upgrading to "2.6.18-194" I am getting odd messages in the logs. Such as; sraid3 kernel INFO task pdflush 259 blocked for more than 120 seconds. The output from > grep '120 seconds' /var/log/messages | tr : ' ' | awk '{print $10}' | sort | uniq -c 6 nfsd 4 pdflush This is from an NFS server that since the upgrade has been