Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*3\.2\.9\s+and\s+locking\s+problem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*3\.2\.9\s+and\s+locking\s+problem\s*$/: 7 ]

Total 7 documents matching your query.

1. 3.2.9 and locking problem (score: 1): Author: Arkadiusz Mikiewicz <arekm@xxxxxxxx>; Date: Fri, 9 Mar 2012 20:28:47 +0100; Are there any bugs in area visible in tracebacks below? I have a system where one operation (upgrade of single rpm package) causes rpm process to hang in D-state, sysrq-w below: [ 400.755253] SysRq :; /archives/xfs/2012-03/msg00219.html (15,250 bytes)
2. Re: 3.2.9 and locking problem (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 12 Mar 2012 11:53:25 +1100; I can't see why we'd get a task stuck here - it's waiting on the XFS_ILOCK_EXCL. The only reason for this is if we leaked an unlock somewhere. It appears you can reproduce this fairly quickly, so run; /archives/xfs/2012-03/msg00235.html (9,641 bytes)
3. Re: 3.2.9 and locking problem (score: 1): Author: Arkadiusz Mikiewicz <arekm@xxxxxxxx>; Date: Mon, 12 Mar 2012 14:43:58 +0100; linux vserver patch [1] seems to be messing with locking. Would be nice if you could make a quick look at it to see if it can be considered guilty part? On the other hand I wasn't able to reproduce o; /archives/xfs/2012-03/msg00248.html (11,930 bytes)
4. Re: 3.2.9 and locking problem (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 12 Mar 2012 12:14:25 -0400; In the 3.2 version xfs_sync_flags does a double unlock of the ilock - change the last argument of xfs_trans_ijoin from XFS_ILOCK_EXCL to 0 will fix this. The 3.0 version doesn't have this bug. And bt; /archives/xfs/2012-03/msg00250.html (7,979 bytes)
5. Re: 3.2.9 and locking problem (score: 1): Author: Richard Ems <richard.ems@xxxxxxxxxxxxxxxxx>; Date: Mon, 12 Mar 2012 18:49:14 +0100; Hi Christoph, Is there already a fix or will there be one for 3.2.10 ? I am already using 3.2.x on 4 servers in production ... Thanks, Richard -- Richard Ems mail: Richard.Ems@xxxxxxxxxxxxxxxxx Cape; /archives/xfs/2012-03/msg00252.html (8,535 bytes)
6. Re: 3.2.9 and locking problem (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 12 Mar 2012 14:02:18 -0400; It's code added by the vserver patch that doesn't exist in mainline.; /archives/xfs/2012-03/msg00255.html (8,715 bytes)
7. Re: 3.2.9 and locking problem (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 13 Mar 2012 11:00:52 +1100; Any idea why they aren't sending stuff like this upstream to us so they can be implemented correctly, robustly and in a future-proof manner? vserver users are going to be unhappy when their filesyste; /archives/xfs/2012-03/msg00262.html (8,987 bytes)

Current List: 1 - 7
Page: [1]