http://bugzilla.novell.com/show_bug.cgi?id=568319 http://bugzilla.novell.com/show_bug.cgi?id=568319#c8 --- Comment #8 from Nikanth K <knikanth@novell.com> 2010-02-03 09:30:40 UTC --- I guess this is mostly an xfs over loop on xfs bug. Just that when the loop device supports barrier(issues fsync), xfs deadlocks. pdflush: writing dirty pages of the encrypted loop files. It holds an exclusive lock of the sb inodes of this encrypted disk. loop0,loop1,loop2,loop3: all are flushing the encrypted disk. Have issued an fsync on the underlying fs and waiting for them to finish. But it never finishes! kdmflush: all are waiting for loop threads to complete I/O. xfsdata/3 is waiting for excl lock of some inode. mld_hash holds shared/read lock of some inode. par2 holds exclusive/write locks on some inodes. There seems to be a deadlock for the inode lock. If you can upload a dump, it would be easy to find out exact cause. It is quiet difficult to deduce which xfs call we are seeing, whether the xfs calls over the encrypted disk or the underlying disk. -- 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.