Hi Abhi, On Tue, 2007-08-14 at 14:37 -0500, Abhijith Das wrote: > Robert Clark wrote: > > > I've been seeing the same assertions as in bz198302, so I've tried out > >the debug patch there and it looks like they are being triggered by an > >EAGAIN from flock_lock_file_wait. Is this an expected return code? > No. This is not an expected return code as far as I can tell from the > code. Are you running NFS on GFS? If you can reproduce this problem > reliably, can you add that information to the bz? Also the output of cat > /proc/locks and 'gfs_tool lockdump' would be useful. No, I'm not running NFS. My filesystem is used as a home directory for users running GNOME desktops, so there are some pretty complex programs accessing it. After some experimentation, I've found a reliable way to reproduce the assertion involving opening a file twice and attempting to lock it on both filehandles - more details in bugzilla. Thanks, Robert -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
