http://bugzilla.novell.com/show_bug.cgi?id=568319
http://bugzilla.novell.com/show_bug.cgi?id=568319#c16
--- Comment #16 from Nikanth K 2010-02-16 12:02:24 UTC ---
This more and more looks like an xfs issue.
The problem could be that, when xfsdatad is waiting for lock on the loop
mounted(nested inside another xfs) xfs file-system and pdflush holds an
xfs_ilock in the nested xfs and waits for the log to be flushed.
But pdflush's wait will not complete as xfsdatad is per-cpu and not per-mounted
file-system. For pdflush to recover, xfsdatad has to work on the items queued
for the underlying xfs filesystem, instead of working/waiting on the lock for
the nested file-system. This creates a deadlock.
If this is the case, this could be resolved, either by creating xfsdatad per
mounted file-system, or by imposing some kind of ordering/priority such that
the underlying filesystem's work is given higher priority
I would also comment on the http://oss.sgi.com/bugzilla/show_bug.cgi?id=860 as
well to get some feedback
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.